Why each profile has its own cache
A profile in a Chromium browser is a sealed compartment: its own history, cookies, extensions and its own cache. That is by design — two people sharing a PC, or one person splitting work and personal accounts, should not see each other's data. The first profile is always called Default; every additional one gets a folder named Profile 1, Profile 2 and up. Besides those, the User Data folder holds service profiles such as System Profile and Guest Profile — small, but they cache too.
The arithmetic is what turns this into a real cleanup topic. One profile's cache rarely shocks anyone at 300–800 MB, but a family PC with three Chrome profiles, two Edge profiles and a Vivaldi account quietly accumulates multiple gigabytes across folders nobody looks at. Firefox joins the pattern from a different direction: its profiles live in %LOCALAPPDATA%\Mozilla\Firefox\Profiles with a cache2 subfolder each, and about:profiles lists them all.
- Chrome: %LOCALAPPDATA%\Google\Chrome\User Data\<profile>\Cache (plus Code Cache and GPUCache)
- Edge: %LOCALAPPDATA%\Microsoft\Edge\User Data\<profile>\Cache
- Vivaldi: %LOCALAPPDATA%\Vivaldi\User Data\<profile>\Cache
- Yandex Browser: %LOCALAPPDATA%\Yandex\YandexBrowser\User Data\<profile>\Cache
- Brave: %LOCALAPPDATA%\BraveSoftware\Brave-Browser\User Data\<profile>\Cache
- Firefox: %LOCALAPPDATA%\Mozilla\Firefox\Profiles\<profile name>\cache2
Cleaning every profile the safe way
The honest way inside the browser: open the profile switcher, enter each profile and run the usual clear-dialog (Ctrl+Shift+Del in Chrome, Edge, Vivaldi and Brave, with Cached images and files ticked). Tedious with five profiles, but everything stays within the browser's own plumbing. If you prefer working from Explorer, close the browser completely first — Chrome and Edge keep running after the window closes when their background-apps setting is on, so quit via the menu's Exit command or the tray icon.
Then open each browser's User Data folder, step into every Default and Profile N folder and delete the Cache, Code Cache and GPUCache subfolders inside — never the parent. Cookies and logins live in other files (Network\Cookies, History), so removing cache folders keeps everyone logged in. Deleting whole profile folders instead wipes bookmarks, passwords and settings, which is a different operation with a different outcome.
How often to clean — and doing it in one pass
Cache is regenerated data: nothing degrades if you never clean it, it just eats space. A pass every one or two months is a sensible rhythm; do it more often on a small SSD that runs close to full. After a cleanup, the first visits to familiar sites load a touch slower — that is the cache rebuilding, not a new problem.
Since the manual route means hunting through half a dozen User Data folders, this is exactly the chore automation is for. Kleaner PRO walks every browser profile it finds on the PC and empties their caches in one run, logged-in sessions untouched. Whether you run it on a schedule or keep doing it by hand, the folder map above stays the same.
Questions and Answers
Does clearing cache in one Chrome profile clear the others?
No. Each profile's cache is a separate folder and a separate data island; the clear-dialog touches only the profile it was opened in.
Will deleting browser cache folders log me out of sites?
No. Cookies — the files that hold sessions — live elsewhere (Network\Cookies in Chromium browsers); only pages load a bit slower on the first revisit.
Where is the cache of Chrome's second profile on Windows?
In %LOCALAPPDATA%\Google\Chrome\User Data\Profile 1\Cache. Profiles after the first are numbered: Profile 1, Profile 2, and so on.
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]