Rebuildable storage
A cache can usually be recreated, but an application profile may also contain sign-ins, conversations, offline files, settings, or project data. SizeTrend keeps those cases separate so a large folder name is not mistaken for permission to erase it.
Scan the Windows drive and open the Overview pane. Known temporary files and rebuildable caches appear under Space You Can Reclaim. Each row explains what was recognized, how much allocated space it uses, and what action SizeTrend can safely offer.
Use the row action instead of deleting the parent folder in Explorer. The action may preserve the cache root, call a supported command, or show a review when SizeTrend cannot prove that every file is disposable.
Chrome, Edge, and Firefox caches contain downloaded pages, scripts, images, and startup data that the browser can fetch again. Close the browser first, then let SizeTrend clean only the recognized cache folders.
IndexedDB databases, Local Storage, service workers, offline site content, cookies, and profile data can preserve sign-ins or application files. SizeTrend lists large persistent site data for review and does not treat it as ordinary browser cache.
SizeTrend recognizes rebuildable cache data from Teams, Slack, Discord, Zoom, Visual Studio Code, Claude Desktop, Kiro, Cursor, and Spotify, among others. Close the owning application so files are not being written or held open during cleanup.
Only known cache locations are included. Conversations, settings, extensions, sessions, account state, offline Spotify downloads, and other persistent data remain separate or are shown for review.
Delivery Optimization, Microsoft Store cache, component storage, previous Windows installations, and registered Windows cleanup categories have their own supported mechanisms. SizeTrend opens or runs the appropriate Windows operation instead of deleting protected files directly.
The same rule applies to restore points and other System Volume Information data. SizeTrend can measure or identify the category, but Windows decides what can be removed safely.
npm, NuGet, and pip caches contain packages and metadata that can be downloaded again. SizeTrend asks the package manager to clear its managed cache when the tool is available. Active projects and environments are not removed.
Downloaded PDB and image caches are cleaned only when the location is configured or standard and has the expected symbol-server marker. A folder that merely resembles a symbol store is left for review because it may contain private symbols.
Windows and applications can keep temporary files locked. A cleanup may therefore remove most of a cache while reporting files that were retained. SizeTrend can name an owning application when Windows provides that information.
Close the reported application and try again only if the remaining space matters. Refresh the scan afterward to measure what was actually removed. Do not keep escalating to manual deletion just because a few in-use files remain.
Clean the cache, not the whole profile.
SizeTrend narrows cleanup to data it can identify and leaves persistent storage for review.