CompactGUI: Transparent Folder Compression on Windows with the WOF Driver

The problem CompactGUI solves for small SSDs

Modern game installs are large, and the people who feel that most are the ones with a 500 GB or 1 TB system drive. Windows has shipped a filesystem-level answer to this since Windows 10: the Windows Overlay Filter (WOF) driver, exposed through the command-line tool compact.exe. CompactGUI is a graphical front end for that mechanism. It targets a specific user: someone on Windows who wants a game or program folder to occupy less space without turning it into an archive they have to unpack before running.

The README frames the benefit in concrete terms. It lists ARK: Survival Evolved shrinking from 169 GB to 91.2 GB and Adobe Photoshop from 1.71 GB to 886 MB. Those are the project's own published examples, not independent measurements, and results vary by content. The README also notes the tool is intentionally limited to folders and files: whole drives and entire Windows installations cannot be modified from it.

How WOF compression works inside CompactGUI

The mechanism is transparent compression at the filesystem level. Files are not repackaged the way Zip and Rar archives are. The README states you can still browse, launch games and programs exactly as before, except they take up less space. Decompression happens at runtime, which is why the README describes the added CPU load as hardly noticeable, citing a test on an i3-370M from 2010.

CompactGUI itself is a WPF application written in Visual Basic .NET, with the solution split into CompactGUI.Core, CompactGUI.Logging, CompactGUI.Watcher, CompactGUI.Tests and the main CompactGUI project. The Watcher component is the piece that keeps folders compressed over time: it monitors tracked folders for changes, such as a Steam game update, and re-compresses them in the background. The repository also carries a Version.xml file at the top level, and the README points to an online database of compression results built from community submissions.

That database matters more than it first appears. The estimation feature is described as built from over 100,000 community submissions for Steam games, while non-Steam games fall back to an algorithmic estimate. Estimation is a prediction, not a guarantee, and the README is candid that a large batch of submissions was lost when a Google Form broke at the 100,000 mark.

Installing CompactGUI and compressing a first folder

The README gives two installation routes: download from the GitHub releases page, or install with Winget. The Winget command is the shorter path and is quoted verbatim in the README.

winget install CompactGUI

After installation, launch CompactGUI. The interface is organised around a folder picker, a compression view, a database view and a watcher view, based on the screenshots referenced in the README. Point it at a folder you want to shrink, such as a game install directory, and start compression. The README describes visual feedback on progress and statistics during the pass.

Before compressing, check the estimation figure the tool shows. For Steam games it draws on the community database; for everything else it uses the algorithmic estimate. The README also documents a configurable list of poorly-compressing file types that can be skipped, and that list is editable per folder. If a folder contains a lot of already-compressed data, that setting is the difference between a useful pass and a wasted one.

For repeat use, the README documents Windows Explorer context menu integration and a background Watcher that keeps tracked folders compressed. The Watcher is the feature to enable if a game updates regularly and you do not want to re-run compression by hand each time.

Where CompactGUI is the wrong tool

The README carries an explicit caveat: the tool should not be used on games that utilise DirectStorage on Windows 11. DirectStorage loads assets from the SSD while bypassing the CPU, so compressed files must be decompressed before reaching the GPU, which the README says negates any performance gains. This is not a bug to be fixed later; it is a structural conflict between transparent compression and a storage path designed to avoid CPU work.

The second boundary is scope. CompactGUI compresses folders and files. The README states plainly that whole drives and entire Windows installations cannot be modified from it. If your goal is to reclaim space across an entire volume, this is not the tool.

The third consideration is the compression pass itself. Transparent compression still has to write data, and the README does not document a rollback or undo path for a completed compression run. It also does not document how the Watcher behaves if it re-compresses a folder while a game or application is running. Treat those as unknowns to test on a small folder before committing a 150 GB install.

CompactGUI versus archive tools and compact.exe

The nearest alternative is the built-in compact.exe command-line tool that ships with Windows 10 and later. CompactGUI uses the same underlying WOF algorithms; the README describes it as working directly with the Win32 API to achieve the same thing as compact.exe. The difference is the interface and the surrounding workflow: compact.exe gives you flags and output, while CompactGUI gives you progress statistics, per-folder skip lists, a community estimation database, Explorer integration and the background Watcher. If you are comfortable scripting compact.exe and do not need estimation or monitoring, the command-line tool covers the compression itself.

The other comparison point is archive software such as Zip and Rar. Those produce a separate archive that must be extracted before the contents can be used. CompactGUI does not repackage anything, so the folder keeps working in place. That is the whole reason it exists, and it is also why the DirectStorage caveat applies: an archive would be decompressed once at install time, while transparent compression is decompressed on every read.

Maintenance, licensing and upgrade cost

CompactGUI is licensed under GPL-3.0. That matters if you intend to redistribute a modified build or bundle it into a product; GPL-3.0 carries obligations around source disclosure for derivative works. Nothing here is legal advice, and anyone shipping it commercially should read the licence text rather than rely on a summary.

The project is on the 4.0 beta line, with v4.0.0-beta.12 released on 2026-09-21 and the repository's last push on the same day. Running beta software means the interface and behaviour can change between builds, and the release history shows betas arriving roughly one to three weeks apart. The repository is not archived and development is ongoing. Upgrading between betas is a download-and-replace operation, but the README does not document a migration path for Watcher state or the per-folder skip lists, so re-check those settings after an upgrade.

There is also a data dependency worth noting: the estimation database lives online, and the README invites users to submit Steam game results from within the application. If you rely on estimation accuracy, that reliance is on a community dataset rather than a shipped, versioned file.

Editorial conclusion

Adopt CompactGUI if you run Windows 10 or 11, your SSD is the constraint, and the folders you want to shrink are games or programs that do not use DirectStorage. Skip it on Windows 11 titles built around DirectStorage, and skip it if you want to compress an entire drive or a Windows installation, because the README states the tool only compresses folders and files. Before compressing anything large, verify the folder is not DirectStorage-based, check free space for the compression pass itself, and confirm the Watcher behaviour on folders that update frequently, since the README documents automatic re-compression but not a rollback path.

Frequently asked questions

Official sources

1. IridiumIO/CompactGUI on GitHub
2. Issues
3. License: GPL-3.0
4. README
5. Releases