7-Zip says there is not enough space on the disk: the causes

If 7-Zip says "There is not enough space on the disk" while the drive you chose has room, check three things. Dragging files from 7-Zip File Manager into Explorer extracts them to the Windows temporary folder first, usually on C:. A FAT32 drive cannot hold a file of 4 GiB or more. And the archive and its files may not fit together.

By Yash Bavadiya, maker of HatchZip. Updated .

What does "There is not enough space on the disk" mean in 7-Zip?

It is Windows' message for a full drive, system error 112 in Microsoft's list, and 7-Zip shows it when Windows refuses a write. The message does not name the drive, so the full one may not be the drive you are extracting to.

7-Zip on Linux reports the same failure as "No space left on device".

Why does dragging files out of 7-Zip use space on C:?

Because Explorer can only copy files that already exist on a disk. The 7-Zip FAQ explains: "7-Zip extracts files from archive to temp folder and then 7-Zip notifies Windows Explorer about paths of these temp files. Then Windows Explorer copies these files to drop target folder."

7-Zip's source code shows where that is. For a drag out of an archive, the File Manager creates a folder whose name starts with 7zE in the Windows temporary folder (PanelDrag.cpp); opening a file from an archive uses a folder starting with 7zO (PanelItemOpen.cpp). Windows takes that folder from the TMP or TEMP variable, according to Microsoft. Type %TEMP% into the Explorer address bar to see it; on a standard Windows setup it is inside your user folder on C:.

So dragging a large folder out of 7-Zip onto drive D: needs room for it on C: first, and only then does Explorer copy it to D:.

The fix: use Extract

In 7-Zip File Manager, select the files, click Extract, and set "Extract to" to a folder on the drive you want. Or right-click the archive in Explorer and choose 7-Zip, then Extract files (on Windows 11 it can be under Show more options). The FAQ also notes that dragging from one 7-Zip window to another avoids the temporary files.

If you need drag and drop, you can point the TMP and TEMP user variables at a folder on a drive with room (search Windows settings for "environment variables"). That moves the temporary folder for every program, not only 7-Zip, so Extract is the simpler fix.

Can a FAT32 drive make 7-Zip say there is not enough space?

Yes. FAT32 cannot hold a single file of 4 GiB or more, and the write that would cross that size fails with the same status Windows uses for a full drive, so the message is the same even when the drive is mostly empty.

The limit is in Microsoft's file system comparison, which lists 4 GiB as FAT32's maximum file size. The status comes from the FAT driver: in the FAT driver sample Microsoft publishes, a write that would take a file past 32-bit size is refused with STATUS_DISK_FULL.

To check, right-click the drive in Explorer, choose Properties, and read File system. If it says FAT32 and the archive holds a file of 4 GiB or more, copy anything you need off the drive and format it as exFAT or NTFS (right-click the drive, Format). Formatting erases the drive. 7-Zip's Size column shows how large each file in the archive is.

How much space does 7-Zip need when the archive is on the same drive?

Room for every extracted file, while the archive stays where it is. Add up the Size column in 7-Zip to see what it will write; Packed Size is what the archive already takes.

On 2026-10-25, a 180.0 MB 7z holding 200.0 MB of files was copied onto an empty 220 MiB disk, leaving 50.6 MB free. 7-Zip 25.01 stopped while writing file 6 of 21 with "No space left on device". The full method and the results for unzip and HatchZip are in the guide to extracting without enough disk space, along with the usual fixes: another drive, freeing space, and extracting in place.

A split archive (.7z.001, .7z.002, and so on) is no different: 7-Zip reads the parts in order, and all of them stay on the disk until you delete them.

Where HatchZip fits, and where it doesn't

HatchZip helps when the archive and the files are on the same drive and the drive has room for the files but not for both. It extracts the archive from the end and cuts each finished part off the archive file, and deletes each part of a split archive once it is empty. In the test above, it extracted the same 200.0 MB from a 7z made with -ms=20m on the same nearly full disk, every file byte-identical to the original. Download HatchZip.

How much it helps with a 7z depends on how the archive was made. 7-Zip packs files together into solid blocks, and HatchZip can free a block only once all of it is out. With 7-Zip's default settings, a whole archive can be one block; in the same test, HatchZip refused that archive before changing anything, because it needed 200.1 MB free. hatchzip check shows this before anything changes. If you make the archive yourself, a smaller solid block size (the Solid Block size setting in 7-Zip's Add to Archive window, or -ms=64m on the command line) lets it be freed in steps.

It does not help with:

  • The temporary folder. That is how 7-Zip hands files to Explorer, not a lack of space on your target drive. Use Extract.
  • FAT32. HatchZip cannot write a file of 4 GiB or more to a FAT32 drive either.
  • A drive that cannot hold the extracted files themselves.
  • Keeping the archive. In-place extraction uses it up.
  • .tar.xz and .tar.zst, which 7-Zip opens and HatchZip does not read yet.

Sources

Checked 2026-10-25.