Recover Deleted Chrome Bookmarks: What Actually Works (and Why Bookmarks.bak Fails After Sync)
Chrome has no recycle bin for bookmarks. Four things make them disappear — an accidental delete, a cleanup that took too much, a sync that spread a deletion to every device, a lost profile — and each has a different fix. Here is the triage, the one file that helps until Chrome's next write, and the second bookmark file a signed-in Chrome keeps that has no backup at all.
Chrome has no recycle bin for bookmarks. Delete a folder, and it is gone — no trash to open, no “recently deleted”, and a sync that copies the deletion to every device you are signed into within seconds. What Chrome does have is one silent backup file, and almost every official answer points at it without saying the two things that decide whether it helps: it is spent by the next change to your bookmarks, and on a signed-in Chrome it covers only one of the two bookmark trees you have.
This guide is a triage. Start with what happened to you, because the fix is different for each.
First: copy the files, before Chrome writes again
Whatever happened, do this before anything else. Chrome keeps one copy of your bookmarks file, Bookmarks.bak, in your profile folder — and it does not rewrite that copy on a timer, nor, despite what nearly every guide says, at launch. Chromium backs it up lazily: once per session, the first time anything changes your bookmarks after Chrome starts, from the file as it stood just before that change. A session that opens and closes without a single bookmark change leaves the backup untouched.
That is better news and worse news than "it dies on restart". Better, because a backup can survive several relaunches intact — so look, even if you have already restarted. Worse, because the thing that spends it is not a restart you choose to make: it is the next change, and sync can deliver one from your phone while you are reading this.
So: quit Chrome, or at the very least copy the files below somewhere safe before you touch a bookmark.
| System | Chrome profile folder |
|---|---|
| Windows | %LOCALAPPDATA%\Google\Chrome\User Data\Default\ |
| macOS | ~/Library/Application Support/Google/Chrome/Default/ |
| Linux | ~/.config/google-chrome/Default/ |
A second Chrome profile lives in Profile 1, Profile 2… instead of Default. Inside, this is what is worth copying and what is not:
| File | What it is |
|---|---|
Bookmarks | The live bookmarks of this device. Plain JSON — openable in any text editor. |
Bookmarks.bak | The lazy backup of that file, described above. The only backup Chrome makes. |
AccountBookmarks | A second, separate tree: the bookmarks that live in your Google Account. Present only when you are signed in without sync. Chrome never writes an AccountBookmarks.bak. |
BookmarkMergedSurfaceOrdering | Only the order the two trees are shown in. No titles, no addresses, nothing to recover — leave it where it is. |
EncryptedBookmarks.bak | Sorts right next to the real backup and is not one. See below. |
The second file most guides don't know about
Since Chrome 134, a profile that is signed in but not syncing keeps two bookmark trees and writes them to two files. Bookmarks holds what is only on this device; AccountBookmarks holds what is in your Google Account. Chrome's bookmarks bar shows the two merged, so you can have two folders named "Bookmarks Bar" and two named "Other Bookmarks" without ever noticing there are two of anything.
One fact then decides everything else on this page: the backup exists for the device file only. That is an explicit branch in Chromium's storage code — the account tree is excluded from backups by design, not by an oversight that will be filled in later — and it holds on a real signed-in-without-sync profile: change something, watch AccountBookmarks get rewritten, and no .bak appears beside it.
So if what you lost was in your Google Account, comparing Bookmarks with Bookmarks.bak will truthfully report that the backup holds nothing extra — while your bookmarks are still gone. That answer is about the device tree, and it is easy to read as a verdict on everything you own.
Before you do anything else, look for AccountBookmarks in the profile folder. If it is there, you have two trees, and the first question is which one lost the bookmarks.
EncryptedBookmarks.bak is not a spare copy
Chrome has been rolling out encryption of the local bookmarks file, and a profile that has met it can be left with a file called EncryptedBookmarks.bak. Do not build a plan around it: it is ciphertext, it starts with the marker Chromium's operating-system encryption writes, and the key is in your OS keychain rather than in the file. Renaming it to Bookmarks does nothing at all. It is listed here only because it sits next to Bookmarks.bak in the folder and has the more reassuring name of the two.
Case 1 — you deleted it a moment ago
Open chrome://bookmarks and press Ctrl+Z (⌘Z on a Mac). Chrome's bookmark manager has a one-step undo for the last delete — but only while that tab stays open. Close the tab, or delete something else, and it is gone.
If the undo is already out of reach, you are in the next case.
Case 2 — a cleanup removed more than you meant
Duplicate finders, dead-link checkers and “organize my bookmarks” tools delete in bulk, and most of them delete for good. If the tool showed a report of what it removed, save that first. Then compare the two files: everything the cleanup took is still in Bookmarks.bak if nothing has changed your bookmarks since — including the cleanup's own next delete, and anything sync brought in.
If the profile has an AccountBookmarks file, this comparison covers the device tree only. A cleanup tool deletes across the merged view, so it can perfectly well have taken bookmarks from both trees while the backup can only account for one of them.
The Bookmarks recovery tool does the comparison in your browser: drop both files, it lists what the backup has that the current file does not, grouped by folder, and you download the ones you tick as a bookmarks HTML file. Import it from chrome://bookmarks → ⋮ → Import bookmarks. Nothing is uploaded; the files never leave your machine.
Before the next cleanup, export your bookmarks first. Ten seconds, and this case stops existing.
Case 3 — sync removed them everywhere
This is the one that hurts, and the one where the usual advice fails. You deleted on a laptop (or a child did, or an extension did), and by the time you noticed, the deletion had reached your desktop and your phone too. Google's account bookmarks keep no history to roll back. There is no “restore bookmarks” in your Google account, and signing out does not bring them back.
What is left is Bookmarks.bak — on any device where the deletion was not the change that spent this session's backup. Sync writes the deletion into each device's Bookmarks file immediately; the .bak beside it holds whatever that Chrome saw before its first bookmark change of the session. Pick the device you have used least — least used means fewest chances to have spent it — copy its Bookmarks.bak out before doing anything else, and bring it to the recovery tool or the swap below.
Signed in without sync, the shape is the same and the file is not there. Deleting a bookmark that lives in your Google Account removes it from the account, and so from every device signed into it; the tree that held it has no .bak on any of them. What is on your side in that case is the next section, not this one.
If every device has spent its backup, see case 4.
Case 4 — the profile is gone
Reinstalled Chrome, reset your profile, deleted the user folder, changed machines without copying it: the device files go together, and nothing in Chrome holds an earlier copy of them. The recoveries for those live outside Chrome: a Time Machine or File History snapshot of the profile folder, a bookmarks HTML you exported at some point, or a machine that has not been turned on since.
Check the account tree before you accept this verdict. If you were signed in without sync, the bookmarks you had saved to your Google Account were never only on that disk — sign in again on a fresh profile and they come back, because the account is where they were living. What the lost profile really took is the device tree: the bookmarks in Bookmarks, which existed on that one machine and nowhere else. On a two-tree profile this case is half a loss, not a total one.
What it is not safe to conclude this from is a comparison that came up empty. “The backup holds nothing the current file lacks” is a statement about Bookmarks; it is silent about the account tree, and on a signed-in profile it is silent about the half of your library Google is still holding.
If none of that turns anything up, the honest answer is that those bookmarks are gone. Set up the export habit before rebuilding.
The classic fix: swap the files
If you would rather restore the whole earlier state than pick and choose:
- Quit Chrome completely (check it is not still running in the background).
- In the profile folder, rename
BookmarkstoBookmarks.old. - Rename
Bookmarks.baktoBookmarks. - Start Chrome.
Everything as of that backup is back — including bookmarks you added since, which are now gone (they are in Bookmarks.old if you need them). Comparing the two files instead lets you take back only what went missing and keep the rest.
This swaps the device tree and nothing else. If the profile has an AccountBookmarks file, that tree is untouched by all four steps: it has no backup to swap in, and Chrome will go on showing it exactly as it is now. Anything you get back this way arrives on the device side of the merged view.
Why Bookmarks.bak fails after a sync
The file is a snapshot, not a history — and the moment the snapshot is taken is the part almost every guide gets wrong. Chrome does not write it at launch. It writes it once per session, at the first change to your bookmarks after launch, copying Bookmarks as it stood immediately before that change. Chromium's own source calls this a lazy backup and keeps it that way to avoid a disk write nobody needed; a browsing session that never touches a bookmark leaves the backup alone.
Two consequences, pulling in opposite directions. A backup can outlive several restarts, so it is worth looking even after you have relaunched — the common advice to give up at that point is too pessimistic. And the change that spends it does not have to be yours: one edit arriving from your phone is a bookmark change, and it will spend the session's single backup on the state you were trying to keep.
That is why two people can follow the same instructions and get opposite results: one reached the file before anything had changed and got everything back; the other had already saved a bookmark, and found a backup identical to the broken file. Sync stretches the failure across devices — each device spends its own backup on its own first change — so the machine you have touched least is the last place the bookmarks exist.
None of this applies to AccountBookmarks. There is no second backup file and no session in which one is written. For the account tree, the only copies are the ones you made yourself: an export, or a filesystem snapshot of the whole profile folder.
Never need this page again
Chrome's own export (chrome://bookmarks → ⋮ → Export bookmarks) writes a single HTML file every browser can import. Do it before a cleanup, before reinstalling, before a new machine. The backup guide covers it, including exporting just the folders you care about.
FAQ
Q: Does Chrome have a recycle bin for deleted bookmarks? A: No. The bookmark manager has a one-step Ctrl+Z / ⌘Z that lasts while the chrome://bookmarks tab is open, and nothing after that. There is no trash folder and no restore point in your Google account.
Q: Where is the Bookmarks.bak file? A: In your Chrome profile folder, next to a file called Bookmarks. Windows: %LOCALAPPDATA%\Google\Chrome\User Data\Default. macOS: ~/Library/Application Support/Google/Chrome/Default/. Linux: ~/.config/google-chrome/Default/. Other profiles use Profile 1, Profile 2 and so on.
Q: Why is my Bookmarks.bak the same as my Bookmarks file? A: Because something changed your bookmarks after the loss and Chrome spent the backup on that moment. The backup is written once per session, at the first bookmark change after launch, from the current file — so a single edit, or one deletion arriving over sync, is enough to make it a copy of the file that already lacks them. A restart alone does not do it; the first change after the restart does.
Q: Can I get bookmarks back that sync deleted on all my devices? A: Only from a device that has not restarted Chrome since the deletion arrived — its Bookmarks.bak still holds the earlier state. Google keeps no history of account bookmarks to restore from.
Q: Is there a way to restore Chrome bookmarks from my Google account? A: No. Account bookmarks are the live copy, not a backup: whatever is deleted on one signed-in device is deleted in the account. Recovery has to come from a file on one of your machines. The account does keep bookmarks alive across a lost profile, though — that is a different question, below.
Q: What is the AccountBookmarks file next to my Bookmarks file? A: Your second bookmark tree. Since Chrome 134, signing in without turning sync on splits your bookmarks in two: what was already on the device stays there, in Bookmarks, and what you save afterwards goes into your Google Account, in AccountBookmarks. Chrome merges the two into one bar, which is why most people have two "Bookmarks Bar" folders and have never noticed.
Q: Where is AccountBookmarks.bak? A: It does not exist, on any platform or any version. Chromium writes a backup for the device bookmarks file only — the account tree is excluded deliberately. So a comparison of Bookmarks against Bookmarks.bak says nothing at all about bookmarks that were in your Google Account, and coming up empty is not evidence they are unrecoverable.
Q: My profile is gone. Are the bookmarks I saved to my Google Account gone too? A: No, if you were signed in without sync. Those bookmarks lived in the account rather than on that disk: sign in again on a new profile and the account tree comes back with them. What the profile took with it is the device tree — the bookmarks in the Bookmarks file, which existed on that machine only.