Cookie and session sync
On paid plans a profile arrives on your other computers already signed in — how the snapshot is taken, when it is applied, and the storage each plan gets.
On this page
Sync carries every profile's identity — its fingerprint, its proxy, its name. Session sync carries the other half: the cookies and site data that make the profile arrive signed in rather than merely identical.
Part of Pro, Team and Custom.
On Free, profiles still sync. Their cookies and site data don't, so a synced profile opens as the same machine but logged out.
🍪 What a session contains#
| Part | Notes |
|---|---|
| Cookies | Read out of the browser and written back in through the browser on the other machine — never copied as a file. |
| Local Storage | Where many sites keep half of their session. |
| IndexedDB | Since version 0.1.151. A lot of modern web apps keep their signed-in state here. |
| Open tabs | Since version 0.1.163 — the tab set from the last run, with each tab's history. |
Cookies get their own treatment for a good reason: Chrome encrypts its cookie file with a key tied to one computer. A copied file arrives unreadable on the second machine, and you'd be logged out with nothing to explain why. Writing them back through the browser avoids that, and is also why sessions move correctly between Windows and a Mac.
⏱️ When the snapshot happens#
- On close. The snapshot is taken when you close the profile's browser, not on a timer — a cookie jar read halfway through a login is a snapshot of a half-logged-in account.
- Uploaded before the profile is released. LoginDeck waits up to 20 seconds after a browser closes so the session goes up before another computer can claim the profile.
- Applied on open. The other computer files the session when it arrives, then writes it into the profile the moment somebody actually opens it. It also syncs just before a launch, so a session saved minutes ago on another machine is the one you get.
Close the browser on the first computer first
This is the single most common reason a profile "arrives logged out". Nothing is captured until the browser closes.
💾 How much storage each plan has#
Sessions are the only part of sync with real size to it, so each plan has a session storage allowance:
| Plan | Session storage in sync |
|---|---|
| Free | 250 MB (sessions don't sync) |
| Pro | 2 GB |
| Team | 6 GB |
| Custom | 20 GB |
Go over it and a sync round is refused whole, with nothing already synced touched: "this would put 2100 MB in sync, and Pro covers 2048 MB. Clear a few browser sessions or move up a plan — nothing already synced has been touched."
Two ways out: Clear cache… from a profile's ⋯ menu (or the bulk Clear cache button) on profiles you don't need signed in, or move up a plan. Profiles locked by your plan don't count toward the allowance.
📦 Per-capture limits#
One capture is allowed, after compression, up to 8 MB of Local Storage, 12 MB of IndexedDB and 8 MB of tabs.
If a profile's IndexedDB is bigger than that, that one part is skipped for that capture and the cookies and Local Storage still go. The other computer then keeps the IndexedDB it already had — a skipped part means "leave what's there", never "wipe it".
🗂️ Sessions and team members#
A session record carries the folder its profile is in, so the server only sends it to members who can see that profile. Someone with access to one folder never receives cookies from another. See What members can see and do.
ℹ️ Good to know#
- Cache is not part of this. Cache, GPU cache and service-worker storage never leave the computer — they're gigabytes the browser rebuilds by itself.
- Open tabs only reopen on profiles whose start behaviour is Previously opened tabs. A profile set to Blank page, or one launched at a URL by a Flow or the API, opens where you sent it.
- Downgrading to Free doesn't delete sessions already on the server. They're kept; what stops is pushing new ones.
- A profile in the bin keeps its cookies on the computer it was deleted on, so a restore brings that machine's own session back. See Delete and restore profiles.
- Importing cookies from a file is a different feature and works on every plan. See Import and export cookies.
❓ Common questions#
Will I stay logged in when I open the profile on my laptop?
On Pro, Team and Custom, yes — close the browser on the first computer, then open the profile on the laptop.
Does Free sync cookies at all?
No. Free syncs profiles, proxies, tags, folders and Flows, but not sessions. See Plans and what each one includes.
Why did my tabs come back empty?
Check the profile's start behaviour is Previously opened tabs rather than Blank page, and that the browser was closed properly on the other computer. See Tabs, sessions and clearing a profile's cache.
A site logged me out even though sync worked. Why?
Some sites tie a session to more than cookies — an IP, a device check, or data that was over the per-capture limit. Open the profile through the same proxy it normally uses and sign in once; the next capture will carry it.
Can I stop one profile's cookies from syncing?
Not per profile. Clear cache… on a profile clears what's there, and the next capture is only as big as what the browser rebuilds.
Does session sync slow the app down?
No. Sessions are filed when they arrive and only written into a profile when you open it, so a sync round never has to touch every profile's browser.