Chrome Bookmarks Not Syncing: 7 Fixes That Work

You set up a new laptop, signed into Chrome, and watched your passwords, extensions and history land exactly where they should. Then you opened the bookmarks bar and it was empty, or worse, it was full of things you saved three years ago and nothing since. Everything else made the trip. The one thing you actually wanted did not.

Or the other version. You save a link on your phone, walk to your desk, and it is not there. You check the sync settings on both devices and they both say the same thing, so you turn sync off and on again, which is the point where most people give up and email the link to themselves.

The reason this is so much more annoying than it should be is that Chrome gives you almost no feedback. Sync either works or it silently does not, and the settings screen looks identical in both cases. Google’s own troubleshooting page for sync problems lists two fixes. Chromium’s source code contains a hard cap that puts bookmark sync into a permanent error state and then refuses to retry for a month. That gap between what Google documents and what Chrome actually does is why searching this problem gets you 200 community forum threads and no answers.

So this page is the seven things that actually block bookmark sync, in the order you should check them, cheapest first. Three of them are not in any official help article.

What Chrome sync actually promises

Chrome sync is the feature that copies your browser data to your Google Account and mirrors it onto every device signed into that account. It is a replication system, not a storage system, and the difference matters for every fix below.

Google’s list of what travels covers bookmarks, reading list, passwords, payment info, addresses, extensions, web apps, settings and preferences, plus tabs and history once you enable them. Each of those is a separate data type internally, and each one can fail on its own. That is the single most useful thing to understand here. Bookmarks can be broken while everything else is fine, and the top-level sync toggle will still say it is on.

Which is exactly the symptom most people describe, and exactly the one no generic “turn sync off and on again” guide addresses.

Fix 1: Confirm bookmarks specifically are syncing

Start with the boring one, because it is right more often than it should be. Being signed in is not the same as syncing, and syncing everything is not the same as syncing bookmarks.

Go to chrome://settings/syncSetup. If it offers to turn sync on, that is your answer. If sync is already on, open the data controls and check that bookmarks are included rather than assuming. Chrome lets you sync a subset, and a subset you picked in 2022 on a machine you have since replaced will follow your account around.

Do this on both devices. A surprising share of “not syncing” cases are one device happily uploading to an account that the other device is not syncing down from.

Fix 2: Fix “Sync is paused” (the most common cause by far)

This is the one to check before anything else, and it is the reason the forums are full of people insisting sync was on the whole time.

Chrome ties sync to a token from your Google session. Google’s own wording is blunt about the trigger: “If you signed out of a Google service like Gmail, Chrome pauses sync.” Sign out of Gmail in a tab, and your bookmarks quietly stop moving between devices. Nothing warns you in a way you would notice. There is a small “Verify it’s you” prompt behind the profile icon and that is it.

Click the profile icon at the top right. If you see anything about verifying or signing in again, that is your problem. Sign in and sync resumes, usually within seconds.

Two things make this worse than a one-off. The first is that a Google password change or a two-factor update pauses sync the same way. The second is fix 3.

Fix 3: Stop Chrome clearing cookies when it closes

If sync pauses again every time you restart the browser, you have almost certainly told Chrome to clear cookies on exit. That setting signs you out of Google along with everything else, so sync pauses on every single launch. You fix it, it breaks again tomorrow, and it looks like a bug rather than a setting.

The fix is not in the sync settings, which is why people miss it. Google routes it through site data instead. Go to Settings, then Privacy and security, then Site Settings, then Additional content settings, then On-device site data, and allow sites to save data on your device. If you want to keep clearing cookies broadly, add Google accounts to the allowlist instead of turning the whole thing off.

Fix 4: Check you are in the right Chrome profile

Chrome runs multiple profiles and each one has its own bookmarks and its own sync state. If a second profile exists, you can spend an afternoon fixing sync on a profile that was never the problem.

Open chrome://version and look at the Profile Path. Compare it across devices. If one says Default and the other says Profile 2, you are looking at two different browsers that happen to share a taskbar icon.

This gets people most often on managed accounts. Since Chrome 102, signing into a work or school Google Account creates a separate profile by default rather than merging into your personal one, so bookmarks appear to vanish moments after a work sign-in. That case is covered in more depth in our guide on Chrome bookmarks disappearing.

Fix 5: Check whether your bookmarks are account bookmarks or local bookmarks

This is the newest cause on the list and the one that explains the strangest symptom, where some bookmarks sync and others sitting right next to them never do.

Chrome used to have one bookmark tree. It now has two. Per Chrome’s own developer announcement, “Chrome will separate syncing and non-syncing bookmarks into two separate subtrees in the bookmarks tree.” Every bookmark node carries a syncing flag that is either true or false, and the change started rolling out to a slice of Chrome Stable users from the end of June 2025 before widening.

The practical result is that you can have two folders called Bookmarks bar and two called Other bookmarks, one pair saved to your Google Account and one pair that exists only on that machine. Anything in the local pair is never going to appear on another device, and no amount of toggling sync will change that, because sync is working correctly and those bookmarks were never in scope.

Open the bookmark manager with Ctrl+Shift+O on both devices and compare the folder structure rather than the contents. If one machine has a set of folders the other does not have at all, this is your cause, and the fix is to move or re-save those bookmarks into the account tree.

Fix 6: Check for a work or school policy

If this is a managed laptop, stop troubleshooting and check the policies. An admin can break bookmark sync in three different ways and the sync settings screen will not tell you.

Open chrome://policy and search the list. These are the three that matter, straight from Google’s policy documentation:

SyncTypesListDisabled is the interesting one and the reason this section exists. It is the only cause on this whole page that produces the exact symptom of every other data type syncing normally while bookmarks alone sit still. If you are on a work machine and passwords and history are crossing devices but bookmarks are not, check this policy before you touch anything else. Google’s documentation is explicit that the type names are case sensitive, so an admin who typed Bookmarks broke it slightly differently than one who typed bookmarks.

Worth knowing that BrowserSignin set to disabled keeps your existing data. Google’s own description states that “their local profile data like bookmarks, passwords etc. will be preserved and still usable.” So a policy change is not data loss, it is a sync ceiling.

Fix 7: Read chrome://sync-internals, and check the bookmark limit

If the first six did not do it, this is where you stop guessing. chrome://sync-internals is the only genuine diagnostic Chrome ships, and almost nothing written about this problem mentions it.

Open it, find the type list, and look at the Bookmarks row. If the count is zero when you have hundreds of bookmarks, Chrome is not uploading. If there is an error string, read it, because that is the answer.

And this is the finding that justifies the whole page. Chromium’s source sets a hard maximum on synced bookmarks. From components/sync_bookmarks/constants.h, checked on July 30, 2026:

// The maximum number of bookmarks that are allowed to be synced. If the number
// of local bookmarks exceeds this limit, sync will enter a "bookmarks limit
// exceeded" error state.
inline constexpr size_t kSyncBookmarksLimit = 100000;

Two things about that. First, cross it and sync does not slow down or partially work, it enters an error state and stops. Second, and this is the part that turns a bad afternoon into a bad month, Chrome does not retry promptly once you are back under the limit. The same directory sets the expiry on that error state to 30 days, minus up to 7 days of randomized jitter so that every affected client does not re-download at once. Delete 40,000 bookmarks to get under the cap and sync can still refuse to move for weeks.

One correction while we are here, because it is repeated everywhere. The widely cited figure is 100,000 on desktop and 20,000 on mobile, from coverage of the limit landing in 2023. That mobile number is out of date. Chromium’s Android sync service now declares SYNC_BOOKMARKS_LIMIT = 100000 and is kept in lockstep with the C++ constant by a lint rule, so the cap is the same 100,000 on both today.

Realistically, most people reading this are nowhere near 100,000 bookmarks. But bookmark importers, extension migrations and repeated HTML imports duplicate aggressively, and a few rounds of “import my old bookmarks to be safe” is how a normal person quietly ends up with a six-figure bookmark tree and permanently broken sync.

Chrome not showing bookmarks at all: a different problem

Worth separating this out, because “not syncing” and “not showing” get searched interchangeably and they have almost nothing in common.

If bookmarks are missing on this device rather than failing to arrive from another one, do not start with sync. Run these three checks first:

• Press Ctrl+Shift+O to open the bookmark manager: if your bookmarks are there but the strip under the address bar is empty, this is a view problem and the fix is Ctrl+Shift+B. Full detail in our guide on the Chrome bookmarks bar disappearing.
• Check the Other bookmarks folder: saves land there rather than on the bar more often than people expect, so a bar that looks empty is often a bar that was never filled.
• Check the profile at chrome://version: an empty bookmark manager on a second profile is the single most common cause of “Chrome is not showing my bookmarks.”

Only after all three come back clean is this a sync question. And if the bookmarks are genuinely gone from the machine, that is a recovery job, not a sync job, and the routes are in our guide on how to recover deleted bookmarks.

The uncomfortable part: sync is not a backup

Here is the take that matters more than any fix above. Most of the frustration with bookmark sync comes from expecting it to do a job it was never built to do.

Sync’s job is agreement. It makes every device hold the same list. It is extremely good at that, which is precisely why it is useless as a backup. Delete a folder of 200 bookmarks on your laptop and sync does its job flawlessly by deleting them from your phone, your tablet and your work machine within seconds. There is no server-side trash and no undelete. Your Google Account is not a copy of your bookmarks, it is the same bookmarks, stored once.

The passphrase case makes this concrete. If you encrypt sync with a passphrase and forget it, the only route forward is a reset, and Google’s documentation is clear about the cost: “the data encrypted by your passphrase is deleted from Google’s servers and you’re signed out from all your devices.” That is not a recovery flow, it is a demolition flow. Google recommends exporting first for exactly that reason.

So the habit worth building is not better sync hygiene. It is one manual export you keep somewhere sync cannot reach. Chrome’s bookmark manager exports to a single HTML file in about ten seconds, and unlike your Google Account, that file does not update itself when you make a mistake. Our guide on moving bookmarks between browsers covers the export in detail.

What sync was never going to reach

One last thing, and it is the reason a lot of people find this page and then realize sync was only half their problem.

Chrome sync covers the bookmarks Chrome knows about. It has no idea about the saves that live inside the platforms you actually read. Your X bookmarks, your Reddit saved posts and your LinkedIn saved items are not in Chrome’s bookmark tree at all. They sit in three separate accounts, none of which sync anywhere, none of which have a backup file, and none of which have real search. Reddit silently caps saves. X gates search behind a subscription. LinkedIn gives you a reverse-chronological list and nothing else.

Fixing Chrome sync gets your links onto every device. It does not make any of it findable, and it does not touch the three places most of your saving now happens. That is a different layer of the problem, and it is the one we built ContextBolt for.

ContextBolt is a Chrome extension that captures your saves from X, Reddit and LinkedIn, stores the full content on your device rather than a pointer to someone else’s server, and tags each one with AI so you can search by meaning instead of trying to remember the exact words. The Basic tier is free and covers 150 bookmarks with AI tagging, topic clustering and semantic search. Pro is $6 a month for unlimited bookmarks, encrypted cloud sync and a personal MCP endpoint, which lets Claude, Claude Code, Cursor and Windsurf read your saved library directly.

That last part is the bit worth sitting with. Sync answers “is this list on my other laptop.” It was never designed to answer “what was that thing I saved about pricing six months ago,” which is the question people are actually trying to ask. We argued the longer version of that case in why MCP will replace browser bookmark sync.

Fix your sync first. Then fix the bit sync was never going to fix.