Disk Fragmentation Impact Calculator
Estimate the extra read time fragmentation costs on a spinning hard drive from the file count, fragments per file and seek time — and why SSDs are exempt.
How it works
Extra seeks = files × (fragments per file − 1) · Extra time = extra seeks × seek time · Fragmentation index = (frags − 1) ÷ frags
On a spinning hard drive, reading a file means moving the head to where its data sits; a contiguous file is one smooth read, but a fragmented file scatters across the platter and forces an extra seek for every additional piece. Each seek costs several milliseconds of pure mechanical latency, so multiplying the extra fragments by the seek time estimates the time simply lost to head movement. Solid-state drives have no head and effectively zero seek time, so fragmentation is irrelevant to them — defragmenting an SSD only wastes write endurance.
Worked example
Reading 5,000 files that average 4 fragments each means 5,000 × 3 = 15,000 extra seeks. At 9 ms per seek that is 135,000 ms, or about 135 s of head movement that a defragmented drive would avoid — a fragmentation index of (4−1)/4 = 75%.
Frequently asked questions
Should I defragment an SSD?
No. SSDs have no moving head and access any block in the same time, so fragmentation does not slow reads. Defragmenting one just adds write wear; modern operating systems run TRIM on SSDs instead and skip defragmentation.
Is this an exact time?
It is an estimate of the seek overhead only. Real read time also depends on transfer rate, caching, read-ahead and the operating system, but the seek count is the part fragmentation actually changes, so it captures the effect that defragmenting removes.
What counts as heavy fragmentation?
A fresh, contiguous file is 1 fragment. Files averaging 2–3 fragments are mild; averages above 5–10 on a busy, near-full HDD are heavy and noticeably slow, which is when a defragmentation pass pays off.
Related calculators
This calculator is for educational purposes. Double-check important results before acting on them.