Slack Space
Also known as: file slack space, disk slack, slack space
Slack space is the unused remainder inside the last block a file occupies, left over because filesystems allocate whole blocks. It is space reserved by a file but not filled with its data, and it accumulates across many small files.
- Slack space is the unused tail of the last block a file occupies, caused by whole-block allocation.
- It grows with larger block sizes and with the number of small files stored.
- Slack is hidden from logical byte size and only appears as inflated size on disk.
Where slack space comes from
Filesystems allocate storage in fixed-size blocks (clusters). When a file does not fill its final block exactly, the leftover portion of that block is slack space: reserved by the file yet not used by its data. A 5 KB file on a volume with 4 KB blocks needs two blocks (8 KB), leaving roughly 3 KB of slack in the second block.
Slack space is a direct consequence of block size and the rounding it imposes. The larger the block size relative to your files, the more slack each file tends to carry, which is why volumes tuned for large media can waste more space on small files.
Why it wastes storage at scale
A single file's slack is small, but multiply it across thousands of caches, thumbnails, logs, and message fragments and the wasted space becomes significant. This overhead is invisible in a file's reported byte size and only shows up when you compare logical size to actual size on disk.
You cannot eliminate slack space without changing the filesystem layout, but you can reduce its impact by removing the high-count clutter that generates it. A cleaner like Cleanor focuses on duplicate photos, redundant downloads, and large files, so freeing whole blocks recovers real capacity instead of chasing per-file overhead.