🔄What syncs between your computers

Your profiles live on your own disk. When you sign in, LoginDeck also keeps a small encrypted record of each one on its server — kilobytes, not gigabytes — so the same profiles, folders, tags and proxies show up on your other computers.

This page is the exact list. Every record is encrypted on your computer before it leaves it: see How your data is protected.

✅ What syncs#

Two details worth knowing about that list:

• Saved proxies carry their passwords. They have to: a proxy row that arrives without its credentials looks synced and then fails the moment you launch. That also means anyone you give access to a profile receives its proxy password — see What members can see and do.
• Last launch time and the proxy's exit location travel as observations, not edits. They are merged field by field, newest wins, so a laptop that opens a profile can't overwrite a rename you made on the desktop.

🔐 Cookies and site data (paid plans)#

On Pro, Team and Custom, LoginDeck also carries the part that makes a profile arrive signed in rather than merely identical:

• Cookies — read out of the browser and written back in through the browser on the other machine, never copied as a file. Chrome encrypts its cookie file with a key tied to one computer, so a copied file would arrive unreadable and log you out with no explanation.
• Local Storage — where many sites keep half of their session.
• IndexedDB — since version 0.1.151. A growing number of web apps keep their signed-in state here, and without it those profiles arrived logged out even with the cookies intact.
• Open tabs — since version 0.1.163. The tab set from the last run, with each tab's back/forward history.

The timing matters: the snapshot is taken when you close the profile's browser, not on a timer, and it is written into the profile the next time somebody opens it on the other computer. So close the browser on the first machine before you go looking for the session on the second one.

🚫 What stays on the computer it's on#

• Cache, GPU cache and service-worker storage. Gigabytes the browser rebuilds by itself.
• Extension files. The profile remembers which extensions it uses, but each computer needs those extensions in its own library. A profile that names an extension this computer doesn't have launches without it, and the editor says so. See Add extensions to profiles.
• Schedules. A schedule stays on the machine you created it on, on purpose: two computers both firing "every night at 2am" would be two runs of one Flow on one profile. The Flow itself syncs; the decision to run it here does not. See Run Flows on a schedule.
• Fingerprint check results. Each computer keeps its own. See Check a profile's fingerprint.
• App settings, like your theme and your shortcuts.
• The browser data behind a deleted profile. The Recently deleted entry travels, so a restore on one computer restores everywhere — but each computer restores its own copy of the cookies and site data. See Delete and restore profiles.

⏱️ When it runs#

Sync doesn't wait for the timer. It runs:

• straight after you sign in, then every 5 minutes (anything from 1 to 720 minutes)
• about two seconds after any change you make
• just before a profile launches, so a session saved on another computer minutes ago is used
• after a browser closes, so its session goes up before the profile is released
• when you come back to the window, when you unlock the screen, and when the computer wakes up
• when you quit — open browsers are closed properly and pending changes pushed first
• whenever you press Sync now on the Account page

ℹ️ Good to know#

• The newer change wins, per profile. If a change you made here was replaced by a newer one from another machine, the result line under Sync now says so and names it, rather than reporting a clean sync.
• A delete beats an edit, whatever the clocks say. The one exception is an explicit Restore from Recently deleted.
• Over your plan limit, a sync round is refused whole and nothing already synced is touched. Renames and deletes still go through, because they don't make the account bigger. And reading is never blocked — you can always pull your own data back onto a machine.
• Very large sessions are trimmed, not dropped. After compression, a capture carries up to 8 MB of Local Storage, 12 MB of IndexedDB and 8 MB of tabs. Past the IndexedDB budget, that one part is skipped for that capture and the cookies and Local Storage still go; the other computer keeps the IndexedDB it already had rather than losing it.
• Open tabs only reopen on profiles whose start behaviour is Previously opened tabs. A profile set to Blank page, or launched at a specific URL, or started by a Flow or the API, opens where you sent it. See Tabs, sessions and clearing a profile's cache.
• Phones used as proxies aren't part of this list. They live on your account on the server, so every computer signed into the account sees them. See Use an Android phone as a mobile proxy.

❓ Common questions#

Will my profiles stay on this computer if I turn sync off?

Yes. Your profiles are files on your disk. Turning Sync automatically off stops them being copied to your other computers; it doesn't remove anything.

Why did a profile arrive logged out?

Either you're on Free, which doesn't sync cookies, or the browser on the first computer was still open when you looked. The snapshot is taken on close. See Cookie and session sync.

Can two computers open the same profile at once?

No. A profile can only be open on one computer at a time, and the other one names the machine holding it. See When someone else has a profile open.

Does sync upload my browser cache?

No. Cache, GPU cache and service-worker storage never leave the computer. What travels is the profile record and, on paid plans, the cookies and site data that carry your logins.

My second computer doesn't have my extensions.

Extension files don't sync. Add the same extension to the library on that computer and the profile will pick it up again.