Windows 11 ships with Storage Sense and the classic Disk Cleanup tool, and for a lot of people they’re enough. But if your drive keeps filling up — especially on a laptop with a smaller SSD — you’ve probably noticed those built-in tools plateau, reclaiming a few gigabytes and then shrugging at the other twenty. To really free up space on Windows 11, you need to know what the built-in tools do well, where they stop, and how to safely clear the big stuff they ignore. Here’s the complete, safe playbook.
Step 1: See where the space actually went
Before deleting anything, find the real offenders. Open Settings → System → Storage for a category breakdown. It’s a decent first look, but “Other” and “System & reserved” are vague. To see specific large files and folders, use a disk analyzer that builds a treemap and a descending size list — that’s the fastest way to answer “what’s eating my disk,” and it stops you deleting the wrong thing. See Where Did My Disk Space Go? Find Large Files Fast for OS-by-OS methods.
Step 2: Turn on Storage Sense (the automatic option)
Storage Sense is Windows 11’s built-in janitor. Go to Settings → System → Storage → Storage Sense and enable it. It can automatically:
- Empty the Recycle Bin after a set number of days.
- Delete files in your Downloads folder that haven’t changed in N days (be careful — see below).
- Clear temporary files apps no longer need.
Safety caveat: the “delete Downloads older than X days” option is convenient but blunt — it doesn’t know which old downloads you still want. If you keep installers, reference docs, or media in Downloads, either leave that toggle off or set a long interval, and review before trusting it.
Step 3: Clear temporary files
Windows accumulates temp files from installers, updates, and apps. Go to Settings → System → Storage → Temporary files, review the checklist, and clean. Common safe items:
- Windows Update Cleanup — old update files after an update succeeds.
- Delivery Optimization Files — cached update downloads shared on your network.
- Temporary Internet Files and Thumbnails — regenerated on demand.
- Recycle Bin — empties it (make sure nothing there is wanted).
You can also clear the user temp folder directly. Press Win + R, type %temp%, and delete what’s inside:
%LocalAppData%\TempSafety caveat: clear temp files with apps closed. Files currently in use won’t delete (Windows will skip them, which is fine). Don’t delete the Temp folder itself — just its contents.
Step 4: Understand the built-in tools’ limits
Here’s where Disk Cleanup and Storage Sense stop being enough:
| Tool | Great at | Doesn’t touch |
|---|---|---|
| Storage Sense | Recycle Bin, temp, old Downloads | App caches, dev artifacts, duplicates |
Disk Cleanup (cleanmgr) | Update cleanup, system files, temp | node_modules, Docker, WSL, package caches |
| Settings → Storage | Category overview, temp files | Per-file detail, duplicates |
The space they miss is often the largest space: application caches buried in %LocalAppData%, developer build artifacts, Docker/WSL virtual disks, and duplicate files. That’s what the rest of this guide covers.
Step 5: WinSxS — leave the folder alone, clean it the right way
Open File Explorer, look at C:\Windows\WinSxS, and you’ll see something huge — often 8–15 GB. Your instinct is to delete it. Don’t. WinSxS (the “component store”) holds the files Windows needs to service, update, uninstall, and repair itself. Deleting or manually pruning it can break Windows Update and leave your system unrepairable. Also, its reported size is misleading — many files are hardlinks counted more than once, so it’s smaller on disk than Explorer claims.
The safe way to shrink it is Microsoft’s own maintenance command, which removes genuinely superseded components:
# Run in an elevated (Administrator) PowerShell/Command Prompt
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
Dism.exe /Online /Cleanup-Image /StartComponentCleanupThe first command reports whether cleanup is recommended; the second performs it safely. Never del or rmdir inside WinSxS — let DISM decide what’s removable.
Step 6: The big stuff the built-in tools ignore
Application caches
Apps stash gigabytes under %LocalAppData%. Browsers (...\Google\Chrome\User Data\Default\Cache), Electron apps (Slack, Teams, Discord), and media apps are common offenders. These Cache and Code Cache subfolders are safe to clear — but clear the cache subfolder, never the profile folder that holds your logins and settings.
Developer artifacts
If you write code, this is usually the biggest win. node_modules folders, bin/obj from .NET builds, target/ from Rust/Java, and package caches (npm, NuGet, pip) can total tens of gigabytes. They all regenerate from your source and lockfiles. There’s a complete, cross-platform treatment in A Developer’s Guide to Reclaiming Disk Space.
WSL and Docker virtual disks
WSL 2 and Docker Desktop store everything inside growing virtual hard disk files (.vhdx). Critically, these files grow but don’t automatically shrink when you delete data inside them. After clearing images or containers, you may need to compact the disk. With Docker/WSL fully shut down:
wsl --shutdown
# then, for a specific distro's disk, from an elevated prompt:
Optimize-VHD -Path "C:\path\to\ext4.vhdx" -Mode FullOptimize-VHD requires the Hyper-V module; on editions without it, diskpart’s compact vdisk is the alternative. Safety caveat: only compact a .vhdx when its VM/distro is stopped, and prune data inside Docker (docker system prune) first.
A safe Windows 11 cleanup checklist
- Scan first with a treemap/size-list analyzer to find real offenders.
- Enable Storage Sense but set Downloads deletion conservatively (or off).
- Clear temporary files via Settings and
%temp%, with apps closed. - Shrink WinSxS with DISM only — never delete inside
C:\Windows\WinSxS. - Clear app caches at the
Cachesubfolder, never the profile. - Reclaim dev artifacts (
node_modules,bin/obj, package caches). - Prune then compact Docker/WSL virtual disks.
- Never delete inside
C:\Windows,C:\Program Files, orC:\ProgramData(except explicit temp). These are protected for a reason.
A general command-line caution: PowerShell’s Remove-Item -Recurse -Force is unforgiving and bypasses the Recycle Bin. One wrong path deletes everything under it with no undo. Prefer the GUI tools and DISM for system areas, and when scripting a delete, test the path with Get-ChildItem first.
How Declutter helps on Windows
The built-in tools are safe but shallow; manual cleanup is deep but risky. Declutter is built to be both deep and safe. It scans your drive, then its safety engine surfaces exactly the space the OS tools miss — app caches (never profiles), dev build artifacts, package-manager caches, temp files, duplicates, and the Recycle Bin — each with a plain-language reason it’s safe to remove. Protected areas like C:\Windows, Program Files, ProgramData, the pagefile, and your Roaming app data are deny-by-default and can’t be selected.
Every deletion is a reviewed phase: you preview exact paths and total size, approve, and files move to a recoverable quarantine first, so a full undo is always available. It suggests; it never surprises.
The bottom line
To free up space on Windows 11, use Storage Sense and Disk Cleanup for the easy wins, shrink WinSxS only with DISM, and then go after the large stuff the built-in tools ignore — app caches, developer artifacts, and Docker/WSL virtual disks (remembering to compact them). Scan before you delete, keep away from C:\Windows and Program Files, and prefer reversible deletes. That combination reliably reclaims far more than Disk Cleanup alone — often 20–60 GB on a developer machine.
Want the deep clean without the risk? Try Declutter — it finds what Windows tools miss and removes it quarantine-first with full undo. Subscribe to our newsletter for more Windows and cross-platform cleanup guides.