How to use NTFS compression on Windows 10

On Windows 10, the New Technology File System (NTFS) file system includes a lightweight compression feature designed to reduce the size of files and save space while retaining normal access without the need for manual decompression like when using different containers.

However, enabling NTFS compression can have an impact on performance. Even though you don't have to use additional steps, in the background, the feature still has to decompress and recompress files every time you access them, which is a process that requires additional resources.

While the feature can degrade performance, there are plenty of scenarios where compression can still make sense. For instance, it could be another way to free up space, even after deleting temporary files and unnecessary contents. Also, it could be a suitable solution to set up a drive to store files that you rarely use. Or you could save files that you use frequently but that don't significantly impact your device performance, some of which can include pictures and documents.

Whatever your situation might be, on Windows 10, you can enable NTFS compression in at least two different ways. You can use compression at the file level or you can compress the entire drive.

In this Windows 10 guide, we'll walk you through the steps to compress files to free up space without the need for third-party tools.

How to compress files using NTFS file compression

Using the file compression with NTFS is the easiest method to make files smaller without the need to compress the entire drive, or use additional steps to zip and unzip every time you need a file, as the process is handled automatically without significantly impacting performance.

To compress files and folders using NTFS on Windows 10, use these steps:

  1. Open File Explorer.
  2. Browse to the folder that you want to use to store compressed files.
  3. Click the Home button.
  4. Click the New folder button.Quick tip: You can use the Ctrl + Shift + N keyboard shortcut to create a new folder faster.
  5. Type a name for the folder (for example, My Compressed Files) and press Enter.
  6. Right-click the newly created folder and select the Properties option.

  1. Click on the General tab.
  2. Click the Advanced button.

  1. Under the "Compress or Encrypt attributes" section, check the Compress contents to save disk space option.

  1. Click the OK button.
  2. Click the Apply button.
  3. In the "Confirm Attribute Changes" dialog, select the Apply changes to this folder, subfolders, and files option.

  1. Click the OK button.

Once you complete the steps, NTFS file compression will enable in the folder reducing the size of existing and future files you save into this location.

The steps outlined above will work to compress a folder as well as a single file.

You can check that file compression is working because you'll notice two arrows pointing to each other icon in the top-right corner.

If you want to see how much space this method is saving, right-click the folder, and select the Properties option. Size shows the size of the item without compression, while Size on disk is the size of the item after compression.

If you change your mind, you can always revert the changes using the same instructions, but on step No. 9, make sure to clear the Compress contents to save disk space option.

How to compress files using NTFS drive compression

Alternatively, instead of shrinking files and folders individually, you can also use the NTFS feature to compress an entire drive.

Using this option offers the same benefits as compressing files individually, which means that you can access files normally as compression and decompression happen very quickly.

To enable NTFS compression on a hard drive, use these steps:

  1. Open File Explorer.
  2. Click on This PC from the left pane.
  3. Under the "Devices and drives" section, right-click the storage that you wish to compress, and select the Properties option.

  1. Check the Compress this drive to save disk space option.

  1. Click the Apply button.
  2. In the "Confirm Attribute Changes" dialog, select the Apply changes to drive (drive letter), subfolders and files option.

  1. Click the OK button.
  2. Click the OK button again.

After you complete the steps, NTFS will enable compression inside the drive.

You can use compression on a drive with or without files, but if the drive isn't empty, NTFS will need to go through the process of making the files smaller, which could end up taking a long time. (Usually, you want to enable compression on an empty drive before storing files on it.)

If you want to undo the changes, you can use the same instructions outlined above, but on step No. 4, make sure to clear the Compress this drive to save disk space option.

How to know when you should and shouldn't compress files with NTFS

Although the ability to compress files without third-party software can come in handy to minimize storage usage, there are several things to keep in mind when using NTFS compression.

For example, you can enable compression on the drive that contains the Windows 10 installation, but it's not recommended to use the feature as it could significantly impact system performance and create additional problems.

If you want to compress the system drive, you should consider using Compact OS, which is a feature designed specifically to reduce the footprint of the installation allowing to free up space on the drive running Windows 10.

While you can use compression on virtually any device, it's only recommended to use this feature on a computer with a reasonably new processor and a fast drive, such as a Solid-State Drive (SSD), for best performance.

Also, you can use Windows 10's NTFS compression on USB flash drives and SD cards, but you should consider only enabling the feature on more capable drives (such as SSD and HDD).

In the case that you're dealing with a low-end or very old device, you should ignore compression and opt to purchase a larger external drive instead. Using a large storage device means more room to save files without the need for the system to use resources to compress and decompress your data, which can negatively impact performance.

The amount of space that you could save using this feature will always depend upon the amount of data and other factors. NTFS compression has been designed to be fast and lightweight, and as a result, the ratio of compression will usually be less than the one offered by third-party tools.

Drives and folders using NTFS compression can store already compressed files (such as zip folders and mp3 audio files), but it's unlikely that you'll see any size reduction.

Finally, when using NTFS compression, files have to go through a decompression process before they can be transmitted through the network, which means that this method isn't optimized to save bandwidth or time. If you need to send a large amount of data that will benefit from compression, you should use a zip container instead.

We're focusing this guide on Windows 10, but compression has been a feature of NTFS for a long time, which means that you can also use these instructions on Windows 8.1 and Windows 7.

Updated March 19, 2019: We revised this guide to make sure it's current with the latest version of Windows 10.

More Windows 10 resources

For more helpful articles, coverage, and answers to common questions about Windows 10, visit the following resources:

Mauro Huculak

Mauro Huculak is technical writer for His primary focus is to write comprehensive how-tos to help users get the most out of Windows 10 and its many related technologies. He has an IT background with professional certifications from Microsoft, Cisco, and CompTIA, and he's a recognized member of the Microsoft MVP community.

  • Been using this for the movies/shows partition since the XP days
  • You should stop doing that. The compressibility of video files, which are already highly compressed, is very low. Like, almost zero. So all you're doing is making your CPU work harder every time you try to play back one of those files (or move files to that partition), and saving no disk space in the process. NTFS file compression is great for TXT log files and other uncompressed formats like BMP or DOC. With compressed files like JPG, MP4/MKV, or DOCX, it does nothing but waste CPU cycles. For larger files, like movies or TV shows, it wastes a lot of CPU cycles with no benefit at all.
  • Why can't this be done for Windows Phones with low storage too?
  • It wouldn't help because most files on a phone are either already compressed (JPG files), and/or the performance hit from constantly compressing and decompressing system files would not be worth it.
  • I am not exactly a friend of compressing drives or folders. Something could go wrong with storage media itself,
    and some bytes might get corrupted. If you have some real bad luck
    the whole file or folder could get lost entirely. Not sure whether there are any built-in measures in the compression algorithms
    that are able to handle situation like these. Most of the data that is horded in masses these days
    are already compressed as the article mentions.
    Like music, movies, pictures. Never tried it, but I am not sure whether you gain a lot when you compress Office files etc. I have stayed away from disk and folder compression so far.
    It may be cheaper to buy a bigger drive and not encounter decompression snafus
    that potentially may be caused by the storage media being used as it grows old and becomes more unreliable. Wonder if there are any studies on that subject. Also wonder whether cloud services do use (hidden) compression to save storage cost. Some data stays untouched for years,
    so compression might be a thing to consider.
    Any info available on cloud services and (hidden) compression? How dangerous is compression in respect of data integrity? -
  • As with everything - BACK UP YOUR DATA. The only excuse for caring about data corruption in the age of easy free/low cost backup solutions is the time it takes to restore from the backup.
  • It's been a long  time since I've run into file corruption that was not user error (removing a USB drive while it was writing) or hardware failure. In any case the risk can be reduced with a proper backup plan which should be in place on any machine regardless of OS and file system. I would be more worried about drive failure which could cause all the problems you mentioned and more. Working in IT I go with the theory that all drives fail - it's simply a matter of will it fail before you have a backup.
  • I've been using this for aeons on my storage drives.
  • I have held a long-standing belief from the old DOS 6.x days of Doublespace and Drivespace compression tools (among others) that compression tools were pretty much the absolute DEVIL of technology. Prone to corruption and all sorts of issues. A recent question from a colleague of mine sent us to get in touch with a guy who is an "old timer" (haha) with Microsoft and has long been a part of the storage team on Windows... and we asked him, "is it safe?" He told us unequivocally, YES! The advances of NTFS compression over the last couple decades have made it night and day difference between the tools and "what we knew" from the old days. NTFS apparently has many inherent capabilities to self-heal and protect itself from those kinds of issues. He still doesn't recommend compressing an entire drive (or at least the Windows folder) just for performance reasons, but compressing folders and files is just fine.
  • Been doing this since DOS 6.0 when it was called Doublespace. I guess it's true that everything old is new again!
  • Thanks for this, and the link to the old article. I have always seen this option, but heard that it was a bad thing to do back in the W98 or older days. I guess it just stuck with me.
  • The article mention several times "which is a process that requires more processor and hard drive resources.", "it's safe to use NTFS compression when you have a computer with a reasonably fast processor and hard drive",... ​Actually, if you have an unbalanced computer with a quite fast processor but a slow hard drive, compression will use CPU for on-the-fly compression and decompression, but will result in less HDD bandwidth. So, contrary to what the article says, people with slow hard drives will get better speed improvements than people with SSDs. ​If you see your hard drive busy for long period of time and your CPU waiting for data to process, reducing files sizes even by just 10% by using CPU cycles that are otherwise lost waiting for the data might not only save you some storage space, it might well end up improving performances by 10%.
  • I did a performance analysis as part of my job, around 8 years ago, with hardware that was current then. In every case it was beneficial to compress text data (text files, strings, xml), no matter how long or short, before storing in whatever method we used, this was whether writing to a SQL database (MS or Oracle) or direct to disk, the cost of CPU was always outweighed by the reduction in time to write to the storage media, we even found in most cases, pre-compressed data didn't adversely affect performance either, but in that case we got compression ratios so low you wouldn't normally bother if saving disk space was your aim. The benefit was particularly high for SQL server, where we were using Zip compression rather than the built-in file compression, so generally achieved significantly better compression rations. We did find some sets of data where the length was extremely short, could increase the size rather than reduce it, but unless the data was 10s of bytes or the file size was <2kb there was always a reduction in size. These days I always set compression on for log file folders, this is where the data is largely expendable and mostly text (or god forbid, XML), so compresses well, but even then, keeping 1 months worth of files, I always set files a week old, to be zipped and sent to an uncompressed OS folder, doing this on our IIS and FTP servers, has meant we can keep 2 months of logs, for the same space taken by 7 days. I've been using Windows built-in compression for a very long time and so far have never had any data corrupt.