You want to switch browsers. Maybe Chrome is eating your RAM, maybe you are moving to Firefox for privacy, maybe you got a new laptop and it came with Edge. And one thing is holding you back. The pile of bookmarks you have collected over years, the ones you actually go back to.
The fear is reasonable. Bookmarks feel fragile. Do the move wrong and you picture that whole folder tree just gone, or worse, split into two half-copies that never match. So people put it off and keep using a browser they do not like, held hostage by a list of links.
Here is the good news. Moving bookmarks between browsers is one of the most solved problems on the internet, and it takes about two minutes. The trick is one file format that every browser has spoken since the 1990s. The catch is a few traps that turn a clean move into a duplicated mess, plus one thing the transfer quietly leaves behind that nobody warns you about.
- Export to an HTML file, then import it. Every major browser reads the same bookmark format, so Chrome, Firefox, Edge, and Safari all trade files cleanly.
- The whole move takes about two minutes and keeps your folder structure intact.
- The duplicates trap: importing adds, it never replaces. Import once, into a clean profile.
- An HTML file is a snapshot, not a sync. New saves in the old browser will not appear in the new one.
- Browser bookmarks are only half your saves. Your X, Reddit, and LinkedIn saves do not move with any export.
The one method that works in every browser
There is a single format that solves this, and it is worth knowing its name so you recognize it in every menu. It is the Netscape Bookmark File Format, a plain HTML file that stores your bookmarks and their folders in a nested list.
It sounds obscure. It is anything but. It was introduced by Netscape Navigator in the 1990s and became the de facto standard that never died. The file format archive notes it is still the format every major browser uses to export and import. Chrome, Firefox, Edge, Safari, Brave, Opera, they all read it and all write it. That is the whole reason cross-browser moves work. Nobody has to agree on anything new. They all already agreed, thirty years ago.
So the method is always the same two steps. Export your bookmarks from the old browser into an HTML file. Import that HTML file into the new browser. The file carries your links, their titles, and your folder tree in one pass. No account, no extension, no cloud.
The one thing to know before you start. This file is a snapshot, a photo of your bookmarks at the moment you export. It is not a live connection. We will come back to what that means, because it is where “without losing them” actually gets tested.
How to export bookmarks from your old browser
Each browser hides the export button in a slightly different drawer. Here is where to find it in the four big ones.
| Browser | How to export to HTML |
|---|---|
| Chrome | Menu (⋮) → Bookmarks and lists → Bookmark Manager → the ⋮ inside it → Export bookmarks |
| Firefox | Menu → Bookmarks → Manage bookmarks → Import and Backup → Export Bookmarks to HTML |
| Edge | Favorites (Ctrl+Shift+O) → the ⋯ menu → Export favorites |
| Safari | File menu → Export → Bookmarks (saves a Safari Bookmarks.html file) |
In every case you get a file, usually named bookmarks.html or favorites.html, saved wherever you point it. Put it on the desktop for now. That single file is your entire collection, safe and portable. Google’s own Chrome bookmarks guide and Mozilla’s Firefox export guide both walk the exact clicks with screenshots if a menu has moved in your version.
One quiet tip. Even if you are not switching browsers, export this file once a month and keep it in a folder somewhere. It is a free backup of years of curation, and it weighs almost nothing.
How to import them into your new browser
Same idea in reverse. Open the new browser and find its import option.
| Browser | How to import an HTML file |
|---|---|
| Chrome | Menu (⋮) → Bookmarks and lists → Import bookmarks and settings → Bookmarks HTML File |
| Firefox | Manage bookmarks → Import and Backup → Import Bookmarks from HTML |
| Edge | Favorites (Ctrl+Shift+O) → ⋯ → Import → Favorites or bookmarks HTML file |
| Safari | File menu → Import From → Bookmarks HTML File |
Pick your file, click open, done. Your bookmarks land with their folders. Microsoft’s Edge import guide and Apple’s Safari import guide cover the same step for those two.
Most browsers also offer a direct import that skips the file entirely. On the same computer, the new browser can read the old one’s bookmarks straight out of its profile, and this route can also grab passwords, history, and autofill, which the HTML file cannot. If both browsers are on one machine, direct import is faster. The HTML file is for when they are not, or when you are pulling from several browsers at once.
What “without losing them” actually means
The export and import are the easy part. Losing bookmarks does not happen in that step. It happens in the small traps around it. Here are the four that catch people.
Duplicates, because import adds, it never replaces. This is the number one way a clean move turns messy. If you import the same HTML file twice, or import into a browser that already has some bookmarks synced in, you do not get a merge. You get two copies of everything, often dumped in a folder called “Imported” or “Other bookmarks.” The fix is discipline, not software. Import once, into a fresh profile. If you do end up doubled, delete the whole extra Imported folder and re-do it clean, rather than trying to dedupe by hand.
Favicons do not travel. The little site icons next to each bookmark are not stored in the HTML file. They rebuild themselves as you visit each page again. So for the first day your shiny new bookmark bar looks like a row of blank pages. Nothing is lost. The icons just have to reload. Do not panic and re-import.
It is a snapshot, so the two browsers drift. The moment you finish importing, the file is stale. Every new bookmark you save in the old browser is not in the new one, and vice versa. If you keep using both, they quietly diverge until you cannot remember which link is where. Pick one browser as home after the move, or you recreate the split-pile problem we cover in browser bookmarks vs social bookmarks.
Turning on sync can overwrite. If you sign into a sync account on the new browser right after importing, and that account already holds an older bookmark set, sync may reconcile in a direction you did not expect. Finish your import, confirm the bookmarks look right, and only then sign into sync. Do it in that order and nothing gets clobbered.
Get past those four and the move genuinely is lossless. Your links and folders arrive exactly as they left.
Should you just use sync instead?
Fair question. If you are staying inside one browser family, sync beats the file every time. Sign into Chrome on every device and your bookmarks follow you automatically, no export needed. Chrome alone can hold up to 100,000 synced bookmarks across your signed-in devices.
But sync has one hard wall. It only works within the same browser. Chrome sync does not reach Firefox. Safari’s iCloud sync does not reach Edge. The second you switch families, or want a single view across several browsers, sync cannot help you and the HTML export is the only bridge. There are cross-browser sync extensions that try to fill this gap, but they add an account and a moving part, and they are overkill for a one-time move.
So the honest rule. Staying in one browser forever, use its sync. Moving browsers, or living across a few, use the HTML file. It is the tool that does not care whose logo is on the window.
The half of your saves that never moves
Now the thing nobody warns you about, and it is the reason a bookmark move can feel weirdly incomplete.
Your browser bookmarks are only part of what you have saved. Think about where you actually keep interesting things these days. The X thread you saved mid-scroll. The Reddit post you tapped to keep. The LinkedIn update you bookmarked. None of those are browser bookmarks. They live inside each app, on that platform’s servers, and no bookmark export on earth touches them. You can move every browser bookmark perfectly and still leave the bigger, more useful pile exactly where it was, stuck in three apps that barely let you search it. That gap is the whole reason saved posts go missing.
And even the bookmarks you did move come with the same old problem. They are searchable by title only. Move a thousand links to a new browser and you have moved a thousand links you still cannot find by meaning, only by remembering the exact words in the title. You relocated the junk drawer. You did not fix it. That is the core failure of folder-based bookmarking in the first place.
This is the gap I built ContextBolt to close, so weigh that as you read it. It is a Chrome extension that captures what you save on X, Reddit, and LinkedIn into one place that lives on your own machine. It stores the content of each post, not just a link, so a save survives the author deleting the original. It auto-tags every save by topic, so your collection sorts itself instead of rotting in folders. And it searches by meaning, so you can look for “growing a small team” and surface a post that said “scaling our first five hires” without typing those exact words. The mechanics are in semantic search for bookmarks.
Basic is free and covers 150 saves with AI tagging and semantic search. Pro at $6 a month lifts that to unlimited, adds encrypted cloud sync, and gives you an MCP endpoint so tools like Claude can read your saves directly in a conversation. The point is not to replace your browser bookmarks. It is to catch the half of your saved life that no browser export was ever going to move.
The honest take
Moving bookmarks between browsers is not the scary part it feels like. Export to HTML, import the file, watch for duplicates, pick one browser as home. Two minutes, and thirty-year-old plumbing does the work. Do not let a list of links keep you on a browser you have outgrown.
But do the move with clear eyes about what it is and is not. It relocates your browser bookmarks, folders and all, and it leaves them exactly as findable, or unfindable, as they were before. It does not touch the saves trapped in your social apps, and it does not give you search by meaning. If the goal is a clean start, moving the browser is step one. Fixing how you find things again is the step that actually pays off.