How NTFS compression works and when it pays off
NTFS compression is a per-file mechanism built into the file system itself: each file is compressed in 4 KB blocks, marked with an attribute, and decompressed on the fly whenever something reads it. Nothing gets packed into an archive, no file changes its path or name, and the attribute travels with the file when you copy it between NTFS drives. It works only on NTFS — FAT32, exFAT and ReFS simply do not have this feature.
The math depends entirely on what your files are. Text, office documents from older formats, SQL dumps and uncompressed images compress by 30–70%; already-packed media (JPG, MP4, ZIP, and the modern .docx/.xlsx, which are ZIP containers inside) gain nearly nothing and just burn CPU. Compress folders full of the first kind, skip folders full of the second, and the feature becomes a quiet win.
- Compresses well: .txt and .log files, mail archives, CSV and SQL exports
- Compresses well: BMP and TIFF images, virtual machine disks (VHD/VHDX)
- Compresses well: websites, HTML/XML trees, old .doc and .xls documents
- Gains almost nothing: JPG, PNG, MP4, MP3 — formats with built-in compression
- Gains almost nothing: ZIP, 7z and RAR archives, and modern .docx/.xlsx files
- Skip entirely: database files of running servers and heavily rewritten data
Enabling it: the checkbox and the compact command
For a folder, right-click it in File Explorer, open Properties → Advanced and tick “Compress contents to save disk space”. Windows will offer to apply the change to the folder only or to everything inside — pick the second. For a whole drive, right-click the drive, open Properties and tick “Compress this drive to save disk space”, then confirm the dialog; only new files are compressed immediately, existing ones are processed in the background, and you can keep using the PC.
The command-line route gives more control. In an elevated prompt, compact /c /s /i /q "D:\Projects" compresses the folder and all subfolders quietly, compact /u /s undoes the attribute recursively, and a bare compact /s shows a report of what is already compressed. One global switch lives in fsutil: fsutil behavior set disablecompression 1 turns compression off system-wide for new files (0 restores the default) and requires a reboot — handy as a policy, not as a cleanup tool.
What to expect after enabling it
Explorer marks compressed items with two small blue arrows pointing at each other. The mark is purely cosmetic, but it tells you at a glance which folders carry the attribute. Savings show up gradually on existing data — the background pass on a big drive can run for hours — and files written after enabling are compressed on write automatically.
Two limits are worth remembering. First, a file cannot be both NTFS-compressed and EFS-encrypted — ticking one clears the other, since they compete for the same attribute slot. Second, compression is a trade of CPU for disk space: on a modern SSD and CPU it is essentially free, but on near-full mechanical drives with databases or frequently rewritten files it can add latency. If you ever need the attribute gone, compact /u reverses everything without touching the file contents.
Questions and Answers
Does NTFS compression slow down Windows?
Each read and write does a little compression work, but on modern CPUs and SSDs the impact is negligible. Avoid it on database files and on folders that big programs rewrite constantly.
Why do compressed files show blue double arrows?
That is Explorer's visual marker for the compression attribute — harmless and informational. It disappears when you remove the attribute with compact /u or through the Properties dialog.
Can I enable NTFS compression on exFAT or FAT32?
No. The feature is part of NTFS only; on exFAT and FAT32 drives the option simply does not exist, and files there stay uncompressed no matter what you tick.
Know what is included before you buy.
The one-time 30-minute trial covers core tools. PRO-labelled features stay locked until a paid license is activated.
Read next
Write to us: [email protected]