Where Chrome keeps its cache — the exact paths
Everything Chrome stores for you lives under %LOCALAPPDATA%\Google\Chrome\User Data, and the first profile is simply called Default. Inside it sit three cache folders: Cache with its Cache_Data subfolder (downloaded page assets), Code Cache (compiled JavaScript) and GPUCache (cached shaders and graphics data). All three are safe to empty and all three are recreated automatically — they are caches by definition, not personal data.
The size is worth a look before you delete: right-click the Cache folder → Properties. On a machine with daily browsing, the main cache commonly grows to hundreds of megabytes, and heavy streaming or web-app use pushes it into gigabytes. Each additional Chrome profile repeats the same trio of folders under its own name, so five profiles can mean five separate piles.
- %LOCALAPPDATA%\Google\Chrome\User Data\Default\Cache — the first profile's main cache; its files live in the Cache_Data subfolder
- %LOCALAPPDATA%\Google\Chrome\User Data\Default\Code Cache — compiled JavaScript, safe to empty alongside the main cache
- %LOCALAPPDATA%\Google\Chrome\User Data\Default\GPUCache — cached shader and graphics data
- Profile 1, Profile 2 … — every additional profile repeats the same cache set under User Data
- %TEMP% is a different story: Chrome's installers and crash dumps land there, not its page cache
Deleting the cache manually, step by step
Close Chrome completely first — background apps can keep chrome.exe alive with no window in sight, so check the tray or Task Manager if in doubt. Press Win+R (or focus File Explorer's address bar), paste %LOCALAPPDATA%\Google\Chrome\User Data\Default\Cache and press Enter. Open the Cache folder, go into Cache_Data, press Ctrl+A to select everything and Shift+Del to delete without a trip to the Recycle Bin.
If Windows refuses with “file in use”, Chrome is still running somewhere — end it in Task Manager and try again. On the next launch Chrome recreates Cache_Data on its own, and pages start repopulating it as you browse. First visits to familiar sites load a bit slower once; afterwards everything is back to normal speed.
What is safe to delete — and what never to touch
Safe: the contents of Cache, Code Cache and GPUCache, in every profile. Deleting them does not sign you out — cookies live in the Network folder and stay untouched — and bookmarks, passwords, history and extensions are stored elsewhere in the same profile tree. The built-in dialog (Ctrl+Shift+Del → “Cached images and files”) does the same job without leaving the browser, so manual deletion mostly earns its keep when Chrome misbehaves or refuses to start.
Never delete the User Data or Default folders themselves: that wipes profiles, saved passwords and bookmarks in one move, and no amount of cache-clearing justifies it. A fresh browser is what the reset at chrome://settings/reset is for — it removes junk while keeping your logins. For the routine version of this chore — emptying Chrome's cache files across profiles on a schedule, cookies and passwords untouched — Kleaner PRO automates it.
Questions and Answers
Where is the Chrome cache folder in Windows 11?
In %LOCALAPPDATA%\Google\Chrome\User Data\Default\Cache, with the actual files in its Cache_Data subfolder. Extra profiles repeat the same structure as Profile 1, Profile 2 and so on under User Data.
Is it safe to delete the Chrome cache folder?
Yes — the contents of Cache, Code Cache and GPUCache can go; Chrome recreates them on the next launch. You stay logged in, because cookies live in a separate Network folder.
Why can't I delete files in Chrome's cache folder?
Because Chrome is still running — often invisibly, via background apps. Quit it from the tray or end the chrome.exe processes in Task Manager, then delete again.
Know what is included before you buy.
The one-time 30-minute trial covers core tools. PRO-labelled features stay locked until a paid license is activated.
Read next
Write to us: [email protected]