Every browser syncs with itself.
Chrome Sync is excellent, as long as everything you own runs Chrome. The moment a second browser enters your life, the most basic feature you can imagine — one set of bookmarks — stops existing.
The short version
- Browser sync is single-vendor by design. Chrome Sync, Firefox Sync, Edge Sync and iCloud each move data between copies of one browser, tied to one company's account.
- It is a retention feature, not a data service. Your bookmarks are the reason it is inconvenient to leave, so interoperability is not on anyone's roadmap.
- Export and import give you a snapshot, not sync. An HTML file is correct for exactly as long as it takes you to add one bookmark.
- The fix is to stop storing bookmarks in a browser account. Keep them in a store that every browser talks to — which is what MarkSync is.
The problem, stated plainly
A lot of people use more than one browser, and not because they are indecisive. Work hands you a managed Chrome profile. Home is Firefox, because you chose it. The phone is Safari, because it is an iPhone, or Chrome, because it is an Android. A browser on a work machine may be locked down by policy, and a browser on your own machine is your own business.
Each of those browsers has a sync feature, and each one works well. Chrome Sync will carry your bookmarks to every other copy of Chrome you sign in to. Firefox Sync does the same for Firefox. Edge does it for Edge. Safari does it through iCloud, for Safari.
None of them will carry a bookmark to a browser made by someone else. Put differently: the feature exists four times, and the thing you actually wanted — one list of links, available wherever you are — exists zero times.
Why it is built this way
It is tempting to assume this is a hard technical problem. It is not. A bookmark is a URL, a title, a position in a folder tree and a timestamp. There is no format war to resolve, no proprietary encoding, nothing that a weekend of work could not bridge.
What there is, instead, is an incentive. Browser sync is bound to an account system — a Google account, a Mozilla account, a Microsoft account, an Apple ID — and those account systems are the product. Sync is what makes a browser sticky: it is the reason that switching browsers feels like moving house rather than opening a different window. A vendor who made it trivial to keep your bookmarks identical in a competitor's browser would be removing one of the few things that keeps you in theirs.
So the silos are not an oversight that someone will eventually fix. They are the feature working as intended, for the company that built it.
The workarounds, and where each one breaks
Export to HTML, import elsewhere
Every browser can export bookmarks to an HTML file, and every browser can import one. This genuinely works — once. What you get is a snapshot: accurate at the moment you clicked Export, and wrong the moment you save another link. Do it monthly and you have a monthly copy of your bookmarks, plus the growing suspicion that two of your folders are now slightly different from each other.
Import is also additive, not reconciling. Importing the same file twice gives you two copies of everything, which is how most people's duplicate problem starts. We wrote about that in why you have four copies of the same bookmark.
"Import from another browser" on first run
Edge and Chrome both offer to pull your bookmarks across when you set them up, and it is a nice touch. It is also a one-time copy, aimed at migration rather than coexistence. It helps the person who is switching permanently. It does nothing for the person who will use both browsers tomorrow.
Vendor bridges
There are a few narrow exceptions — Apple, for instance, offers a way to get Safari's iCloud bookmarks into a browser on Windows. These bridges are real, but they tend to cover one specific pair of products on one specific platform, and they still terminate in somebody's account. None of them generalises to "all my browsers, on all my machines".
Extensions built on a cloud drive
Plenty of extensions sync bookmarks through a file in Google Drive, Dropbox or OneDrive. Some are good. But you have usually just exchanged one account dependency for another, often with the whole bookmark file sitting in readable form in a folder that several other apps can see.
What a real fix has to look like
If the problem is that your bookmarks live inside a browser vendor's account, the fix is not a better browser vendor. It is to move the bookmarks out, into a store that is not owned by any of them, and have each browser read and write that store.
That gives you three properties the built-in features cannot:
- Browser independence. Chrome and Firefox are reading the same list, so there is no "Chrome copy" and "Firefox copy" to drift apart.
- Account independence. No sign-in to a company whose main business is something other than holding your links.
- An exit. If the store is open and documented, you can take it with you, or run it yourself.
How MarkSync does it
MarkSync is a browser extension plus a small sync service, and the extension exists for Chrome, Firefox and Edge, with a web app for everything else — including the browsers that do not allow extensions, like Safari on an iPhone.
All of them speak to the same service and read the same encrypted blob of bookmarks. There is no per-browser copy, because there is no per-browser account: you are identified by a sync ID, an anonymous string, together with a password that never leaves your device. Point a second browser at the same ID and password and it has your bookmarks.
Because the service only ever holds an encrypted blob, it is also not in a position to lock you in. The code is GPL-3.0, the API is documented, and you can run the service yourself if you would rather not rely on anyone, us included.
Where we are honest about the limits: browsers do not all model bookmarks identically — separators, tags and some folder behaviours differ — and iOS does not permit a bookmark-writing extension at all, which is why the phone story runs through the web app. MarkSync gives you one canonical list; it cannot give Safari features Safari does not have.