Chrome Sync Re-enablement: Local Edit Reconciliation at the Profile Configuration Boundary

Chrome Sync serves as the primary restoration mechanism for bookmarks, passwords, history, and settings after sign-in, yet the browser lacks a native full-profile backup archive. Across recent desktop Chrome releases, the configuration boundary where sync is turned off and later re-enabled requires Chrome to reconcile locally created or edited items with the cloud copy. The precise merge-versus-overwrite policy for these local changes is not fully documented for end users, leaving uncertainty about whether offline edits survive the transition or are silently replaced by the cloud state.

Password restoration introduces additional dependency on the encryption mode selected during sync setup. A custom sync passphrase changes how recovered credentials are decrypted, which can block immediate access if the phrase is lost. Because Chrome provides no built-in restore-integrity report, verification remains manual through chrome://bookmarks and chrome://settings/passwords.

Does Chrome merge locally edited bookmarks and passwords with the cloud copy or overwrite local changes when sync is re-enabled after a period offline? How does the custom sync passphrase encryption mode affect the visibility of locally created passwords after re-enabling sync? Is the reconciliation behavior consistent across desktop Chrome and Android, or do platform-specific differences alter the outcome?