Restore Chrome Bookmarks

Do this first, before you reopen Chrome

Chrome keeps exactly one backup, and it replaces Bookmarks.bak with your current bookmarks the next time it saves them, which in practice means the next time you open Chrome. If your bookmarks vanished and you have already closed and reopened Chrome a few times while trying to fix it, the backup may now be a copy of the empty version. That is the most common reason a recovery fails, and nothing can undo it afterwards.

So before anything else: close Chrome, go to the folder below, and copy both Bookmarks and Bookmarks.bak somewhere safe like your desktop. Work from those copies. Once they are out of the profile folder, Chrome cannot touch them.

Where the Chrome bookmarks file lives

The folder holds two files with no file extension, Bookmarks and Bookmarks.bak. On Windows, AppData is hidden, so paste the path into the address bar of File Explorer rather than trying to click your way there.

• WindowsC:\Users\<you>\AppData\Local\Google\Chrome\User Data\Default
• macOS~/Library/Application Support/Google/Chrome/Default
• Linux~/.config/google-chrome/Default

If you use more than one Chrome profile, the one you want may be in Profile 1, Profile 2 and so on rather than Default. Sort the folders by date modified and start with the most recent.

The other four keep the same two files in their own folders. Opera is the odd one out: it sits under Roaming rather than Local on Windows, and it has no User Data level.

• Edge%LOCALAPPDATA%\Microsoft\Edge\User Data\Default~/Library/Application Support/Microsoft Edge/Default~/.config/microsoft-edge/Default
• Brave%LOCALAPPDATA%\BraveSoftware\Brave-Browser\User Data\Default~/Library/Application Support/BraveSoftware/Brave-Browser/Default~/.config/BraveSoftware/Brave-Browser/Default
• Vivaldi%LOCALAPPDATA%\Vivaldi\User Data\Default~/Library/Application Support/Vivaldi/Default~/.config/vivaldi/Default
• Opera%APPDATA%\Opera Software\Opera StableOpera GX uses Opera GX Stable in the same parent folder~/Library/Application Support/com.operasoftware.Opera~/.config/opera

Why not just rename the file, like everyone says

The usual advice is to delete Bookmarks, rename Bookmarks.bak to Bookmarks, and restart. It does work. The problem is that it is all or nothing: whatever you have bookmarked right now is replaced by whatever was in the backup. If you lost most of your bookmarks but saved a few good ones since, you lose those too, and there is no second backup to fall back on.

Converting the backup to a bookmarks.html file and importing it instead is additive. Chrome puts the recovered bookmarks into a new folder called "Imported" and leaves everything else alone. If it turns out to be the wrong file, you delete that one folder. That is the whole reason this tool exists.

How to import the file you get back

In Chrome, open the menu, then Bookmarks and lists, then Bookmark manager. Click the three dots at the top right of the manager and choose Import bookmarks. Pick the bookmarks.html this page gave you. Edge and Brave work the same way, behind a second three-dot menu inside their own bookmarks manager.

The other two are different, and this is where people get stuck. Vivaldi has no three-dot menu in its Bookmark Manager. It has a labeled Import button in the top right of the page instead. Opera is the odd one out again. Its import and export control sits at the bottom of the left side panel, and choosing import sends you to a settings screen rather than a file dialog.

If there is no file left to read

If you had Chrome sync switched on, Google may still hold a copy. Go to Google Takeout, deselect everything, select Chrome, and request the export. It arrives as a zip containing a bookmarks file you can bring back here. It is slow, sometimes hours, and it only helps if sync was on before you lost them, but it is the one route that does not depend on a file still being on your disk.

What this tool cannot do

It reads a file you already have. It cannot reach into Chrome, recover something you never had a copy of, or pull bookmarks off a different device. If the bookmarks only ever existed on another machine and were never synced to this one, there is no local file here to read, and your route is Chrome sync on that machine or a backup taken from it.

It also does not read Firefox or Safari bookmarks. Firefox stores its bookmarks in places.sqlite with compressed .jsonlz4 backups, and Safari uses a binary property list. Both are different enough that a tool claiming to handle them alongside Chrome would be guessing. If that is what you have, our writeups on Firefox bookmarks disappearing and Safari bookmarks disappearing cover the routes that do work.

Stop losing them in the first place

A recovered bookmark folder is still a wall of blue links you will not read. The reason bookmarks get lost is that nobody misses them until they are gone, which is the same reason they never get used. Backing them up on a schedule fixes half of that, and making them searchable fixes the other half. ContextBolt keeps your bookmarks somewhere your AI assistant can actually read them, so asking "what was that article about database indexes" works instead of scrolling a folder tree.