SIZE VS. SIZE ON DISK

Size vs. Size on Disk: What's the Difference?

Right-click any file in Windows and you'll see two different numbers: size and size on disk - and they almost never match. A 10 MB file might occupy 10.1 MB of storage, while a large database file might occupy far less than its reported size. Neither number is wrong. They measure two different things, and understanding both is essential for accurate disk space analysis.

The Two Key Storage Metrics

Size (actual or logical size) is the true number of bytes of data the file contains. Size on disk (allocated size) is the amount of storage the file system has set aside to hold that data. FolderSizes reports both metrics side by side for every file and folder it scans, because each answers a different question: size tells you how much data you have; size on disk tells you how much storage it consumes.

How Disk Allocation Works: The Cluster System

File systems don't hand out storage byte by byte. They divide a volume into fixed-size allocation units, or clusters - think of them as parking spaces that are all the same size regardless of the vehicle. Cluster size depends on the file system (NTFS, FAT32, exFAT), the partition size, and formatting options; on typical Windows NTFS volumes the default is 4 KB.

A file always occupies whole clusters, which produces some counter-intuitive results:

• A 1-byte text file still allocates an entire 4 KB cluster.
• A 4,097-byte file (one byte over a cluster) requires two full clusters - 8 KB.
• A 10 MB file that isn't exactly divisible by 4 KB uses slightly more than 10 MB.

The unused space at the end of each file's final cluster is called cluster overhang or slack space - allocated but holding no data.

Calculating Wasted Space

On average, each file wastes about half a cluster. That gives a quick estimating formula:

Volumes dominated by huge numbers of small files - source code trees, mail stores, web caches - waste proportionally more, and larger cluster sizes amplify the effect. Rather than estimating, FolderSizes reports actual vs. allocated space for every file, folder, and volume it scans, so you can measure cluster overhang precisely and decide whether it's worth acting on.

When Size on Disk Is Smaller Than Size

Allocation overhead isn't the only reason the two numbers diverge - several NTFS features push the relationship the other way:

• NTFS compression - compressed files occupy fewer clusters than their logical size would require, so size on disk drops below size.
• Sparse files - files with large empty regions (virtual machine disks, some databases) allocate clusters only where real data exists.
• MFT-resident files - very small files can live entirely inside their NTFS Master File Table record, reporting a size on disk of zero bytes.
• Deduplication - on Windows Server volumes with Data Deduplication enabled, allocated space is shared between identical chunks, making per-file allocation figures even more surprising. See our note on Windows deduplication and disk space.

Why This Matters for Storage Management

• Capacity planning - drives fill up by allocated space, not logical size; planning against the wrong metric under-provisions storage.
• Small-file optimization - identifying folders with extreme slack ratios reveals where archiving thousands of tiny files into a single zip reclaims real space.
• Cluster-size decisions - formatting a volume that will hold millions of small files? Measured overhang data beats guesswork.
• Troubleshooting discrepancies - when "the files only add up to 400 GB but the drive says 500 GB used," the gap is usually allocation, compression, or sparse-file behavior - not hidden files.

Seeing Both Metrics in FolderSizes

Every FolderSizes view - the folder size detail report, file size distribution reports, largest files, and search results - shows size and size on disk side by side, from a single file up to an entire network share. FolderSizes 10 can even apply heat tinting to the size-on-disk column, making allocation hotspots visible at a glance. It's the fastest way to see what your storage is really doing with its space.

Related reading: compressing a drive to save disk space, 13 ways to recover disk space, and finding large files on Windows.