Windows Server data compression uses NTFS’s built-in encoding to shrink files on disk without additional hardware. Enable it through File Explorer’s Advanced Properties, the compact.exe command line, or File Server Resource Manager for policy-based automation. Target log files, archives, and file shares — not already-compressed formats like ZIP or JPEG.

What Is NTFS Compression and When to Use It

NTFS compression is a native Windows Server feature that encodes file data using fewer bits at the file system level — transparently, without requiring third-party tools. The trade-off is real: every read and write incurs a small CPU cost to decompress and recompress on the fly. That cost is acceptable for cold archives, log directories, and file shares accessed sporadically. It is not acceptable for databases, active virtual machine disk files, or media formats that store data in compressed form already.

Before enabling compression anywhere, audit current disk usage. Run Get-PSDrive in PowerShell or open Disk Management to identify volumes approaching capacity, then locate the folders holding large, infrequently accessed, uncompressed data. File shares, compliance archives, and old project folders are the best candidates. System volumes, SQL data files, and active application directories are not.

Enable NTFS Compression on Folders or Files

File Explorer gives you the fastest path to enabling compression on a specific folder or file. Right-click the target, select Properties, click Advanced on the General tab, check Compress contents to save disk space, and click OK. When compressing a folder, choose Apply changes to this folder, subfolders, and files for full coverage.

Windows marks compressed items with blue file names in Explorer (when that display setting is active) and badges their icons with a double arrow. To confirm compression is working, right-click the folder, open Properties, and compare Size versus Size on disk. A smaller “Size on disk” value confirms the compression ratio and shows actual space reclaimed.

Use compact.exe for Bulk and Scripted Operations

The built-in compact.exe utility handles bulk compression tasks more efficiently than File Explorer, and it integrates cleanly into scheduled scripts. Open an elevated Command Prompt or PowerShell window and use the following syntax:

• Compress an entire drive: compact /c /s /i /f D:\
• Compress a specific folder: compact /c /s:D:\Share\ArchivedData
• Decompress: replace /c with /u

The /c flag compresses, /s recurses into subdirectories, /i continues past errors, and /f forces re-compression on files already flagged as compressed. For recurring tasks, wrap this command in a PowerShell script and schedule it via Task Scheduler during off-peak hours. Add >> C:\Logs\compression.log to capture a timestamped record of every run.

Expert Take

When scripting bulk compression across multiple servers, run a test pass against a representative sample folder and log before/after disk usage before touching production shares. A compression run with no progress output is a black box. Redirect compact output to a log file so you have a dated record of what ran, what was skipped, and what errored — especially useful when FSRM and manual scripts overlap on the same directory tree.

Set Up FSRM for Policy-Based Automated Compression

File Server Resource Manager (FSRM) is the right tool when you need compression to run automatically on a schedule based on file age, type, or location. Install it through Server Manager by adding the File Server Resource Manager role service under File and Storage Services.

Once installed, build a File Management Task:

1. Open Server Manager → Tools → File Server Resource Manager.
2. Expand File Management Tasks and select Create File Management Task.
3. Set the task scope to the folders you want managed.
4. Under Condition, define your rule — for example, files not accessed in 90 days.
5. Set the Action to File compression.
6. Configure a schedule (weekly or monthly fits most environments) and save.

FSRM executes the task against matching files without administrator intervention. Events log to Event Viewer under Applications and Services Logs → Microsoft → Windows → SRMSVC, giving you an auditable record of every compression action taken and any files skipped due to access errors.

Monitor and Verify Compression Effectiveness

After deploying compression, verify it is delivering real space savings without degrading performance. The two fastest checks are Properties comparisons and Task Manager observation.

• Properties check: Right-click any compressed folder, select Properties, and compare Size to Size on disk. A meaningful gap confirms compression is active. Text-heavy log archives compress 40–70% in practice; binary files and pre-compressed formats show little or no reduction.
• Task Manager: Open the Performance tab, select the relevant disk, and watch I/O throughput and CPU utilization during peak access. A CPU spike that correlates with reads from compressed folders signals the workload is too active for compression at that path.
• Event Viewer: Review FSRM logs for error events indicating files skipped or access-denied failures during scheduled compression runs.

If CPU overhead exceeds your threshold, move active data out of compressed directories and restrict compression to cold-storage paths. Compression works best when data written rarely and read infrequently.

Best Practices and Performance Considerations

Three rules prevent the most common compression mistakes on Windows Server.

Never compress already-compressed files. ZIP, RAR, JPEG, MP4, and similar formats store data in compressed form. Applying NTFS compression on top adds CPU overhead and produces no meaningful space savings. Exclude these extensions explicitly in your FSRM policy conditions or compact.exe scripts using file type filters.

Keep system files and active databases uncompressed. Compressing the Windows directory, SQL Server data files, Exchange databases, or active VM disk images introduces read/write latency that compounds under load. The performance penalty outweighs the space benefit in every production workload scenario.

Schedule bulk operations during off-peak hours. Initial compression of a large share is CPU-intensive. Schedule compact.exe runs or FSRM tasks for nights or weekends. In Task Scheduler, set the process priority to Below Normal so compression yields to user workloads if they overlap.

On SSDs, NTFS compression still saves space, but the performance profile differs from spinning disks. SSDs handle the I/O pattern of compressed reads well — the CPU overhead is the primary cost, not seek latency. That makes an SSD a reasonable host for compressed archives as long as the workload is read-heavy rather than latency-sensitive.

For a broader look at protecting the data living on these servers, see: 13 Essential Strategies for Robust CRM Data Protection and Business Continuity in HR & Recruiting.