What Is CompactOS? Windows' Built-In Compression of System Files, Explained

The mechanism: compressed in place, opened on demand

NTFS has always supported per-file compression, but the classic algorithm, LZNT1, was tuned for documents, not executables. CompactOS uses the newer XPRESS codec through the Windows Overlay Filter (WOF): the file keeps its name and path, its compressed payload is managed by the filter driver, and anything that reads it — including the memory manager itself — gets transparently decompressed data. Microsoft built it as the successor to Windows 8.1's WIMBoot, without that feature's separate image file, and it is far more surgical than the old "compress this drive" checkbox.

You control the whole thing with one tool. compact /compactos:query reports whether it is enabled; compact /compactos:always compresses the eligible system binaries; compact /compactos:off undoes it. Servicing and Windows Update handle compressed files without any special action — the component store tracks compression state, so monthly updates are not a fight with the filesystem.

What it costs, honestly

Decompression happens on read, so the CPU pays a small tax every time a system binary pages in — and on hardware from the last several years that tax is invisible in everyday work. Two honest caveats: on very weak processors paired with slow storage, page-ins become measurably slower, and synthetic disk benchmarks will show lower read throughput on compressed files. Neither shows up as slower app launches or booting on a normal machine — the cost exists, but it is paid in microseconds on files you open once and keep in memory.

What CompactOS does not do is compress your data. It touches Windows' own binaries only — your documents, games and downloads stay exactly as they are, and their size is your business. And because the feature is per-file and reversible, disabling it simply rewrites the files uncompressed over a few minutes: no reinstall, no repartitioning, no risky step.

When it is worth it

The decision is almost entirely about free space, not performance. Two gigabytes decide the matter on a tablet with 64 GB of storage and mean nothing on a 2 TB gaming drive. Check the numbers with the query command before and after — what your machine reports is the only figure that matters, since it varies by Windows version and installed components.

• Tablets and cheap laptops with 32–64 GB eMMC — the feature's target audience; 2 GB is several percent of the whole disk
• A nearly full small SSD where 2 GB delays a storage upgrade or a reinstall
• Machines with hundreds of gigabytes free — skip it; the savings do not justify even a theoretical tax
• Old, very weak CPUs — measure first: run query, enable, and compare boot and app launches before committing
• Anyone about to compress the whole Windows folder by hand with /EXE:LZX — don't; CompactOS already covers the eligible set, supported
• Rollback anytime — compact /compactos:off rewrites the files uncompressed; there is nothing to uninstall

Questions and Answers

Read next