Move your Chrome, Safari, Firefox or Edge bookmarks to Marqly
All four browsers export to the same Netscape bookmark HTML format, so there is one honest answer about what transfers — and it is written from the importer Marqly actually runs in production, not from marketing slides. Folders become boards, URLs and titles come verbatim, saved dates do not survive, and this page shows you exactly where to check after the import.
Chrome
Address bar: chrome://bookmarks → three-dot menu → Export bookmarks. Saves bookmarks_<date>.html to your Downloads folder. Tip: if you sign in with multiple profiles, export from each — they are separate files.
Edge
Favorites bar (Ctrl+Shift+O) → three-dot menu → Export favorites. Same HTML format, same fields.
Safari
Bookmarks → Export Bookmarks… from the menu bar. Safari writes any bookmark description into the file; iCloud-synced devices all read the same library, so one export covers the whole account.
Firefox
Menu (≡) → Library → Import and Backup → Export Bookmarks to HTML… Firefox is the only one of the four that exports tags with every bookmark.
Why move a plain bookmark folder into Marqly at all?
Browser bookmarks store a name and a URL and then quietly rot: the tab you meant to return to lives behind four folder levels you never re-open, titles repeat themselves, and pages disappear. Marqly takes the same HTML file and turns it into a library you can search by describing what you remember — auto-tagging, summaries and semantic search are Pro features, and the free plan still gives you boards, tags and keyword search across the first 100 saves.
If your bookmarks actually came from a service rather than the browser, use the guide for it instead: Pocket, Raindrop.io, Diigo, Instapaper, mymind — or the migration hub.
The move, step by step
1. Export one HTML file from your browser
Chrome: open chrome://bookmarks → ⋮ menu → Export bookmarks. Edge: Favorites bar → ⋯ → Export favorites. Safari: Bookmarks menu → Export Bookmarks… Firefox: Library (≡ → Library) → Import and Backup → Export Bookmarks to HTML.
2. Preview and dedupe the file (free, in-browser)
Open the export in the bookmark file viewer to see counts, folders and repeats before anything moves. Nothing is uploaded — parsing is local. Run the duplicate finder too if you have accumulated the same URL across profile syncs.
3. Import into Marqly
Sign in at app.marqly.com (free plan needs no card) → sidebar menu → Import/Export → Import. Choose the HTML file. One file can be up to 30 MB / 10,000 bookmarks on Pro (10 MB on Free); split a huge profile into two exports by browser if needed.
Tools used above, all free and browser-local: bookmark file viewer ·duplicate finder ·research table builder (turn the imported set into a source log).
What transfers — fidelity matrix
Every row below was read out of the importer Marqly actually runs in production, plus fixture runs of each export format. Where something is lost, we say so — the point is an import you do not have to redo.
Accepted input: .html export (all four browsers write the same Netscape format)
| Field | Outcome | What it means for your library |
|---|---|---|
| URL | Supported | Verbatim — query strings (including signed or tracking parameters) and fragments are preserved; nothing is normalized away. |
| Title | Supported | With HTML entities decoded (& → &). |
| Folders / collections | Supported | Each folder level becomes a Marqly board; items land in the deepest board. |
| Nested folder depth | Partial | Boards hold two levels. Deeper paths flatten by hyphen-joining the remainder — “Research/Sources/2024/Unpublished” becomes board “Sources-2024-Unpublished” under “Research”. Nothing is lost; the name gets longer. |
| Tags | Partial | Firefox tags survive the export (TAGS attribute) and import as Marqly tags. Chrome, Edge and Safari bookmark exports contain no tags — there is nothing to preserve. |
| Notes / descriptions | Partial | Imported as the bookmark description. The current importer can pair a <DD> note with the following item and drops a folder’s very first note — open the first saves of each folder after importing and re-paste if a note landed wrong. |
| Saved date | Not supported | The export carries it (ADD_DATE/created) and the parser reads it, but the import stores items with the import date. Sort by “recently added” after a big import with that in mind. |
| Highlights / annotations | Not supported | Bookmark-file imports carry links, not page markup. Marqly highlights are created on the page after saving. |
| Favicon / extra metadata | Not supported | ICON attributes are parsed and discarded; Marqly re-fetches what it displays. |
| Duplicates | Not supported | Import writes every row; no dedup pass runs. Check the export first with the free duplicate finder, or clean up in Marqly after import. |
- URL
- Supported
- Verbatim — query strings (including signed or tracking parameters) and fragments are preserved; nothing is normalized away.
- Title
- Supported
- With HTML entities decoded (& → &).
- Folders / collections
- Supported
- Each folder level becomes a Marqly board; items land in the deepest board.
- Nested folder depth
- Partial
- Boards hold two levels. Deeper paths flatten by hyphen-joining the remainder — “Research/Sources/2024/Unpublished” becomes board “Sources-2024-Unpublished” under “Research”. Nothing is lost; the name gets longer.
- Tags
- Partial
- Firefox tags survive the export (TAGS attribute) and import as Marqly tags. Chrome, Edge and Safari bookmark exports contain no tags — there is nothing to preserve.
- Notes / descriptions
- Partial
- Imported as the bookmark description. The current importer can pair a <DD> note with the following item and drops a folder’s very first note — open the first saves of each folder after importing and re-paste if a note landed wrong.
- Saved date
- Not supported
- The export carries it (ADD_DATE/created) and the parser reads it, but the import stores items with the import date. Sort by “recently added” after a big import with that in mind.
- Highlights / annotations
- Not supported
- Bookmark-file imports carry links, not page markup. Marqly highlights are created on the page after saving.
- Favicon / extra metadata
- Not supported
- ICON attributes are parsed and discarded; Marqly re-fetches what it displays.
- Duplicates
- Not supported
- Import writes every row; no dedup pass runs. Check the export first with the free duplicate finder, or clean up in Marqly after import.
parser code + fixture runs reproducing each browser’s export layout · checked 2026-09-26 against Marqly’s deployed importer. Preview any export file before uploading it with the bookmark file viewer; clean repeats first with the duplicate finder.
Five-minute check after importing
- Count — bookmarks in the source browser ≈ saves in Marqly (minus duplicates you kept on purpose). The import dialog shows progress; a mismatch stops here, not after you cleaned the browser up.
- Depth — open one former three-level folder and confirm it reads
Parent / Child-Grandchild. - Tags (Firefox) — a couple of known tagged items should show the same tags.
- Notes (Firefox/Safari) — check the first item of a folder that had a description; the current importer shifts notes onto the following item.
- Search — keyword search works on the free plan for the whole library; semantic (“describe and find”) is Pro.
Something off? You can delete the imported batch from its boards and re-import after trimming the HTML file — the export is yours, and nothing about the import touched the browser itself.
Questions the export file won’t answer
Do my folders survive the move?
Yes — each folder becomes a Marqly board. Marqly boards hold two levels, so a deeper path like Research/Sources/2024 flattens to Sources-2024 under Research. Nothing is dropped; the third level joins into the second level’s name.
Will my saved dates come with them?
No, and this is the one row that surprises people: the export carries every ADD_DATE and the importer reads it — but the stored bookmark is dated the import day. If chronological filing matters, import in passes (oldest browser profile first) or sort by title.
Do tags transfer?
Firefox writes tags into the HTML export and they import as Marqly tags. Chrome, Edge and Safari bookmarks simply have no tags to export — the browsers never stored them.
What about bookmark notes and descriptions?
Firefox and Safari write descriptions as <DD> entries and they come through as the bookmark description. In the current importer, a note can land on the following item and the first note in each folder can be dropped — after import, open the top of each folder and spot-check. (A fix is being verified upstream; we will update this page the day it ships.)
Is anything deduplicated automatically?
No. Every row in the file becomes a save. Check repeats before uploading with the duplicate finder — free, local, no account — or clean up afterwards.
Can I undo an import?
There is no one-click undo, which is why the guide says preview first. Imports create ordinary new saves, so the recovery is ordinary: select the imported items in their board and delete them, or stop the job from the import dialog if the counts look wrong mid-flight. Your browser’s bookmarks and the export file are untouched throughout — the import never writes to your browser.
Does importing hurt my existing Marqly library?
No — imports add saves; they do not edit or delete what you already had. Duplicates of existing saves are possible if you imported a similar file before.
