What Should I Set the Allocation Unit Size to When Formatting?

By Jason Fitzpatrick on January 29th, 2013

In addition to asking for the file system you’d like to use, disk formatting tools will also ask for an “Allocation unit size”. What does this mean and what value should you select?

Today’s Question & Answer session comes to us courtesy of SuperUser—a subdivision of Stack Exchange, a community-driven grouping of Q&A web sites.

The Question

SuperUser reader Andrew Keeton is curious about what exactly he’s supposed to put in the allocation section when formatting a drive. He writes:

I’m formatting a 1TB external hard drive as NTFS. This drive is mainly meant for storing media such as music and video.

What should I choose for the allocation unit size setting? The options range from 512 bytes to 64K. Are there any guidelines that I might apply to other drive types? Should I stop poking around and just leave it at “default?”

While the default setting is usually the best choice for most users, let’s dig a little deeper.

The Answers

SuperUser contributors Jonathan and Andrew offer some insight. Jonathan writes:

If you are a “Standard User” by Microsoft’s definition, you should keep the default 4096 bytes. Basically, the allocation unit size is the block size on your hard drive when it formats NTFS. If you have lots of small files, then it’s a good idea to keep the allocation size small so your harddrive space won’t be wasted. If you have lots of large files, keeping it higher will increase the system performance by having less blocks to seek.

But again, nowadays hard drive capacity is getting higher and higher it makes small difference by choosing the right allocation size. Suggest you just keep the default.

Also keep in mind that the majority file are relatively small, larger files are large in size but small in units.

Andrew expands upon Jonathan’s answer with:

In terms of space efficiency, smaller allocation unit sizes perform better. The average space wasted per file will be half the chosen AUS. So 4K wastes 2K per file and 64K wastes 32K. However, as Jonathon points out, modern drives are massive and a little wasted space is not worth fussing over and this shouldn’t be a determining factor (unless you are on a small SSD).

Compare 4K vs 64K average case waste (32K-2K = 30K), for 10,000 files that only comes out to 300,000KB or around 300MB.

Instead think about how the OS uses space. Let’s say you have a 3K file which needs to grow 2K. With a 4K AUS the data needs to be split over two blocks – and they may not be together so you get fragmentation. With a 64K AUS there are a lot fewer blocks to keep track of and less fragmentation. 16x the block size means 1/16th the number of blocks to keep track of.

For a media disk where you photos, music and videos are stored, every file is at least 1MB I use the biggest AUS. For a windows boot partition I use the Windows default (which is 4K for any NTFS drive smaller than 16TB).

To find out what the cluster size is on an existing disk:

fsutil fsinfo ntfsinfo X:


Have something to add to the explanation? Sound off in the the comments. Want to read more answers from other tech-savvy Stack Exchange users? Check out the full discussion thread here.

Jason Fitzpatrick is a warranty-voiding DIYer who spends his days cracking opening cases and wrestling with code so you don't have to. If it can be modded, optimized, repurposed, or torn apart for fun he's interested (and probably already at the workbench taking it apart). You can follow him on if you'd like.

  • Published 01/29/13
More Articles You Might Like

Enter Your Email Here to Get Access for Free:

Go check your email!