What this tool helps you work out
A drive rarely becomes full at a convenient time. Windows updates, temporary files, logs, user profiles, databases and pagefile growth can turn a small daily increase into an outage several weeks later.
This calculator divides usable free space by the expected daily growth rate. It is most helpful when the growth rate has been measured over several days rather than guessed from a single reading.
Enter your details
Before you calculate
Do not treat every byte of reported free space as safely usable. Windows and applications need working room for updates, temporary files and recovery operations. Reserve a safety margin first, then calculate from the remaining usable space.
A log may grow slowly for days and then spike during an error. Use a high-growth scenario as well as the ordinary average when the drive supports an important service.
How the estimate is calculated
Days remaining = usable free space ÷ average daily growthIf the calculator includes a reserved-space field, that amount is removed before the division. The estimate assumes growth continues at the same average rate.
Worked example
A Windows server has 120 GB free. You reserve 30 GB so updates and recovery tasks still have room, leaving 90 GB usable. Logs and application data are growing by 2.5 GB per day:
90 GB ÷ 2.5 GB/day = 36 days
That is the planning deadline, not the date to begin acting. Alerting and remediation should start well before the drive reaches the reserved margin.
Common disk-growth mistakes
- Using total free space without a safety reserve.
- Measuring growth across only one quiet day.
- Deleting files without identifying the process that recreates them.
- Ignoring shadow copies, update caches, crash dumps or database transaction logs.
- Watching percentage free on very large disks without also setting an absolute-space alert.
What actually fills a drive
Storage rarely fills because of the things people notice. Documents and photographs accumulate slowly and visibly; the fast growth is usually invisible and automatic.
- Windows Update retains previous versions after a feature update, which can occupy 20 GB or more for ten days before clearing automatically.
- System restore and shadow copies take a configurable share of the drive and quietly hold it.
- Hibernation reserves a file roughly the size of installed memory, so 32 GB of RAM means a 32 GB file sitting permanently on the drive.
- The page file takes several gigabytes more, and grows under memory pressure.
- Browser caches grow to hundreds of megabytes each, multiplied by however many browsers and profiles are in use.
- Cloud sync folders hold a local copy of everything unless configured otherwise — a shared work drive can pull down far more than expected.
- Game installations are the largest single category on many home machines, routinely 100 GB each, with updates that download a full replacement rather than a patch.
- Application caches and logs, particularly from development tools, video editors and anything that keeps a working cache.
An SSD needs free blocks to write efficiently, and one that is nearly full has to shuffle existing data to make room for every write. Performance falls noticeably as a drive passes about 90% full, and the drive's own wear levelling has less room to work, which shortens its life. Keeping 10 to 15% free is not wasted space — it is what keeps the drive fast. Mechanical drives suffer differently but also slow when full, as data ends up on the slower inner tracks.
Reading the trend rather than the snapshot
A drive that is 80% full is not a problem. A drive that was 60% full a month ago and is 80% now is a problem, and that is what this calculator is for — the rate, not the level.
Growth is rarely steady, so a single measurement over a few days can mislead badly in either direction. A week that included a game installation or a feature update overstates the trend; a quiet week understates it. Two or three measurements a week apart give a far more reliable figure than one measurement over a longer period, because they reveal whether the growth is continuous or came in one lump.
Worth distinguishing: a one-off addition, which changes the level and not the rate; steady accumulation from photographs, documents and downloads, which is the real trend; and runaway growth from a log file, a failing backup or a misconfigured cache, which will fill any drive given time and needs finding rather than accommodating.
Recovering space, in order of value
- Storage Sense or Disk Cleanup, including the system files option. Removes previous Windows installations, delivery optimisation files and temporary data. Frequently recovers tens of gigabytes and risks nothing.
- Uninstall what is not used. Sort installed applications by size; games and creative software dominate.
- A visual disk usage tool. Something that maps the drive by size shows immediately where the space went, and reliably finds things nobody would have thought to look for.
- Cloud sync settings. Files On-Demand keeps files in the cloud until opened, which can recover a great deal on a machine syncing a large shared drive.
- Reduce system restore allocation, rather than turning it off. It is worth having when something goes wrong.
- Turn off hibernation if you never use it, recovering a file the size of installed memory. Note that this also disables fast startup.
- Move large libraries to a second drive. Games, video and photograph libraries relocate cleanly, and most games have a built-in way to move an installation without redownloading.
Two things to avoid: registry cleaners, which recover no meaningful space and can break a working system, and deleting anything from Windows or Program Files by hand. Use the uninstaller or the built-in cleanup tools.
Frequently asked questions
How much free space should Windows have?
There is no single percentage for every system. Keep enough space for updates, temporary activity, recovery and the workload's normal growth. Important systems should use monitored thresholds rather than a fixed folklore rule.
Why does free space keep changing?
Windows servicing, browser caches, restore points, pagefiles, logs and application data can all expand and contract.
Can I delete WinSxS to free space?
Do not manually delete the WinSxS folder. Use supported Windows servicing and cleanup tools.
Should I alert on percentage or gigabytes free?
Use both where possible. A percentage works across different drive sizes, while an absolute threshold protects the minimum working space needed by the system.
What if growth is accelerating?
Use the highest recent rate or model separate normal and incident scenarios. A simple average will otherwise overstate the time remaining.
How much free space should I keep on an SSD?
Around 10 to 15% of capacity as a working minimum. SSDs need free blocks to write efficiently, and a nearly full drive has to rearrange existing data before it can write anything new, which is noticeably slower. Free space also gives the drive's wear levelling room to work, which affects how long it lasts. On a 500 GB drive, 50 to 75 GB free is a sensible target.
Why does Windows report less space than the drive's stated capacity?
Two separate reasons that compound. Manufacturers count a gigabyte as 1,000,000,000 bytes while Windows counts 1,073,741,824, so a 1 TB drive shows as roughly 931 GB before anything is on it. Then the recovery partition, the EFI partition and the file system's own structures take a few gigabytes more. Neither is a fault or a shortfall.
Is it bad to fill a drive completely?
Yes, for both performance and stability. Windows needs working space for the page file, temporary files and updates, and a drive with almost nothing left can prevent updates installing, stop applications saving, and in some cases stop the machine booting cleanly. On an SSD the performance penalty arrives well before the drive is actually full.
Should I defragment my SSD?
No. Defragmentation is for mechanical drives, where it reduces physical head movement. An SSD has no moving parts, gains nothing from it, and defragmenting causes unnecessary writes that consume a small amount of its finite write endurance. Windows already handles SSDs correctly by running TRIM instead, and its Optimise Drives tool knows the difference — leave it on its default schedule.
Related Windows and technology tools
References
These sources support the Windows behaviour or command guidance discussed on this page.
External documentation can change. Check the linked source before applying a setting to an important system.