How to actually back up your bookmarks because sync does not count

Ask most people whether their bookmarks are backed up and they will say yes, because Chrome or Safari shows the same list on their phone, their laptop and their work Mac. That feeling is not wrong exactly. It is just answering a different question. Sync keeps your devices agreeing with each other. A backup keeps an old copy of your data safe from what you do to the current one.

The gap between those two only shows up at the worst moment, after a bookmark, a folder, or an entire bookmarks bar is already gone. Understanding what sync actually does, then adding a real export habit on top of it, closes that gap properly.

What does browser sync actually protect you from?

Sync solves a genuine, common problem: losing a device. Google's own explanation of Chrome sync is that once you are signed in, your bookmarks and other browsing data are saved to your Google Account, and if you change devices, lose your phone or buy a new laptop, you can get that saved information back. Apple's iCloud sync for Safari works the same way in principle: sign in on a new Mac or iPhone, and the same bookmarks appear there too.

That is real protection, and worth having. A stolen laptop or a phone dropped down a drain used to mean starting a bookmarks list from nothing. Sync removes that particular disaster.

What does sync not protect you from?

The part sync does not cover is anything that happens to the data itself, on purpose or by accident. Sync's whole job is to make every signed-in device match the current state. That includes the bad states, not only the good ones.

Apple is unusually direct about this in its own documentation. Its guide to keeping Safari in sync with iCloud explains that because your information is stored in iCloud, changes you make on one device automatically appear on all your other devices, and gives a plain example: remove an item from your Reading List on your iPad, and it is removed everywhere. Bookmarks sync through the same iCloud mechanism and behave the same way. Delete a folder of bookmarks on your Mac by mistake, and the next time your iPhone syncs, that folder is gone there too.

The same logic covers sync errors, not just your own mistakes. Sync engines occasionally misfire, a botched update, a corrupted local profile, or a bad merge after being offline for a while can send an incomplete or duplicated list out to every device at once. When that happens, sync is not a safety net. It is the mechanism that spreads the damage.

How do you export your bookmarks in Chrome?

Chrome writes a plain HTML file, and it takes under a minute. Google's own support documentation covers the same steps, and the file it produces opens in any browser, not only Chrome.

1. Open Chrome and click the three dots in the top right corner. This is Chrome's main menu.
2. Go to Bookmarks and lists, then choose Bookmark Manager. This opens a full page listing every bookmark and folder.
3. Click the three dots at the top of the Bookmark Manager, then choose Export Bookmarks. Chrome writes a file named bookmarks, followed by the date.
4. Save it somewhere other than your Desktop. Where exactly is covered further down.

The full detail, including how to bring that file back into another browser, is in the guide to moving bookmarks out of Chrome.

How do you export your bookmarks in Safari?

Safari's export sits in the File menu, though the exact wording depends on which macOS you are running. Apple's own Safari support documentation covers the current version, which arrived with macOS Sequoia in late 2024.

1. Open Safari and click File in the menu bar. On macOS Sonoma, this shows Export, then Bookmarks, saving a file called Safari Bookmarks.html directly.
2. On macOS Sequoia or later, choose Export Browsing Data to File instead. Select Bookmarks from the list before continuing.
3. Click Save and choose a location. Apple's own guidance notes the export carries no encryption, so treat the file with the same care as anything containing your browsing history.
4. Open the result to confirm it worked. A proper export contains your whole bookmarks bar and folder structure, not just a handful of top-level items.

The version-by-version detail is in the guide to exporting and moving Safari bookmarks.

Where should that export file actually live?

Desktop is the default save location in both browsers, and it is a poor choice for a backup. A file sitting on the Desktop is on the same drive as everything else, so whatever takes out your Mac, a failed drive, a bad reinstall, a spilt drink, takes the backup out with it too.

A better home is somewhere separate from the machine that made the file: an external drive, a folder inside iCloud Drive or Dropbox that also lives on another device, or both. The specific service matters less than the principle. Losing the Mac should not also mean losing the export.

Keep the browser's own dated filename, or add a date yourself, rather than saving over the same bookmarks.html each time. One named copy per export makes it possible to see when something specific went missing, rather than only what the list looks like right now.

Is doing this once actually a backup?

A single export is a snapshot, frozen at the moment you made it. That is genuinely useful once, right after reading this, but it is not yet a backup in any meaningful sense. A backup implies a system: the same action, repeated on a schedule, so the gap between the copy and reality never grows too wide.

This is exactly where manual exports tend to fail in practice. Nobody keeps a recurring reminder for something that feels like a chore, and after a few months the file people reach for during an actual loss covers only half of what they had saved by then. A once-off export is better than nothing, but it is a promise to your future self that is easy to forget making.

Worth being honest about this in both directions. A tool that keeps a persistent copy of everything you save, the moment you save it, removes the remembering entirely: there is nothing to schedule and nothing to forget. That is the part of this problem Muse actually solves. It does not solve the rest of it. Muse does not sync between devices, so a bookmark saved into Muse on one Mac does not appear on another. It does not archive the page behind a link either, so a saved page that later goes offline is exactly as gone as it would be anywhere else, a limit covered properly in the guide to link rot. What Muse keeps is the bookmark itself: its title, preview, tags and any note, sitting in a library on your Mac independent of whatever your browser is doing with its own copy. That covers one part of a proper backup habit, not the whole of it.