Defragging an SSD: The Myth That Refuses to Die

Why fragmentation tortured hard drives but not flash

On a mechanical drive, reading a file split into 500 fragments means 500 physical head trips, each costing milliseconds. Defragmentation was invented to collapse those trips into one clean sequential read, and on spinning platters the payoff was real and measurable. An SSD has no heads and no platters: every block answers in the same fraction of a microsecond, wherever it physically sits. Random and sequential reads run nearly equal on a modern NVMe drive, so the very problem defragmentation solves does not exist on flash.

Fragmentation still happens — Windows just files it under 'who cares'. The file system keeps splitting large files across free blocks as the drive fills, and on an HDD you would feel it. On an SSD the only cost of a fragmented file is a slightly longer list of block addresses, which the controller resolves essentially for free.

What Optimize Drives actually does to an SSD

Open Optimize Drives (dfrgui) and look at the Media type column: Windows knows an SSD from an HDD and treats them differently by design. For SSDs the tool's job is TRIM — telling the controller which blocks are logically deleted so future writes go straight to fresh cells instead of through a read-modify-write cycle. That is real maintenance, it runs on a weekly schedule by default, and pressing the button adds nothing the schedule has not already done. The one apparent exception: with System Restore enabled, Windows runs a traditional defrag pass on SSDs roughly once a month, deliberately, because snapshots break once file fragmentation crosses a threshold. That pass is Microsoft's own engineering trade-off, not a bug in your setup.

• Check the Media type column in Optimize Drives (dfrgui) before running anything.
• Leave the scheduled optimization on — for SSDs it sends TRIM, not a defrag pass.
• Verify TRIM once: in an elevated Command Prompt run fsutil behavior query DisableDeleteNotify — you want 0.
• Ignore third-party suites that defragment every drive they see; 'SSD support' in a 2005-era tool is marketing, not media sensing.
• If System Restore is on, don't panic at the monthly defrag entry in the history — it keeps volume snapshots viable.
• Watch Total Host Writes and TBW in a SMART tool if you care about wear: that number, not fragmentation, is the SSD's real odometer.

The maintenance an SSD actually wants

Flash wears out from writes, not from fragmentation, so the honest checklist is short: keep 10–15 percent of the drive free so the controller has room to shuffle, update the firmware when the vendor ships fixes, and don't store a pagefile-sized panic about it. Consumer drives ship with TBW budgets that most households never approach in a decade of ordinary use. A defrag pass moves every block for zero performance gain — the one 'maintenance' task that spends endurance to buy nothing.

So when the old advice resurfaces in a forum thread, the answer fits in one line: Windows has handled this correctly since 2012. The defragmenter your cousin remembers was a tool for a problem flash does not have.

Questions and Answers

Read next