Exporting your Chrome bookmarks, and where to take them next

Somewhere between deciding to leave a browser and actually leaving it sits a folder of bookmarks nobody wants to lose. Getting them out is neither hard nor hidden behind anything paid. Every major browser writes a plain HTML file with a single menu command, and that file works everywhere else too.

Whatever prompted this, a slow browser, a new Mac, or simply wanting your links to live somewhere other than inside one company's software, the mechanism is identical and it needs nothing installed. This covers the exact steps for Chrome, Safari, Firefox and Edge, what actually ends up inside the file once you have it, and what is worth doing with it afterward: a backup, a straight move into another browser, or something that turns the list back into pictures.

How do you export your bookmarks from Chrome?

Chrome keeps this three clicks deep inside its bookmark manager. It costs nothing, needs no extra software, and takes under a minute.

1. Open Chrome and click the three dots in the top right corner. This is the More menu, sometimes shown with no label at all.
2. Go to Bookmarks and lists, then choose Bookmark Manager. On a Mac the shortcut is Command-Option-B; on Windows it is Control-Shift-O.
3. Click the three dots at the top of the Bookmark Manager, then choose Export Bookmarks. This is a separate menu from the one you opened Chrome with.
4. Choose where to save the file, then click Save. Chrome names it bookmarks, followed by today's date, though the name does not matter.

That is the whole job. Google's own Chrome Help documentation covers the same steps for exporting, and for importing a file back in.

What about Safari, Firefox and Edge?

The steps are just as short in the other three, and the file each one produces opens cleanly in any of the others. That is not a coincidence, and the next section explains why.

Safari

1. Open Safari and click File in the menu bar. Not the settings icon, the actual File menu.
2. Choose Export Bookmarks.
3. Pick a name and a location, then click Save. Safari defaults to your desktop.

Firefox

1. Click the menu button in the top right, then Bookmarks, then Manage Bookmarks. This opens a separate Library window.
2. In the Library window, click Import and Backup, then choose Export Bookmarks to HTML.
3. Pick a location and click Save. Firefox names the file bookmarks.html by default.

Edge

1. Click the three dots in the top right, then Favorites. Or press Control-Shift-O.
2. Click the three dots at the top of the Favorites panel, then Export favorites.
3. Choose a location and click Save. Edge names the file favorites, followed by the date.

What is actually inside the file you just saved?

Open it in a text editor rather than a browser and it reads as plain HTML, built on an old format called the Netscape Bookmark file. That shared format is exactly why every browser can read every other browser's export without any conversion step in between. Each bookmark carries three real pieces of information: its title, its URL, and the date it was added. Folders are preserved too, nested exactly as you built them, written out as ordinary HTML lists.

That is genuinely all of it. There is no article text, no screenshot of the page, and no preview image. A bookmarks file has never stored what a page looks like, only where it is and what you called it.

Why does that matter if you want to see the pages, not just a list?

This is the gap between a bookmarks file and a visual library. Import the file into something that just reads it back, and you get exactly what was in there: a title and a link. Anything that shows you a preview, a screenshot or a thumbnail of the page had to go and fetch that separately, after the import, because the export never carried it in the first place. That is true of any tool built around bookmarks, not just one particular app. A destination that promises pictures instead of a list is promising to do that fetching work on your behalf, not admitting that the export file was somehow incomplete.

Muse works this way with a bookmarks file from Chrome, Safari or any other browser. It reads the titles, URLs, dates and folder structure straight out of the file, then requests each page's preview image and site icon itself, so a saved link ends up looking like the thing it points to rather than a line of blue text.

What should you actually do with the file?

Three sensible things, and they are not mutually exclusive.

Keep it as a backup. This is worth doing on its own, regardless of what app you end up using next. A bookmarks.html file sitting in a folder you control is a real, portable copy of years of saved links, in a format that has barely changed since the 1990s and will very likely still open in another twenty years. Do this even if you have no immediate plan for the file.

Import it into another browser. Every browser above has an Import option that reads the same file format straight back in, folders and all. This is the route if you are simply moving from Chrome to Safari or Firefox and want the same list waiting for you in the new one.

Import it somewhere that shows the pages rather than lists them. If a folder tree of blue links was the actual problem, a bookmarks file is also the input a visual library needs. Muse imports bookmark files from Chrome, Safari and other browsers, rebuilds the folder structure as collections, and fetches a preview for each link as it comes in, so the list turns into something you can recognise on sight rather than read line by line.

None of that requires deciding anything up front. The file is small, it costs nothing to make, and having it changes nothing about how you use the browser you exported it from. It is only useful the day you actually need it.