Fragmentation
Also known as: file fragmentation, disk fragmentation, fragmented files
Fragmentation is when the data for a single file is scattered across non-contiguous physical locations on a storage device, instead of sitting in one continuous run. It builds up as files are repeatedly created, grown, and deleted, leaving a patchwork of free gaps.
- Fragmentation = one file's data stored in scattered, non-contiguous blocks rather than one continuous run.
- On flash storage (eMMC/UFS/SSD) there is no seek penalty, so the performance impact is minor and manual defrag is unneeded.
- Keeping free space and clearing junk reduces fragmentation more effectively than any defrag step on a phone.
Why fragmentation happens
When a file system writes a file, it asks for free space to hold the data. On a fresh, mostly empty volume it can usually place the whole file in one contiguous run of blocks. Over time, as files are deleted and new ones written, the free space breaks into a patchwork of small gaps. When a new file is larger than any single gap, the file system has to split it across several non-contiguous locations — that file is now fragmented.
Appending to existing files makes this worse. If a file grows after the blocks immediately after it are already taken, the new data must go elsewhere, leaving the file in two or more pieces. Databases, logs, and media files that are edited in place are common sources. This is also why a device that has been near-full and heavily churned tends to fragment faster than one with lots of free headroom.
Does it still matter on phones and SSDs?
On spinning hard drives, fragmentation hurt performance because the read head had to physically seek between scattered locations. On the flash storage (eMMC, UFS, SSD) used in modern phones and computers, there is no seek penalty — any block can be read in roughly constant time — so the classic slowdown is far smaller and manual defragmentation is generally unnecessary and can even waste write cycles.
Modern file systems also actively avoid fragmentation. APFS on iOS/macOS and F2FS (designed for flash) on many Android devices use allocation strategies and copy-on-write that keep most files reasonably contiguous. The remaining concern is logical: extreme fragmentation can increase metadata overhead and the number of I/O operations, which is one reason keeping free space available matters more than chasing a low fragmentation number.
What this means for storage cleanup
You can't directly 'defragment' an iPhone or a typical Android phone — the OS manages block placement and doesn't expose it. What you can do is reduce the churn and pressure that cause fragmentation: clear out junk files and stale app cache, remove duplicate photos and large unused media, and avoid running the device constantly at 95–100% full. More free space gives the file system room to place new files contiguously.
Cleanor helps on the practical side: it finds reclaimable space (caches, duplicate and similar photos, large videos) so the volume has breathing room. The flash controller and file system handle the low-level block placement; your job is simply to stop the device from running so full that every write has to be squeezed into scattered gaps.