Cloud Sync
What has to be true for sync to run, and how conflicts and plan limits show up.
What sync needs to be running
Sync only starts once you have a verified account, a signed-in session, and a server URL configured — the default TabSlate Cloud URL if you didn't change it, or your own self-hosted server if you did. If any of those isn't true yet — you're still on the guest workspace, your email isn't verified, or your session has gone stale — TabSlate keeps working entirely from local data and simply doesn't push or pull anything.
Once sync is running, the status shown in the sidebar reflects what's actually happening — syncing while a push or pull is in flight, an error state with details available on hover if something goes wrong, and back to idle once everything is caught up. Sync now forces an immediate attempt instead of waiting for the next automatic one.
Official Cloud and self-hosting use the same sync
TabSlate's extension talks to the same sync API whether you're using the official TabSlate Cloud service or a compatible self-hosted TabSlate server — it doesn't behave differently depending on which one you point it at. What can differ between them is what the server itself enforces, such as plan limits, not how the extension syncs with it.
Conflicting changes and plan limits
If the same data changes in two places before they've synced with each other, TabSlate resolves it automatically rather than asking you to pick a version — the affected item ends up reflecting whichever change last reached the server, and your dashboard updates to match on the next sync.
Hitting a plan limit — for workspaces, collections, bookmarks, tags, or saved groups — during sync shows a temporary banner naming the limit you've reached alongside your current usage. See Settings → Plan & Quotas for where those limits are tracked.
Permanently deleting a workspace on a synced account isn't purely local — it has to be confirmed by the server. If you're offline when you try, the deletion is blocked rather than applied, so your device and account can't end up disagreeing about whether it happened.
Last updated on