The moment Chrome sync clicked for me was saving a password on my phone and finding it already filled in on my desktop three minutes later without any deliberate action on my part. That seamlessness is what the feature is designed to deliver — reducing friction between devices until the browser feels like a single continuous workspace accessible from multiple screens rather than a separate program installed on each one. We go deeper on the whole subject in our Chrome How-To Guides.
Chrome sync keeps bookmarks, passwords, browsing history, installed extensions, preferences, open tabs, themes, and saved tab groups consistent across every device signed in to the same Google account, propagating changes within seconds. Most users enable it during initial Chrome setup and then proceed without revisiting it — benefiting passively but not fully, because the granular controls let you decide exactly which data types sync and which stay local.
What Chrome sync keeps consistent — the full data type list
When fully enabled, Chrome sync maintains consistent state for:
- Bookmarks: all folders, sub-folders, names, and URLs
- Passwords: all saved login credentials, encrypted
- Autofill data: saved addresses and payment card details
- History: a cross-device combined browsing record from all synced devices
- Extensions: the same set of installed extensions available on every device
- Settings: homepage, search engine, startup behaviour, and most Chrome configuration
- Open tabs: tabs currently open on each device, visible on all other devices
- Theme: the active Chrome theme applies everywhere
- Saved tab groups: groups named and saved on one device appear in the saved groups panel on others
What sync doesn’t include is equally important. Chrome Flags (experimental features at chrome://flags) are device-specific and don’t propagate. Downloaded files don’t sync — the file on one device’s disk doesn’t appear on others. Cookies and active site login sessions don’t sync either. Being authenticated with a website on one device doesn’t transfer that login session to another device — even with full sync active.
This session-cookie isolation is intentional and correct. Carrying session cookies between devices would create a serious security vulnerability. The practical consequence: switching devices still requires actively logging into each website on the new device, after which the site’s own session cookie makes subsequent visits frictionless. Sync provides the credentials; you provide the login action. Users who expect to be automatically logged into everything immediately after enabling sync on a new device are consistently surprised by this behaviour — the passwords are there, the sessions are not.
Enabling and configuring Chrome sync
Enabling sync requires a Google account. Click the profile icon at the top-right of Chrome → “Turn on sync” → sign in with Google account credentials → confirm with “Yes, I’m in.”
Chrome defaults to “Sync everything” mode — all available data types sync simultaneously. For more specific control: Settings → You and Google → Sync and Google services → “Manage what you sync” → switch to “Customize sync.” The Customize view shows a toggle for each individual data type, each independently adjustable without affecting the others. Changes take effect immediately and propagate to all connected devices within seconds.
The most common specific customisation: disabling history sync while keeping all other types active. History sync creates a combined cross-device record that accumulates aggressively — visiting the same page on five synced devices generates five entries for that URL in the combined record, producing a history that’s longer but less useful for navigating any individual device’s actual usage pattern. Disabling history while keeping bookmarks, passwords, and autofill provides most of the daily utility of sync without the combined-history noise.
Using synced open tabs to continue browsing on a different device
Synced open tabs is one of the most practically useful capabilities that sync enables — and one the majority of users never discover. When sync is active with the “Open tabs” data type included, tabs currently open on each signed-in device are visible from every other signed-in device. Research begun on a phone during a commute can be continued on a desktop when back at the office, without emailing links, without a notes app as intermediary, without losing any browsing context from the mobile session.
To access another device’s open tabs: open Chrome’s History page (Ctrl+H or Chrome menu → History → History). The left sidebar contains a “Tabs from other devices” section listing each signed-in device by name alongside a timestamp of the last sync update from that device. Expanding any device shows its currently open tabs. Clicking any listed tab opens it in the current device’s Chrome.
The Tab Search panel (Ctrl+Shift+A) also surfaces recent tabs from other synced devices alongside locally open tabs in a single searchable interface — often faster than navigating to the history page when only a tab title or topic keyword is remembered.
That all assumes history is being recorded in the first place. If the history page comes up empty, the issue is Chrome history not saving locally — worth ruling out before assuming sync is at fault.
The tab list reflects the most recent Chrome sync update from each device, not necessarily the real-time current state. A device that last synced two hours ago shows the tab state as of two hours ago. For most practical cross-device continuation scenarios — picking up research from a session ended hours earlier — this slight staleness is irrelevant. For real-time mirroring, the other device needs to be online with Chrome running.
Troubleshooting Chrome sync when changes stop propagating
The most frequently reported sync problem: data changes made on one device don’t appear on another within a reasonable timeframe. In most cases the delay resolves on its own within a few minutes as the sync queue catches up. Persistent non-propagation after fifteen to twenty minutes warrants specific investigation.
First diagnostic check: confirm sync is active and not paused on both devices. Click the profile icon at the top-right of Chrome — if the profile area shows a warning or “Sync is paused,” the sync session has been interrupted. This typically happens after a Google account password change, a security event that invalidated the authentication token, or a session expiry. Re-authenticating with current Google account credentials resumes sync automatically.
If sync appears active but a specific data type isn’t propagating: Settings → You and Google → Sync and Google services → “Manage what you sync” → verify the affected type is toggled on. A common cause of “bookmarks aren’t syncing” is that the data type was accidentally disabled.
If all settings look correct on both devices but a specific data type still fails: disable sync completely on the affected device, wait thirty seconds, then re-enable. This forces a clean full sync from the server rather than relying on the incremental update queue that may contain an unresolvable error state. Our Chrome bookmarks guide covers the duplicate bookmark scenarios that can arise when two devices modify the same bookmark independently before sync resolves the conflict.
The chrome://sync-internals diagnostic page provides a more detailed technical view of sync status — the timestamp of the last successful sync cycle, the queue of pending changes, and specific error codes for persistent failures. Not needed for routine troubleshooting, but useful when simple re-authentication doesn’t resolve the issue.
Privacy implications and passphrase encryption
Chrome sync stores data on Google’s servers to enable cross-device access. By default, Google encrypts sync data in transit using TLS and at rest using server-side encryption — the data is encrypted, but Google holds the encryption keys, meaning Google can technically access the decrypted content for purposes described in its privacy policy.
For users who want stronger protection, Chrome sync supports a passphrase that enables end-to-end encryption for synced passwords and payment information. With a passphrase set, those data types are encrypted on the device before the encrypted data is sent to Google’s servers. Google receives only the ciphertext and cannot decrypt it — the passphrase, known only to the user, is required.
Setting a passphrase: Settings → You and Google → Sync and Google services → “Encryption options” → “Encrypt synced data with your own sync passphrase” → enter and confirm the passphrase.
The critical limitation: passphrase recovery is not possible through the Google account. If the passphrase is forgotten, the only recovery is a complete sync reset that deletes all synced data from Google’s servers and starts fresh. The passphrase provides genuine end-to-end privacy at the cost of this account-level recovery option. Store it somewhere you won’t lose it — a password manager is the obvious choice.
The privacy consideration most worth weighing when configuring sync is history specifically. Enabling history sync gives Google a detailed, cross-device, account-linked record of browsing activity. Users who want sync’s cross-device convenience for bookmarks and passwords without providing a complete browsing history have a clear option in the Customize sync settings: disable History while keeping all other data types active. For the comprehensive data collection picture beyond sync, Google’s privacy policy covers what data Chrome and Google services collect and how it’s used.
| Data type | Sync by default | Notes |
| Bookmarks | Yes | Syncs instantly across devices |
| Passwords | Yes | Encrypted; credentials available but not login sessions |
| History | Yes | Combined cross-device; can disable without affecting other types |
| Extensions | Yes | Same extension set across devices |
| Open tabs | Yes | View other devices’ tabs via History → Tabs from other devices |
| Saved tab groups | Yes | Groups sync to all devices signed in to the account |
| Settings | Yes | Includes search engine, startup, and most preferences |
| Chrome Flags | No | Device-specific, always local |
| Downloads / files | No | Files stay on the device where downloaded |
| Login sessions (cookies) | No | Intentional — each device authenticates independently |
Chrome sync works best when configured to match actual data needs rather than left on the default all-data-types setting. The five minutes spent in Customize sync to disable history (if it adds noise rather than value), verify which data types you actually want cross-device, and consider the passphrase option (if privacy is a priority) turns a passive background feature into a deliberately configured tool that serves the specific cross-device workflows that matter most.
Multiple Google accounts and sync
Chrome supports multiple profiles, each signed into a different Google account with its own separate sync. This is the correct setup for users who have both a personal Google account and a work Google Workspace account: a personal Chrome profile syncs personal bookmarks, passwords, and extensions to the personal account; a work profile syncs work-related browser data to the work account. Each profile maintains complete isolation from the other — personal browsing history doesn’t appear in the work profile’s history, and work passwords don’t appear in personal autofill.
Switching between profiles: click the profile icon at the top-right of Chrome → “Add” or switch to the other profile. Each profile opens in its own Chrome window with its own signed-in account, extensions, and synced data. For users who regularly need to operate across both personal and work contexts, the profile separation makes sync genuinely useful for both without mixing the two accounts’ data.
Sync and Chrome extensions — what actually happens on a new device
Extension sync deserves specific attention because it often surprises users. When Chrome sync includes extensions and you sign into a new device, Chrome will attempt to reinstall the same set of extensions that are installed on your other devices. This happens automatically in the background after sign-in.
The practical consequence: on a new device or Chrome install, the same extensions appear without manually reinstalling each one — useful when you have twenty extensions configured across devices. The extensions must still download from the Chrome Web Store rather than being transmitted directly through sync, so the time for extensions to appear depends on download speed and Web Store availability. Extensions that have been removed from the Web Store since installation won’t reinstall on new devices even when sync is active, since the source no longer exists.
Extension settings (not the extensions themselves) may also sync if the extension was designed to use Chrome’s sync storage API. Many extensions store preferences and configuration in sync storage, so settings configured on one device appear on others — this varies by extension and depends on whether the developer implemented sync storage. When it works (as it does for many popular extensions), this eliminates the manual reconfiguration of extension preferences on each new device.
Signing out of sync — what happens to local data
Signing out of Chrome sync on a device: Settings → You and Google → click your account name → “Sign out and turn off sync.” A prompt asks whether to clear locally-saved data (passwords, history, bookmarks, etc.) from the device when signing out, or to keep the local copy. Choosing to keep the local data leaves a copy of all synced data on the device even after the sync account is disconnected — the data exists locally but no longer receives updates from the account.
This behaviour matters when handing a device to someone else or before factory resetting. Signing out of sync and choosing to clear data removes the locally-stored synced data from the device. Not clearing it leaves personal passwords, bookmarks, and history on the machine — which is a privacy consideration worth being intentional about when a device changes hands. If this sounds familiar, Chrome Startup Settings is worth a look.
Chrome sync is one of those features that genuinely earns its place in daily use once properly configured. The cross-device continuity for bookmarks and passwords alone eliminates a category of friction that used to require manual workarounds (emailing links, using a password manager separately from the browser, manually reinstalling extensions on new devices). Getting sync configured with the right data types and an understanding of what it does and doesn’t cover converts it from a background convenience into a deliberate, understood part of the browser workflow. Our guide on Chrome Print Settings covers an adjacent issue.
