Tabs, sessions and clearing a profile's cache
Control whether a profile reopens your tabs, and free disk space without losing any logins.
On this page
A profile keeps two very different kinds of data. One is the part you'd miss: cookies, logins, local storage and the tabs you had open. The other is disposable: cached images, scripts and GPU data that only exist to make pages load faster. Clearing the second never touches the first.
🗂️ Do my tabs reopen?#
Yes, by default. A profile's Start URL setting decides:
| Start URL | What happens when you click Run |
|---|---|
| Previously opened tabs (the default) | The tabs you had open last time come back |
| Blank page | One empty tab |
To change it: open the editor (row ⋯ → Edit), go to the Advanced tab, and set Start URL. You can change the default for new profiles under Settings → Profile defaults.
Always Stop a profile, or close its window, rather than killing the app, so the tabs and cookies are written out properly.
Your tabs travel too, on paid plans
On Pro, Team and Custom, closing a Chromium profile uploads its cookies, local storage and open tabs, encrypted. Open the same profile on another computer and they're there. Free plans sync profile settings but not sessions. See Cookie and session sync.
💾 Do I stay logged in?#
Yes. Each profile has its own cookie store on disk, so it opens signed in to whatever it was signed in to, as long as the site's cookies haven't expired. Nothing is cleared between runs unless you ask for it.
Two things do sign a profile out:
- Clear cookies on the editor's Cookies tab.
- Cookies that were session-only when they were imported. See Import and export cookies.
🧹 Clear a profile's cache#
- Stop the profile. A running profile's cache can't be cleared, and you'll see "Close the profile first — its cache can't be cleared while it's open".
- On its row, click ⋯ → Clear cache….
- Click Clear cache.
You'll see how much was freed, for example "Freed 1.42 GB".
To do several at once, tick the rows and click Clear cache in the bar at the bottom. Running profiles are skipped and counted in the result.
Nothing you care about is deleted
Only cached images, scripts and GPU data go. Cookies, logins, local storage, saved passwords and the fingerprint are untouched. Sites just reload their assets on the next visit.
🔄 Trim caches automatically#
Settings → General → Clear browser cache on close:
| Setting | What it does |
|---|---|
| Over limit (the default) | Trims a profile only once its caches have grown past the limit |
| Every close | Trims every profile whenever it closes |
| Never | Only when you use Clear cache… yourself |
Limit per profile sets how many megabytes a profile may keep, from 16 to 8192. It starts at 256 MB.
When a profile is trimmed on close you'll see "Cleared 412 MB of cache from acme-google-ads".
Every launch also caps the page cache at 150 MB and the media cache at 50 MB, so a single profile can't run away with your disk between trims.
❓ Common questions#
Where is my profile data stored?
On Windows, under %APPDATA%\LoginDeck\data. On a Mac, ~/Library/Application Support/LoginDeck/data. Each profile has its own folder there with its browser data in it.
My profile opened without my tabs. Why?
Check three things: the profile's Start URL may be Blank page; the profile may have been closed abruptly instead of stopped; or, if you opened it on another computer, the tab set didn't travel — tabs sync on paid plans only, and a very large tab set can be skipped.
Will clearing the cache log me out or change my fingerprint?
No. Neither. The fingerprint is part of the profile's settings, not its cache.
My LoginDeck folder is huge. What's taking the space?
Mostly profile caches and the browser versions you've downloaded (about 200 MB each). Clear caches on the profiles you use most, and remove browser versions you don't need under About → Chrome versions.
Does clearing the cache help with CAPTCHAs or bans?
Rarely. Those come from the account, the IP and behaviour, not from cached images. See Sites show CAPTCHAs or block accounts.
ℹ️ Good to know#
- Stopping a profile closes the browser the way its own close button does, so cookies get written. If it hasn't closed after 8 seconds it's closed by force.
- Deleting a profile keeps its cookies and tabs in Recently deleted for 30 days. See Delete and restore profiles.