Partly. The export menu can't be scripted, but the browser's live bookmark file can simply be copied — it is a normal file, and any backup tool that covers your profile folder captures it. Copy it while the browser is closed, or you may catch a half-written state.

Is a cloud drive enough on its own?

For the exported file, yes. For a synced browser profile stored in a cloud drive, no — that's still sync, with the same deletion problem, plus a real risk of profile corruption from two machines writing at once.

Should I back up the browser's own file as well as the export?

Only if you rely on something the export drops — Firefox tags and keyword shortcuts, or Safari's Reading List. Otherwise the export is the more useful artefact, because anything can read it.

How big should the file be?

Roughly 100-200 bytes per bookmark, so a few thousand bookmarks make a file under a megabyte. Much larger usually means embedded favicons, which is harmless. Much smaller than expected means you exported the wrong profile.

What about a password manager's built-in bookmarks?

Same principle: export to a portable format on a schedule. Any store you cannot get a plain file out of is a store you do not have a backup of.

How to back up your bookmarks (and why sync isn't a backup)

Export a bookmarks.html file and keep it somewhere that isn't a browser profile. That's the whole backup strategy. It is plain text, every browser can import it, and nothing — not sync, not a reinstall, not a corrupted profile — can reach back and change it.

Why sync is not a backup

Sync's job is to make every device match, which includes matching your deletions.

Delete a folder of four hundred bookmarks on your laptop and your phone loses them within seconds — faithfully, by design, exactly as instructed. A backup is defined by being unreachable from the thing it protects against, and sync is the opposite: it is permanently connected to the mistake you are about to make.

Sync is excellent at what it does. It protects you from losing a laptop. It does not protect you from losing your bookmarks.

Making the backup

Chrome, Edge, Brave, Opera: Ctrl+Shift+O (⌘+⌥+B on Mac) → ⋮ menu → Export bookmarks
Firefox: Ctrl+Shift+O → Import and Backup → Export Bookmarks to HTML
Safari: File → Export → Bookmarks

Name it with the date and the browser — bookmarks-2026-07-chrome.html — so a folder of them reads as a history rather than a pile of files called bookmarks (3).html.

Where to keep it

Anywhere that isn't managed by a browser. A Documents folder, a cloud drive, an external disk, an email to yourself. The file is small and boring, which is exactly what makes it durable.

Keep the last three or four rather than overwriting one. Bookmark loss is often noticed weeks late, and a single backup made after the loss is worth nothing. Dated files cost a few hundred kilobytes and remove that failure mode entirely.

How often?

Quarterly is enough for most people; before any browser or computer change, always.

The moments genuinely worth an export are the risky ones: switching browsers, setting up a new machine, a major OS update, or any point where you are about to click something in a profile folder. Those are also exactly the moments people skip it.

Check the backup is actually good

An untested backup is a guess. Drop the file into the bookmarks file viewer — it opens locally, nothing is uploaded — and confirm the count looks right and your folders are there.

This takes a few seconds and catches the failure that matters: an export made from the wrong profile, or after the loss rather than before it. A file that exists is not the same as a file that contains your bookmarks.

Back up less, not more

Most long-lived bookmark collections are a third dead links and a fair number of duplicates. Before filing an export away, it is worth running it through the dead link checker and the duplicate finder. The backup gets smaller, more useful, and considerably less depressing to restore from.

Keep the raw export too, at least once. Cleanup tools make judgement calls, and the unedited file is your appeal.

Browsers back up too — quietly

Yours already keeps something, though not for long and not where you'd look. Firefox writes dated snapshots into a bookmarkbackups folder; Chromium browsers keep a single Bookmarks.bak that is overwritten at every launch; Safari relies on iCloud archives. These are worth knowing about for recovery, but none of them is a substitute for a file you control — they all live inside the profile, and they all disappear with it.

Common questions

Can I automate this?: Partly. The export menu can't be scripted, but the browser's live bookmark file can simply be copied — it is a normal file, and any backup tool that covers your profile folder captures it. Copy it while the browser is closed, or you may catch a half-written state.
Is a cloud drive enough on its own?: For the exported file, yes. For a synced browser profile stored in a cloud drive, no — that's still sync, with the same deletion problem, plus a real risk of profile corruption from two machines writing at once.
Should I back up the browser's own file as well as the export?: Only if you rely on something the export drops — Firefox tags and keyword shortcuts, or Safari's Reading List. Otherwise the export is the more useful artefact, because anything can read it.
How big should the file be?: Roughly 100-200 bytes per bookmark, so a few thousand bookmarks make a file under a megabyte. Much larger usually means embedded favicons, which is harmless. Much smaller than expected means you exported the wrong profile.
What about a password manager's built-in bookmarks?: Same principle: export to a portable format on a schedule. Any store you cannot get a plain file out of is a store you do not have a backup of.

Back up your bookmarks