A clear explanation of NTFS drive compression, how much space it can save, whether it is safe, and when you should—or should not—enable it.
The Compress this drive to save disk space option tells Windows to use the built-in NTFS file system compression feature on a drive. Windows stores eligible files in a compressed form so they occupy less physical space, then automatically decompresses them in memory when programs open them.
This process is transparent and lossless. You continue opening, editing, copying, and saving files normally. It does not convert the drive into a ZIP archive, reduce image quality, or permanently remove information from files.
NTFS compression works at the file-system level. Windows divides file data into blocks, compresses blocks that can be reduced efficiently, and stores the compressed result on the disk. When an application requests the file, NTFS decompresses the required data automatically. When the application saves changes, Windows compresses the data again before writing it to storage.
Files can be compressed individually. A drive may contain compressed and uncompressed files at the same time.
A compressed folder is marked so new files added to it are normally compressed automatically.
Programs use compressed files like ordinary files; no manual extraction step is required.
Data that does not compress well may remain close to its original size on disk.
When you select the checkbox in a drive’s Properties window and click Apply, Windows asks whether to apply the change only to the drive’s root or also to all subfolders and files. To compress existing content across the drive, choose Apply changes to drive, subfolders and files.
Yes, NTFS compression is generally safe. It is a built-in Windows file-system feature and uses lossless compression, so decompressed data is identical to the original data. Clearing the checkbox later reverses the process and restores files to ordinary uncompressed NTFS storage.
However, safe does not always mean ideal. Compressing an entire drive can take a long time, use CPU resources, and produce little benefit if the drive mostly contains data that is already compressed. A power loss, failing disk, or file-system corruption is a risk during any large storage operation, so important data should always have a separate backup.
There is no fixed compression percentage. The result depends almost entirely on the data stored on the drive. Plain text, source code, logs, database exports, XML files, and uncompressed bitmap images may shrink substantially. JPEG photos, MP4 videos, ZIP archives, application installers, and many modern game files are already compressed and often shrink very little.
| File Type | Typical Compressibility | Examples | Recommendation |
|---|---|---|---|
| Plain text and logs | High | .txt, .log, .csv, .xml |
Good candidates for compression |
| Source code and scripts | High | .html, .css, .js, .py |
Usually worthwhile for archives |
| Uncompressed images | Medium to high | .bmp, some .tif files |
Can save noticeable space |
| Modern documents | Low to medium | .docx, .xlsx, .pdf |
Results vary; many are already compressed internally |
| Photos, audio, and video | Low | .jpg, .png, .mp3, .mp4 |
Usually not worth compressing with NTFS |
| Archives and installers | Very low | .zip, .7z, .rar, .iso |
Little or no useful saving |
Compression adds CPU work because data must be compressed when written and decompressed when read. The real-world impact depends on the processor, storage device, workload, and how compressible the files are.
On a modern PC performing ordinary document, browsing, and office tasks, the difference may be small. In some read-heavy situations, compression can even reduce the amount of data that must be read from a slower disk. However, heavy write workloads and applications that constantly update large files can experience additional overhead.
Folders containing logs, text files, old projects, and rarely changed documents are generally suitable candidates.
Good use caseWindows can use compressed files transparently, but whole-drive compression creates broader and more continuous CPU overhead.
Evaluate firstVirtual machines, active databases, build folders, caches, and frequently updated game data are poor candidates.
Avoid when possibleNTFS compression works on both HDDs and SSDs. An HDD may benefit from reading fewer physical bytes, but its slower random access can still dominate performance. An SSD is already fast, so reducing I/O may be less valuable, while the CPU still performs compression and decompression. The best decision depends more on the workload and file types than on the storage technology alone.
You can compress the Windows system drive, and Microsoft includes this option as one possible way to free space when the OS drive is low. It can be useful as a temporary measure when you need enough free storage to install a Windows update or complete maintenance.
For permanent everyday use, compressing the entire C: drive is usually less efficient than cleaning temporary files, uninstalling unused applications, moving personal data, or upgrading storage. The system drive contains many files that change frequently, plus many program and media files that may not compress well.
C:, open Settings → System → Storage, review Temporary files and Cleanup recommendations, enable Storage Sense, uninstall unused apps, and move large videos, ISO images, backups, or virtual machines to another drive.
Targeted compression is often better than compressing a whole drive. It gives you most of the potential storage benefit while limiting CPU overhead and avoiding workloads that react poorly to file-system compression.
The graphical procedure is almost identical in Windows 10 and Windows 11. The option is available for compatible NTFS volumes.
If Windows reports that some files are in use or access is denied, you may be able to choose Ignore All and let the process continue. Those particular files may remain uncompressed.
Compressing only selected folders is usually the best balance between saved space and performance. Use this method for archives, logs, source code, or other highly compressible data.
NTFS compression is reversible. Decompressing a drive or folder restores normal file storage without changing the file contents.
The built-in compact command displays or changes NTFS compression for files and directories. Open Command Prompt or Windows Terminal; administrator rights may be required for protected locations.
Command Promptcompact
Command Promptcompact /c /s:"D:\Archive" /i
Command Promptcompact /u /s:"D:\Archive" /i
| Parameter | Meaning |
|---|---|
/c |
Compresses the specified files or directories. |
/u |
Decompresses the specified files or directories. |
/s:"path" |
Processes the specified directory and its subdirectories. |
/i |
Continues the operation after errors whenever possible. |
The option normally appears only when the volume supports NTFS file compression. Check the drive’s Properties window and look at the File system field.
| Possible Cause | Explanation | What to Do |
|---|---|---|
| The drive uses FAT32 or exFAT | The Explorer checkbox uses NTFS file-system compression. | Use ZIP archives, move data to an NTFS volume, or reformat only after backing up all files. |
| The NTFS allocation unit is larger than 4 KB | NTFS compression is not available on volumes formatted with allocation units larger than 4 KB. | Check the cluster size. Changing it normally requires backing up and reformatting the volume. |
| The file is EFS-encrypted | NTFS compression and EFS encryption cannot be active on the same file. | Keep the file encrypted, or decrypt it before enabling compression. |
| You do not have permission | Protected system or shared files may require elevated rights or may be in use. | Sign in as an administrator and close applications using the files. |
| The drive is read-only or has errors | Windows cannot rewrite file data when the volume is write-protected or unavailable. | Remove write protection and check the file system before retrying. |
Open Command Prompt and run the following command, replacing C: with the required drive letter:
Command Promptfsutil fsinfo ntfsinfo C:
Find Bytes Per Cluster. A value of 4096 means a 4 KB allocation unit.
| Method | How It Saves Space | File Access | Best Use |
|---|---|---|---|
| NTFS compression | Stores individual files in compressed form on an NTFS volume | Transparent; files open normally | Compressible folders that must remain directly accessible |
| ZIP or 7z archive | Combines files into a separate compressed archive | Files may need extraction or archive-aware software | Long-term storage and transferring groups of files |
| Storage Sense | Deletes selected temporary or unnecessary local files | Deleted files are no longer available locally | Automatic routine cleanup |
| OneDrive Files On-Demand | Keeps selected files online-only instead of storing full local copies | Internet may be required to download online-only files | Cloud-synced personal and work files |
| CompactOS | Compresses Windows operating-system binaries | Managed automatically by Windows | Reducing the Windows installation footprint |
Compress this drive to save disk space enables lossless NTFS compression for files and folders on a compatible Windows volume. It is generally safe and completely reversible, but the amount of storage saved depends on file types, and Windows must use additional CPU time whenever compressed data is read or written.
For most PCs, the best strategy is to compress selected folders containing text-heavy or rarely changed data rather than the entire system drive. Use whole-drive compression when you understand the tradeoffs or need temporary space, and use Storage Sense, Cleanup recommendations, data migration, or a larger drive for a more permanent solution.