Recover Chrome Bookmarks from Bookmarks.bak: Step by Step (2026)

To recover Chrome bookmarks from Bookmarks.bak: close Chrome completely, copy the whole profile folder somewhere safe, open the folder listed as Profile Path at chrome://version, rename the current Bookmarks file to Bookmarks.old, rename Bookmarks.bak to Bookmarks, then reopen Chrome and check. That is the method community guides agree on. It is not documented by Google, it only restores one earlier version, and sync can change the outcome, so use it when an HTML export or another synced device is not available.

This guide gives the steps in a safe order, explains what the file is and is not, and lists the cases where it will not help. We could not reach Google’s help pages through automated checks when writing, and Google does not describe this file there as far as we can tell, so everything below about the file comes from community sources that agree on the core method and disagree on details. We flag the disagreements rather than hide them.

Before you start: what this will and will not do

It can help if	It will not help if
You deleted bookmarks this session and the .bak predates the deletion	The .bak was written after the deletion
Chrome opened a damaged or empty bookmarks file	You have no .bak file in the profile
You are not syncing, or you can pause it first	Sync overwrites the local file
You have no HTML export	You have an export (use it instead)

Step 1: try the safer routes first

If you have any of these, use them before touching profile files:

1. An HTML export. In the bookmark manager, import it. See how to export Chrome bookmarks for how those files are made.
2. A second device that still has the bookmarks. Take it offline, export an HTML file, and reconnect afterwards.
3. A bookmark manager that holds a copy.

If not, continue.

Step 2: close Chrome completely

Community guides say a running Chrome can overwrite the file, so quit Chrome from its menu, not just the window. On a computer, also check that no background Chrome process remains. Do not edit files while Chrome is running.

If you use more than one profile, remember which profile lost its bookmarks. You will recover only that profile’s folder.

Step 3: find the correct profile folder

Open Chrome one more time only to read the path, then close it again. Type chrome://version in the address bar and copy the value next to Profile Path. That is the folder for the profile in use. The folder is usually named Default or something like Profile 1, but do not guess; use the path Chrome shows you.

Open that folder in your file manager. On Windows, turn on file name extensions in the View options first, so a rename does not produce a double extension such as Bookmarks.bak.bak.

Step 4: copy before you change anything

Copy the entire profile folder to a safe location, such as your documents. If anything goes wrong, you can restore from that copy. This single step is what separates a recoverable mistake from a permanent one, and it costs a few seconds.

Step 5: look at what is there

In the profile folder, look for a file named Bookmarks and a file named Bookmarks.bak. Check their sizes and modified dates in the file manager’s details view. If Bookmarks.bak is zero bytes or missing, stop; this route cannot help you. If its modified date is older than you expected, that is information too: it is the oldest version you can get.

Newer Chrome versions may also keep an additional file for account bookmarks when a profile is signed in but not syncing. That detail comes from a community report and not from Google, so do not rely on it, but if you see an extra bookmarks file, copy it too.

Step 6: swap the files

1. Rename Bookmarks to Bookmarks.old. This keeps your current file in case the backup is worse.
2. Rename Bookmarks.bak to Bookmarks. Do not delete anything.
3. Do not open Chrome yet.

If you would rather not rename, copy Bookmarks.bak to a new name and keep the original, then place the copy under the name Bookmarks. The principle is the same: keep every original.

Step 7: reopen Chrome and verify

Open Chrome and check chrome://bookmarks. Look at several folders and recent items. If the set is right, immediately export an HTML file from the bookmark manager so you have a fresh, portable backup. If the set is wrong, close Chrome and reverse the rename: put Bookmarks.old back as Bookmarks.

Some guides say restored bookmarks may not return to their original positions and can land in Other bookmarks. Drag them back as needed.

Step 8: handle sync deliberately

If sync is on for Bookmarks, Chrome may compare the local file with your Google Account’s copy. That can overwrite your restored file with the synced state, or merge the two. Google’s own sync documentation describes synced information as available on every device signed in to the account, which is why a bad state can spread as easily as a good one.

Safer sequence: before restoring, export from the device that looks right; check the sync state; restore; export again; then check that the other devices match. Our Chrome bookmarks not syncing fix covers the sync checks without recommending a reset.

If the restored set is not quite right

A restore that brings back most of your bookmarks is still a win. Open the bookmark manager, compare against anything you remember adding recently, and re-add the missing items by hand or from browser history. If the restored file is older than the changes you wanted to keep, export it as HTML straight away. Then close Chrome and swap Bookmarks.old back in to export that version as HTML too. Importing the two HTML files into one place lets you merge the sets rather than choosing one. Merging brings duplicates, so sort the result afterwards instead of trusting either version to be complete.

Why the backup is not what you think

The community picture has three caveats:

• It is one version, not a history. There is no timeline to roll back through.
• The timing is disputed. Many guides say it is made at startup. One source we found says it is written before the first change in a session instead. Either way, it can be older than you assume.
• Google does not document it. Behavior can change between versions without notice.

That is why the file is a rescue, not a backup strategy.

What not to do

• Do not delete Bookmarks before you have copied it.
• Do not swap files with Chrome open.
• Do not trust Bookmarks.bak as your backup plan.
• Do not run a recovery utility that wants your Google password.
• Do not repeat the swap many times without copying again; each attempt can overwrite your options.

Prevent it: make real backups

1. Export an HTML file monthly using our Chrome export guide.
2. Back up every browser with this multi-browser guide.
3. Keep a second copy in cloud storage, not only on the same computer.
4. Fix sync problems early, not after a loss.

If bookmarks vanished after an update or sign-in rather than a deletion, start with Chrome bookmarks lost after an update or sign-in, since the cause is usually a different profile. And see can I export my data.

Where Marqly fits (honestly)

Marqly is a bookmark manager that keeps your library outside any one browser profile. Import the HTML file from your recovered bookmarks and folders become boards, with titles, URLs, notes and tags kept. Original save dates are not preserved and duplicates are not removed on import. The Free plan holds up to 100 bookmarks; Pro is $72 a year or $9 a month, with no free trial. The extension and the iOS and Android apps keep it reachable if a profile breaks.

It does not repair a corrupted Chrome profile or read Bookmarks.bak itself. If recovery worked and you only needed the file back, you are done. If you want a copy that does not depend on a profile folder, get started free and see bookmark sync.

Summary

1. Prefer an HTML export or another synced device.
2. Close Chrome completely.
3. Read Profile Path from chrome://version.
4. Copy the whole profile folder.
5. Check both files’ sizes and dates.
6. Rename Bookmarks to Bookmarks.old, then Bookmarks.bak to Bookmarks.
7. Reopen, verify, export an HTML file.
8. Deal with sync deliberately.