Size vs. Size on Disk: Why Your Files Take More Space Than They Say
Size is the raw byte count of your file as Windows or macOS reports it. Size on Disk is the actual space the file consumes on the drive, rounded up to the nearest allocation unit (cluster). The gap between them is the slack space you never see.
People panic when a 1 GB folder suddenly claims “1.5 GB on disk.” They think something’s wrong or that a virus duplicated data. In reality, your 4 KB cluster just wastes 3 KB on every tiny text file, making the mismatch feel like magic.
Key Differences
Size counts exact bytes; Size on Disk counts blocks. A 1-byte file still occupies an entire 4 KB cluster on NTFS, so Size on Disk reads 4 KB. Smaller cluster sizes (like on exFAT) narrow the gap, but never eliminate it.
Which One Should You Choose?
Look at Size when you care about data transfer, cloud sync limits, or email attachments. Watch Size on Disk when your SSD is nearly full or when copying to a USB stick with large allocation units—because the drive’s real estate is what ultimately runs out.
Examples and Daily Life
Save 5,000 tiny notes in Notepad on a 64 KB-cluster USB: Size = 5 MB, Size on Disk = 320 MB. Zip those notes into one archive and both numbers collapse to ~3 MB, instantly freeing “ghost” space and baffling everyone on the team Slack.
Does formatting with smaller clusters fix the gap?
It shrinks but doesn’t erase it; extremely small clusters hurt performance and increase fragmentation.
Why does macOS show only “Size” and still fill the drive?
macOS hides the on-disk metric in Finder, yet APFS still uses 4 KB blocks—so the same invisible overhead exists.
Can third-party tools reclaim the slack space?
No tool can recover slack inside clusters, but compressing or consolidating files into larger ones reduces the inflated Size on Disk count.