What JClean finds
This page is built from the same 72 rules the app uses, so it's always accurate. Rules marked "Developer" appear in Developer mode.
Android
-
Android caches
DeveloperIn Everyday mode: Temporary files from Android tools
Caches the Android tools keep.
If cleaned: They're rebuilt as the tools run.
Safe to clean Deleted permanently
Where it looks
- {home}/.android/cache
-
Android emulators (AVDs)
DeveloperIn Everyday mode: Simulated Android phones
Each Android emulator and the data on it.
If cleaned: The emulator and its data are removed. You can create it again in Android Studio.
Needs review Deleted permanently
Where it looks
- {home}/.android/avd/*
-
Android system images
DeveloperIn Everyday mode: Android versions for emulators
Android versions downloaded to run emulators.
If cleaned: Android Studio downloads them again when an emulator needs one.
Needs review Deleted permanently
Where it looks
- {localAppData}/Android/Sdk/system-images/*
-
Old Android Studio caches and logs
DeveloperIn Everyday mode: Leftovers from old Android Studio versions
Caches and logs from Android Studio versions you've upgraded from. The newest is kept.
If cleaned: Nothing: those versions aren't used anymore.
Safe to clean Deleted permanently
Where it looks
- {localAppData}/Google/AndroidStudio*
Browser caches
-
Brave cache
In Everyday mode: Brave's saved web data
Copies of web pages, scripts and images Brave keeps to load sites faster.
If cleaned: The browser downloads pages and images again as you visit sites. You stay signed in, and your history, bookmarks and passwords aren't touched.
Safe to clean Deleted permanently
Where it looks
- {localAppData}/BraveSoftware/Brave-Browser/User Data/*/Cache
- {localAppData}/BraveSoftware/Brave-Browser/User Data/*/Code Cache
- {localAppData}/BraveSoftware/Brave-Browser/User Data/*/GPUCache
- {localAppData}/BraveSoftware/Brave-Browser/User Data/*/Service Worker/CacheStorage
-
Chrome cache
In Everyday mode: Chrome's saved web data
Copies of web pages, scripts and images Chrome keeps to load sites faster.
If cleaned: The browser downloads pages and images again as you visit sites. You stay signed in, and your history, bookmarks and passwords aren't touched.
Safe to clean Deleted permanently
Where it looks
- {localAppData}/Google/Chrome/User Data/*/Cache
- {localAppData}/Google/Chrome/User Data/*/Code Cache
- {localAppData}/Google/Chrome/User Data/*/GPUCache
- {localAppData}/Google/Chrome/User Data/*/Service Worker/CacheStorage
-
Edge cache
In Everyday mode: Edge's saved web data
Copies of web pages, scripts and images Edge keeps to load sites faster.
If cleaned: The browser downloads pages and images again as you visit sites. You stay signed in, and your history, bookmarks and passwords aren't touched.
Safe to clean Deleted permanently
Where it looks
- {localAppData}/Microsoft/Edge/User Data/*/Cache
- {localAppData}/Microsoft/Edge/User Data/*/Code Cache
- {localAppData}/Microsoft/Edge/User Data/*/GPUCache
- {localAppData}/Microsoft/Edge/User Data/*/Service Worker/CacheStorage
-
Firefox cache (cache2)
In Everyday mode: Firefox's saved web data
Copies of web pages and images Firefox keeps to load sites faster.
If cleaned: The browser downloads pages and images again as you visit sites. You stay signed in, and your history, bookmarks and passwords aren't touched.
Safe to clean Deleted permanently
Where it looks
- {localAppData}/Mozilla/Firefox/Profiles/*/cache2
-
Opera cache
In Everyday mode: Opera's saved web data
Copies of web pages, scripts and images Opera keeps to load sites faster.
If cleaned: The browser downloads pages and images again as you visit sites. You stay signed in, and your history, bookmarks and passwords aren't touched.
Safe to clean Deleted permanently
Where it looks
- {localAppData}/Opera Software/Opera Stable/Cache
- {localAppData}/Opera Software/Opera GX Stable/Cache
Build caches
-
Electron, Composer and node-gyp caches
DeveloperIn Everyday mode: Temporary files from developer tools
Downloads cached by Electron, Composer and node-gyp.
If cleaned: They're downloaded again when needed.
Safe to clean Deleted permanently
Where it looks
- {localAppData}/electron/Cache
- {localAppData}/Composer
- {localAppData}/node-gyp/Cache
-
Go build cache
DeveloperIn Everyday mode: Build files (Go)
Compiled packages Go keeps to make builds faster.
If cleaned: The next build is slower while Go fills the cache again.
Safe to clean Cleared with go clean -cache
Where it looks
- {localAppData}/go-build
-
Playwright and Puppeteer browsers
DeveloperIn Everyday mode: Browsers downloaded for testing
Browser builds downloaded by Playwright and Puppeteer for automated tests.
If cleaned: They're downloaded again the next time tests need them.
Needs review Deleted permanently
Where it looks
- {localAppData}/ms-playwright/*
- {home}/.cache/puppeteer/*
Chat and media apps
-
Discord cache
In Everyday mode: Discord's saved data
Images and page data Discord keeps so chats load faster.
If cleaned: The app downloads what it needs again. Your messages, files and settings aren't touched.
Safe to clean Deleted permanently
Where it looks
- {appData}/discord/Cache
- {appData}/discord/Code Cache
- {appData}/discord/GPUCache
- {appData}/discord/Service Worker/CacheStorage
-
Microsoft Teams cache
In Everyday mode: Teams' saved data
Images and page data Microsoft Teams keeps so chats and meetings load faster.
If cleaned: The app downloads what it needs again. Your messages, files and settings aren't touched.
Safe to clean Deleted permanently
Where it looks
- {appData}/Microsoft/Teams/Cache
- {appData}/Microsoft/Teams/Code Cache
- {appData}/Microsoft/Teams/GPUCache
- {appData}/Microsoft/Teams/Service Worker/CacheStorage
-
Slack cache
In Everyday mode: Slack's saved data
Images, files and page data Slack keeps so conversations load faster.
If cleaned: The app downloads what it needs again. Your messages, files and settings aren't touched.
Safe to clean Deleted permanently
Where it looks
- {appData}/Slack/Cache
- {appData}/Slack/Code Cache
- {appData}/Slack/GPUCache
- {appData}/Slack/Service Worker/CacheStorage
-
Spotify cache (com.spotify.client)
In Everyday mode: Spotify's saved music data
Music and data Spotify keeps on this Mac. Songs downloaded for offline listening may be stored here too, so check before cleaning.
If cleaned: Spotify streams songs again as you play them. Offline downloads may need to be downloaded again. Playlists and settings aren't touched.
Needs review Deleted permanently
Where it looks
- {localAppData}/Spotify/Storage
- {localAppData}/Spotify/Data
Device backups
-
iPhone and iPad backups (MobileSync)
In Everyday mode: iPhone and iPad backups
Full backups of iPhones and iPads made by iTunes or Apple Devices. Each one can be many gigabytes.
If cleaned: The backup moves to the Recycle Bin. Once it's emptied you can't restore that device from it.
Caution Moved to the Recycle Bin
Where it looks
- {appData}/Apple Computer/MobileSync/Backup
- {home}/Apple/MobileSync/Backup
Docker
-
Docker build cache
DeveloperIn Everyday mode: Docker build files
Layers Docker keeps to speed up image builds.
If cleaned: The next build is slower while Docker fills the cache again.
Safe to clean Cleared with docker builder prune -f
Where it looks
- Reported by the tool (docker-build-cache)
-
Docker Desktop disk image (docker_data.vhdx)
DeveloperIn Everyday mode: Docker's storage file
The virtual disk Docker Desktop stores all images, containers and volumes in. Pruning frees space inside it, but the file doesn't shrink on its own.
If cleaned: JClean never removes this file. Clean Docker's images and build cache, then in Docker Desktop use Troubleshoot → Clean / Purge data, or compact the disk with Optimize-VHD, to hand the space back to Windows.
Shown for information Never cleaned
Where it looks
- {localAppData}/Docker/wsl/disk/docker_data.vhdx
- {localAppData}/Docker/wsl/data/ext4.vhdx
-
Unused Docker images
DeveloperIn Everyday mode: Docker images no container uses
Images not used by any container, including ones you pulled and never ran.
If cleaned: Docker downloads or rebuilds an image the next time you need it.
Needs review Cleared with docker image prune -a -f
Where it looks
- Reported by the tool (docker-images)
-
Unused Docker volumes
DeveloperIn Everyday mode: Docker data no container uses
Volumes not attached to any container. They can hold databases and other data you meant to keep.
If cleaned: The data in these volumes is deleted permanently.
Caution Cleared with docker volume prune -f
Where it looks
- Reported by the tool (docker-volumes)
Downloads
-
Old installers in Downloads
Installers, disk images and archives in Downloads that are more than 30 days old. Usually for apps that are already installed.
If cleaned: They move to the Recycle Bin, so you can restore them until you empty it.
Needs review Moved to the Recycle Bin
Where it looks
- {home}/Downloads
Editors and IDEs
-
Cursor caches and logs
DeveloperIn Everyday mode: Temporary files from Cursor
Caches, downloaded extension packages and logs Cursor keeps.
If cleaned: Cursor rebuilds them. Your settings, extensions and projects aren't touched.
Safe to clean Deleted permanently
Where it looks
- {appData}/Cursor/Cache
- {appData}/Cursor/CachedData
- {appData}/Cursor/CachedExtensionVSIXs
- {appData}/Cursor/Code Cache
- {appData}/Cursor/GPUCache
-
JetBrains caches and logs from old versions
DeveloperIn Everyday mode: Leftovers from old JetBrains IDE versions
Caches and logs from IDE versions you've upgraded from. The newest version of each IDE is kept.
If cleaned: Nothing: those versions aren't used anymore.
Safe to clean Deleted permanently
Where it looks
- {localAppData}/JetBrains/*
-
JetBrains settings from old versions
DeveloperIn Everyday mode: Settings from old JetBrains IDE versions
Settings and plugins from IDE versions you've upgraded from. The newest version of each IDE is kept.
If cleaned: They move to the Recycle Bin. Old versions of the IDE lose their settings.
Needs review Moved to the Recycle Bin
Where it looks
- {appData}/JetBrains/*
-
Old editor extension versions
DeveloperIn Everyday mode: Old versions of editor extensions
Older copies of extensions left behind after updates. The newest version of each is kept.
If cleaned: Nothing: the editor uses the newest version.
Safe to clean Deleted permanently
Where it looks
- {home}/.vscode/extensions/*
- {home}/.cursor/extensions/*
- {home}/.windsurf/extensions/*
-
VS Code caches and logs
DeveloperIn Everyday mode: Temporary files from VS Code
Caches, downloaded extension packages and logs VS Code keeps.
If cleaned: VS Code rebuilds them. Your settings, extensions and projects aren't touched.
Safe to clean Deleted permanently
Where it looks
- {appData}/Code/Cache
- {appData}/Code/CachedData
- {appData}/Code/CachedExtensionVSIXs
- {appData}/Code/Code Cache
- {appData}/Code/GPUCache
-
Windsurf caches and logs
DeveloperIn Everyday mode: Temporary files from Windsurf
Caches, downloaded extension packages and logs Windsurf keeps.
If cleaned: Windsurf rebuilds them. Your settings, extensions and projects aren't touched.
Safe to clean Deleted permanently
Where it looks
- {appData}/Windsurf/Cache
- {appData}/Windsurf/CachedData
- {appData}/Windsurf/CachedExtensionVSIXs
- {appData}/Windsurf/Code Cache
- {appData}/Windsurf/GPUCache
Large files
-
Large files unchanged for 90+ days
In Everyday mode: Large files you haven't opened in a while
Files over 1 GB that haven't changed in 90 days. Found by a full scan.
If cleaned: They move to the Recycle Bin, so you can put them back until you empty it.
Needs review Moved to the Recycle Bin
Where it looks
- {home}
Logs
-
Crash dumps (%LOCALAPPDATA%\CrashDumps)
In Everyday mode: Crash reports
Reports saved when an app quits unexpectedly.
If cleaned: Old reports are gone. New ones are saved if an app crashes again.
Safe to clean Deleted permanently
Where it looks
- {localAppData}/CrashDumps
-
Gradle daemon logs
DeveloperIn Everyday mode: Build tool logs (Gradle)
Logs written by Gradle's background build process.
If cleaned: Gradle starts new logs.
Safe to clean Deleted permanently
Where it looks
- {home}/.gradle/daemon
Machine learning models
-
Hugging Face hub cache
DeveloperIn Everyday mode: Downloaded AI models (Hugging Face)
Models and datasets downloaded by Hugging Face libraries. Often several gigabytes each.
If cleaned: Code that uses these models downloads them again, which can take a long time.
Needs review Deleted permanently
Where it looks
- {home}/.cache/huggingface/hub
-
Local LLM models (Ollama, LM Studio)
DeveloperIn Everyday mode: Downloaded AI models (Ollama, LM Studio)
Language models downloaded to run on this Mac. Each can be many gigabytes.
If cleaned: You'll need to download a model again before using it.
Needs review Deleted permanently
Where it looks
- {home}/.ollama/models
- {home}/.lmstudio/models
- {home}/.cache/lm-studio/models
Package caches
-
Bun install cache
DeveloperIn Everyday mode: Downloaded packages (Bun)
Copies of packages Bun has downloaded, kept so installs are faster.
If cleaned: Bun downloads them again the next time you install or build. Nothing in your projects changes.
Safe to clean Deleted permanently
Where it looks
- {home}/.bun/install/cache
-
Cargo registry and git checkouts
DeveloperIn Everyday mode: Downloaded packages (Cargo)
Crates Cargo has downloaded, and dependencies fetched from git.
If cleaned: Cargo downloads them again the next time you install or build. Nothing in your projects changes.
Safe to clean Deleted permanently
Where it looks
- {home}/.cargo/registry/cache
- {home}/.cargo/registry/src
- {home}/.cargo/git/checkouts
-
Conda package cache (pkgs)
DeveloperIn Everyday mode: Downloaded packages (Conda)
Package archives and extracted packages Conda keeps after installing them into environments.
If cleaned: Conda removes packages no environment needs. Your environments keep working.
Safe to clean Cleared with conda clean --all -y
Where it looks
- {home}/miniconda3/pkgs
- {home}/anaconda3/pkgs
- {home}/miniforge3/pkgs
-
Dart and Flutter pub cache
DeveloperIn Everyday mode: Downloaded packages (Flutter)
Packages downloaded by Dart and Flutter. Globally activated tools live here too.
If cleaned: Packages are downloaded again on the next pub get. Global tools must be activated again.
Needs review Cleared with dart pub cache clean --force
Where it looks
- {localAppData}/Pub/Cache
-
Go module cache
DeveloperIn Everyday mode: Downloaded packages (Go)
Go modules downloaded for your projects. Go makes these read-only, so its own command removes them.
If cleaned: Go downloads them again the next time you install or build. Nothing in your projects changes.
Safe to clean Cleared with go clean -modcache
Where it looks
- {home}/go/pkg/mod
-
Gradle caches
DeveloperIn Everyday mode: Downloaded packages (Gradle)
Dependencies and build outputs Gradle keeps between builds.
If cleaned: Gradle downloads them again the next time you install or build. Nothing in your projects changes.
Safe to clean Deleted permanently
Where it looks
- {home}/.gradle/caches
-
Maven repository (.m2)
DeveloperIn Everyday mode: Downloaded packages (Maven)
Every library Maven has downloaded. May also hold artifacts you installed locally with mvn install.
If cleaned: Maven downloads libraries again on the next build. Locally installed artifacts must be rebuilt.
Needs review Deleted permanently
Where it looks
- {home}/.m2/repository
-
npm cache
DeveloperIn Everyday mode: Downloaded packages (npm)
Copies of every package npm has downloaded, kept so installs are faster.
If cleaned: npm downloads packages again the next time you install them. Nothing in your projects changes.
Safe to clean Cleared with npm cache clean --force
Where it looks
- {localAppData}/npm-cache/_cacache
-
NuGet caches (global packages, HTTP cache)
DeveloperIn Everyday mode: Downloaded packages (.NET)
Packages NuGet has downloaded for .NET projects, shared by every project on this PC.
If cleaned: Packages are downloaded again the next time a project restores. Nothing in your projects changes.
Safe to clean Cleared with dotnet nuget locals all --clear
Where it looks
- {home}/.nuget/packages
- {localAppData}/NuGet/v3-cache
- {localAppData}/NuGet/plugins-cache
-
pip cache
DeveloperIn Everyday mode: Downloaded packages (pip)
Copies of Python packages pip has downloaded.
If cleaned: pip downloads them again the next time you install or build. Nothing in your projects changes.
Safe to clean Deleted permanently
Where it looks
- {localAppData}/pip/Cache
-
pnpm store
DeveloperIn Everyday mode: Downloaded packages (pnpm)
pnpm's shared store of packages. Projects link to it, so only unused packages can be removed.
If cleaned: pnpm removes packages no project uses. Projects keep working.
Safe to clean Cleared with pnpm store prune
Where it looks
- {localAppData}/pnpm/store
-
Poetry cache
DeveloperIn Everyday mode: Downloaded packages (Poetry)
Python packages and metadata Poetry has downloaded.
If cleaned: Poetry downloads them again the next time you install or build. Nothing in your projects changes.
Safe to clean Deleted permanently
Where it looks
- {localAppData}/pypoetry/Cache
-
uv cache
DeveloperIn Everyday mode: Downloaded packages (uv)
Python packages and builds uv keeps to make installs fast.
If cleaned: uv downloads them again the next time you install or build. Nothing in your projects changes.
Safe to clean Cleared with uv cache clean
Where it looks
- {localAppData}/uv/cache
-
Yarn cache
DeveloperIn Everyday mode: Downloaded packages (Yarn)
Copies of packages Yarn has downloaded, kept so installs are faster.
If cleaned: Yarn downloads them again the next time you install or build. Nothing in your projects changes.
Safe to clean Deleted permanently
Where it looks
- {localAppData}/Yarn/Cache
- {home}/.yarn/berry/cache
Project build folders
-
.NET bin and obj folders
DeveloperIn Everyday mode: Build output in old .NET projects
Compiled output .NET writes inside a project.
If cleaned: The next build recreates them.
Safe to clean Deleted permanently
Where it looks
- bin next to *.csproj, *.sln
- obj next to *.csproj, *.sln
-
Build output (dist, build)
DeveloperIn Everyday mode: Build output in old projects
Folders a build writes its output to. Some projects keep hand-made files here, so check before cleaning.
If cleaned: Running the build again recreates them. Anything that wasn't generated by the build is lost.
Needs review Deleted permanently
Where it looks
- dist next to package.json
- build next to package.json
-
Cargo target folders
DeveloperIn Everyday mode: Build output in old Rust projects
Everything Cargo compiles for a project. Often the biggest folder in it.
If cleaned: The next build recompiles everything, which can take a while.
Safe to clean Deleted permanently
Where it looks
- target next to Cargo.toml
-
CMake build folders
DeveloperIn Everyday mode: Build output in old C and C++ projects
Build folders CMake generates. Some projects keep other files in build, so check first.
If cleaned: The next CMake configure and build recreates them.
Needs review Deleted permanently
Where it looks
- build next to CMakeLists.txt
- cmake-build-* next to CMakeLists.txt
-
Dart tool folders (.dart_tool)
DeveloperIn Everyday mode: Build caches in old Flutter projects
Caches Dart and Flutter keep inside a project.
If cleaned: The next pub get or build recreates them.
Safe to clean Deleted permanently
Where it looks
- .dart_tool next to pubspec.yaml
-
Flutter build folders
DeveloperIn Everyday mode: Build output in old Flutter projects
Output Flutter writes to the build folder.
If cleaned: The next build recreates it.
Needs review Deleted permanently
Where it looks
- build next to pubspec.yaml
-
Framework build caches (.next, .nuxt, .turbo…)
DeveloperIn Everyday mode: Build caches in old projects
Caches that JavaScript frameworks and bundlers write inside a project.
If cleaned: The next build or dev server run recreates them, a little slower the first time.
Safe to clean Deleted permanently
Where it looks
- .next next to package.json
- .nuxt next to package.json
- .turbo next to package.json
- .parcel-cache next to package.json
- .svelte-kit next to package.json
- .angular/cache next to package.json
- .expo next to package.json
-
Gradle build folders
DeveloperIn Everyday mode: Build output in old Gradle projects
Output Gradle writes to the build folder. Some projects keep other files here, so check first.
If cleaned: The next build recreates it. Anything that wasn't generated by the build is lost.
Needs review Deleted permanently
Where it looks
- build next to build.gradle, build.gradle.kts
-
Gradle project caches (.gradle)
DeveloperIn Everyday mode: Build caches in old Gradle projects
Caches Gradle keeps inside a project.
If cleaned: The next build recreates them.
Safe to clean Deleted permanently
Where it looks
- .gradle next to build.gradle, build.gradle.kts
-
Maven target folders
DeveloperIn Everyday mode: Build output in old Java projects
Compiled classes and packages Maven writes inside a project.
If cleaned: The next build recreates them.
Safe to clean Deleted permanently
Where it looks
- target next to pom.xml
-
node_modules
DeveloperIn Everyday mode: Installed packages in old projects
Packages installed for a JavaScript project. Recreated with npm, pnpm, Yarn or Bun install.
If cleaned: Run your package manager's install command before working on the project again.
Safe to clean Deleted permanently
Where it looks
- node_modules next to package.json
-
Python caches (__pycache__, .pytest_cache…)
DeveloperIn Everyday mode: Python caches in old projects
Compiled files and test caches Python tools write inside a project.
If cleaned: Python recreates them the next time the code runs.
Safe to clean Deleted permanently
Where it looks
- __pycache__ next to pyproject.toml, requirements.txt, setup.py
- .pytest_cache next to pyproject.toml, requirements.txt, setup.py
- .mypy_cache next to pyproject.toml, requirements.txt, setup.py
- .tox next to pyproject.toml, requirements.txt, setup.py
-
Virtual environments (.venv, venv)
DeveloperIn Everyday mode: Python environments in old projects
Python packages installed for one project. Recreated from its requirements.
If cleaned: Recreate the environment and install the requirements before working on the project again.
Safe to clean Deleted permanently
Where it looks
- .venv next to pyproject.toml, requirements.txt, setup.py
- venv next to pyproject.toml, requirements.txt, setup.py
SDKs and runtimes
-
Old Gradle wrapper versions
DeveloperIn Everyday mode: Old versions of Gradle
Gradle versions downloaded by project wrappers. The newest one is kept.
If cleaned: A project that needs an old version downloads it again on its next build.
Safe to clean Deleted permanently
Where it looks
- {home}/.gradle/wrapper/dists/*
-
Old Node.js versions (nvm, Volta, fnm)
DeveloperIn Everyday mode: Old versions of Node.js
Node.js versions installed by a version manager. The newest one is kept.
If cleaned: Projects that need an old version will ask you to install it again.
Needs review Deleted permanently
Where it looks
- {appData}/nvm/v*
- {localAppData}/Volta/tools/image/node/*
- {appData}/fnm/node-versions/*
-
Visual Studio installer cache (ProgramData\Microsoft\VisualStudio\Packages)
DeveloperIn Everyday mode: Visual Studio's installer files
Installer packages Visual Studio keeps after installing or updating, so it can repair itself without downloading.
If cleaned: Visual Studio keeps working. Repairing or modifying it downloads the packages again. Needs administrator approval.
Needs review Deleted permanently
Where it looks
- {env:ProgramData}/Microsoft/VisualStudio/Packages
System files
-
Hibernation file (hiberfil.sys)
In Everyday mode: Hibernation file
Where Windows saves what's in memory when the PC hibernates or starts with Fast Startup.
If cleaned: JClean never removes this file. If you never hibernate, you can turn hibernation off to free it: run "powercfg /h off" in an administrator terminal.
Shown for information Never cleaned
Where it looks
- {env:SystemDrive}/hiberfil.sys
-
Page file (pagefile.sys, swapfile.sys)
In Everyday mode: Memory overflow file
Space Windows uses as extra memory when the PC runs low. Windows sizes it automatically.
If cleaned: JClean never removes this file. Windows needs it; leave its size on automatic unless you know you need something else.
Shown for information Never cleaned
Where it looks
- {env:SystemDrive}/pagefile.sys
- {env:SystemDrive}/swapfile.sys
-
WSL distribution disks (ext4.vhdx)
DeveloperIn Everyday mode: Linux (WSL) storage files
The virtual disks of Linux distributions installed with WSL. Deleting files inside Linux doesn't make these files smaller.
If cleaned: JClean never removes these files. To reclaim space, run "wsl --shutdown", then compact the disk with Optimize-VHD, or "wsl --manage <distro> --set-sparse true" on recent Windows.
Shown for information Never cleaned
Where it looks
- {localAppData}/Packages/*/LocalState/ext4.vhdx
- {localAppData}/wsl/*/ext4.vhdx
Temporary files
-
Temporary files (%TEMP%)
In Everyday mode: Temporary files
Files apps and installers create while they work and often forget to remove.
If cleaned: Anything an open app is still using is skipped. Everything else is gone for good.
Safe to clean Deleted permanently
Where it looks
- {temp}
- {localAppData}/Temp
Trash
-
Recycle Bin
Things you've deleted. They still take up space until the Recycle Bin is emptied.
If cleaned: These items are deleted permanently and can't be restored.
Safe to clean Deleted permanently
Where it looks
- {env:SystemDrive}/$Recycle.Bin/S-1-5-*
Windows updates
-
Component store cleanup (DISM /StartComponentCleanup)
In Everyday mode: Old versions of Windows components
Older copies of Windows files that updates have replaced. Windows can't say how much space this frees until it's done.
If cleaned: Windows removes the old copies, so updates installed so far can't be uninstalled. It can take several minutes and needs administrator approval.
Needs review Cleared with Dism /Online /Cleanup-Image /StartComponentCleanup
Where it looks
- Reported by the tool (component-store)
-
Delivery Optimization cache
In Everyday mode: Shared update files
Update pieces Windows keeps so it can share them with other PCs on your network.
If cleaned: Windows cleans this up on its own over time. Clearing it now needs administrator approval.
Safe to clean Cleared with powershell -NoProfile -NonInteractive -Command Delete-DeliveryOptimizationCache -Force
Where it looks
- Reported by the tool (delivery-optimization)
-
Previous Windows installation (C:\Windows.old)
In Everyday mode: Your previous version of Windows
A copy of the Windows you had before the last major upgrade, kept so you can go back.
If cleaned: You can no longer go back to your previous version of Windows, and any files left in it are gone. Windows' Disk Cleanup removes it, which can take several minutes and needs administrator approval.
Caution Cleared with powershell -NoProfile -NonInteractive -Command Set-ItemProperty -LiteralPath 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches\Previous Installations' -Name StateFlags4242 -Type DWord -Value 2; Start-Process -FilePath cleanmgr.exe -ArgumentList '/sagerun:4242' -Wait
Where it looks
- {env:SystemDrive}/Windows.old
-
Windows Update downloads (SoftwareDistribution\Download)
In Everyday mode: Downloaded Windows updates
Update files Windows downloaded before installing them.
If cleaned: Updates that are already installed aren't affected. If an update is still waiting to install, Windows downloads it again. Needs administrator approval.
Needs review Deleted permanently
Where it looks
- {env:SystemRoot}/SoftwareDistribution/Download