Why bookmark backups matter more than you think

Bookmarks look permanent until they are not: a profile reset, a reinstall, a sync conflict, a hijacked account, or a laptop that simply stops booting. Unlike documents, most people never back them up — yet a well-kept bookmark collection often represents years of curation.

The good news: every major browser can export and import bookmarks in seconds. The better news: there is a routine that makes this almost maintenance-free.

Chrome

Export

  1. Open chrome://bookmarks/
  2. Click the ⋮ menu in the top right
  3. Choose Export bookmarks — you get an HTML file

Import

Same menu → Import bookmarks → select the HTML file. Chrome merges the file into an existing “Imported” folder.

Where the live data lives: your Chrome profile folder, in a Bookmarks file (JSON). Copying the whole profile folder works, but only when Chrome is closed.

Edge

Identical flow to Chrome: edge://favorites/ → ⋯ → Export favourites / Import favourites.

Firefox

  1. Open the Library with Ctrl+Shift+O (Cmd+Shift+O on macOS)
  2. Import and Backup → Export Bookmarks to HTML
  3. To restore: same menu → Import Bookmarks from HTML

Firefox also keeps automatic JSON backups under bookmarkbackups in your profile — genuinely useful if you catch a problem early.

Safari

Safari hides this behind the File menu:

  1. File → Export → Bookmarks… (produces HTML)
  2. To restore: File → Import From → Bookmarks.html

Safari also syncs through iCloud if you have it enabled, but sync is not a backup — deletions propagate.

The trap with HTML exports

HTML exports are universal and portable, but they are flat: folders survive, ordering mostly survives, your tags and notes usually do not. They are a snapshot, not a working format.

If you restore an HTML export into a browser that already has bookmarks, you get duplicates. Always restore into a clean profile, or import into a folder you can delete afterwards.

A better routine: keep your own copy in JSON

A practical setup that avoids the whole problem:

  1. Keep your working collection in a tool that can export JSON — NavProject does this from the About dialog, and stores everything locally in your browser rather than on a server.
  2. Export once a month to a file you actually back up (cloud drive, NAS, or a synced folder).
  3. If a browser profile dies, import that JSON back into the tool and export HTML only when you need it in a browser.

Why JSON? It keeps your structure, ordering, descriptions and settings — and it is diff-able, so you can see what changed. See Import/Export in the app for the exact flow.

Sync vs backup: know the difference

Sync Backup
Copies changes automatically ✅ ❌
Protects against accidental deletion ❌ (deletes propagate) ✅
Survives account loss ❌ ✅
Needs a deliberate action ❌ ✅

Sync is convenience. Backup is insurance. You want both.

FAQ

Where does Chrome store bookmarks without an account? In your local profile folder on disk, in a file called Bookmarks. On Windows it is typically under %LocalAppData%\Google\Chrome\User Data\Default\.

Does uninstalling a browser delete bookmarks? Removing the browser usually leaves the profile behind, but a “reset” or a clean reinstall can wipe it. Export first.

Can I merge two bookmark collections? Yes, but do it in a tool that shows you duplicates — importing one HTML file into another browser is the usual way duplicates appear.

How often should I back up? Monthly is enough for most people; weekly if you save links daily.

Are HTML exports readable? They are plain HTML, so you can open them in any browser and click through your bookmarks — a decent last-resort fallback.