Guiformat Allocation Unit Size Explained: 32K vs 64K and Smaller Sizes
Formatting erases everything on the target drive. Before you change an allocation unit size, back up the drive, and double-check the drive letter. Allocation unit size, also called cluster size, is set at format time. You cannot change it later without reformatting, so it is worth understanding before you click Start. This guide explains what the setting does, what the common values mean, and which values community device guides recommend, without presenting a device value that has not been checked.
This site is an independent, unofficial resource about FAT32 GUI Formatter, also called guiformat. It is not affiliated with RidgeCrop Consultants or Microsoft. Guiformat is a portable Windows program that formats an existing partition to FAT32. Its allocation unit size field is shown in bytes, so 32768 means 32K and 65536 means 64K. The commonly used default is 32768.
What is an allocation unit?
A file system divides a drive into small blocks called clusters or allocation units. Every file occupies a whole number of clusters. A tiny file that is only a few hundred bytes still occupies one full cluster, and the rest of that cluster is unused. A large file occupies many clusters in a row, or in a chain if the drive is fragmented.
That simple rule explains the whole trade-off. A smaller cluster size wastes less space on small files, because each file rounds up to a smaller block. A larger cluster size wastes more space on small files, but the file system has fewer clusters to track, which can help when reading large files in sequence. Neither choice changes the 4GB single-file limit of FAT32, and neither choice changes the total capacity of the drive in a meaningful way for most users.
Consider a drive holding thousands of small text files. With 64K clusters, each file wastes, on average, roughly half a cluster, so the waste adds up across thousands of files. Now consider a drive holding a few hundred large videos. The waste per file is still at most one cluster, which is small compared with a file of hundreds of megabytes. That is why the right size depends on what the drive will hold and what device will read it, not on a single universal best value.
What the common values mean
| Allocation unit size | In bytes | Best suited to |
|---|---|---|
| 4096 (4K) | 4096 | Many small files, where wasted space matters more than sequential speed |
| 8192 (8K) or 16384 (16K) | 8192 or 16384 | Mixed documents and photos on a smaller drive |
| 32768 (32K) | 32768 | General use, and the commonly used guiformat default |
| 65536 (64K) | 65536 | Large files and larger cards where a device guide specifies it |
Smaller sizes are not automatically better, and larger sizes are not automatically faster. For everyday USB use, the difference between 32K and 64K is usually small.
Per-device guidance: only what device guides actually say
Device-specific values below come from community guides, not from a general rule, and they should never be generalised to every device. Always check the guide for your exact device and model before formatting.
| Device or use | Community guide value | Note |
|---|---|---|
| Nintendo 3DS, cards below 64GB | 32768 (32K) | A 3DS rule, not a general rule for all devices |
| Nintendo 3DS, cards at 64GB and above | 65536 (64K) | A 3DS rule, not a general rule for all devices |
| Nintendo Switch, community homebrew guides | 32768 (32K) commonly used | Community guides describe 32K as a standard, suitable size for general Switch installations |
| General USB drive or external drive | 32768 (32K) default | Use this unless a device guide specifies otherwise |
Two warnings belong with that table. First, the 3DS values are specific to 3DS guides. Do not apply the 3DS 64K rule to a camera, a car stereo, or a television simply because the card is 64GB or larger. Second, some community guides place the 3DS threshold at a different card size, so if the guide for your exact setup gives a different value, follow that guide rather than this summary. The table is a starting point for checking, not a replacement for the device guide.
For the Switch, community guides commonly describe FAT32 with 32K clusters as suitable for general installations. That is a community-guide observation, not a claim from Nintendo. If you use a stock Switch, follow Nintendo’s own guidance instead.
How to choose if no device guide applies
Ask three questions. What size are most of the files? If they are mostly small documents, a smaller cluster wastes less space. If they are mostly large media files, a larger cluster is less of a penalty. How large is the drive? On a small drive, the choice matters less in absolute terms. On a large drive holding many small files, a large cluster can waste a noticeable amount of space in total. What will read the drive? If an older device is involved, prefer the value its manual or a well-established guide for that device recommends, even if a different value would look better on paper.
If you cannot answer those questions, leave guiformat at 32768. The default exists because it is a workable compromise for mixed use, and changing it without a reason rarely produces a visible benefit. A wrong cluster size does not normally destroy data, but it can make a picky device refuse a card, which is why device guides matter more than theory.
Changing the size later
There is no safe in-place change of cluster size. To change it, back up the drive, reformat with the new allocation unit size, and copy the files back. That is the same workflow as any format, with the same warning: formatting erases everything on the target volume, so back up first and double-check the drive letter. If you are changing size only because a device rejected the card, test the card in the device after the reformat before copying a large library back onto it. A short test saves a long recopy.
FAQ
What does allocation unit size mean in guiformat?
It is the cluster size, shown in bytes. 32768 is 32K and 65536 is 64K. Every file occupies a whole number of clusters.
Is 64K always faster than 32K?
No. Larger clusters can help sequential reads of large files, but they waste more space on small files, and the difference is often small for everyday use.
Should I use the 3DS 64K rule for all large cards?
No. That rule comes from 3DS guides. Do not generalise it to cameras, consoles, televisions, or other devices.
What should I pick if I am unsure?
Leave guiformat at its commonly used default of 32768, unless a guide for your exact device says otherwise.
