Cluster size is one of those low-level settings most people ignore, but it can have a real impact depending on how you use your drive.
File allocation size (cluster size) is how a file system divides storage space into units (clusters). For example, if you format a drive with a small cluster size of 4K, but your average file size is around 1MB (1024K), each file will be split across 256 clusters (1024/4). That creates a lot of overhead for the file system to track.
On HDDs, splitting data into small clusters can increase the likelihood of file fragmentation. As the physical drive fills up, it compounds the issue as data is written to the outer edges first, and as more data is added, it gets stored closer to the center, resulting in slower performance and increased access time. So a small cluster size combined with a full drive can be a performance drag on an HDD.
With SSDs, fragmentation isn’t the issue, but small clusters still create more work for the controller. The SSD controller has to manage more metadata and handle a higher number of smaller write operations. As free space decreases, the controller has fewer available blocks to work with, which increases write amplification and reduces performance.
Larger cluster sizes (128K or higher) are better suited for large-file workflows like video, where they reduce overhead and improve efficiency. Windows gives you control over cluster size during formatting, but can affect cross-compatibility, as cluster sizes above 2048K can prevent macOS from mounting the volume, often showing as a greyed-out drive in Disk Utility.
On the other hand, macOS doesn't allow manual cluster size control in Disk Utility and applies a preset (128K for exFAT and 4K for HFS+). Disk Utility doesn't expose this setting, but a larger allocation size can be set via Terminal for video or similar workloads.
APFS shares the 4K default with a maximum of 64K. It doesn't benefit from larger cluster sizes the way other file systems do, as it compensates with SSD-specific optimizations, snapshots, and tight macOS integration — making cluster size less of a concern for most workflows.
In practice, cluster size has the most impact on Windows-formatted drives, exFAT and HFS+ volumes. For APFS on an SSD, the file system’s built-in optimizations largely offset the fixed block size, making the default good enough for most use cases.
In short, cluster size isn’t always critical, but for the right workload, it’s one of those small settings that can make a noticeable difference.
Share: