Firefox Add-ons approved the first version. The owner reported it on 2026-11-21. AMO's public API shows the add-on public, version 1.3.0, Firefox 140 or later, slug "bookmarkmagic". Both the slug URL and the gecko-id URL the About link uses answer 200. - README: the Firefox install row links the listing, with an AMO version badge beside the Chrome Web Store and Edge ones. - docs/00: the Type line, the 1.3.0 status (live on all three stores), §9 (gecko id, slug, listing), §10 item 21 done and item 24 done. Item 23's automation state was re-checked and is unchanged: firefox-add-ons still does not exist. - docs/13 §8 and store/listing.*.md: the licence to pick is "GNU General Public License v3.0 or later". AMO offers "v3.0 only" beside it, and that is what the listing ended up with (GPL-3.0-only, per the API) — the docs only said "v3.0". Item 21 keeps it open, along with the empty support site. - docs/15 and CLAUDE.md: Firefox Add-ons live; 1.3.0 is on all three. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
12 KiB
BookmarkMagic
Move your bookmarks between browsers the simple way: with a file. No account, no cloud sync, 100% offline.
A browser extension (Manifest V3) for importing, exporting and editing bookmarks and folder trees — for Chrome and the other Chromium browsers, and, since 1.3.0, for Firefox. English · Tiếng Việt · 日本語 · 简体中文 · Română.
Project status
Maintenance mode since 2026-11-18 — see MAINTENANCE.md.
Bug, UI/UX, accessibility and translation fixes, dependency and security
updates, and features already on the roadmap still land; requests for new
features beyond that are closed automatically. Ideas are welcome in
Discussions › Ideas.
Screenshots
| Import | Edit |
|---|---|
![]() |
![]() |
| Export | Settings |
|---|---|
![]() |
![]() |
Taken with neutral sample data by node scripts/screenshots.mjs --shoot, never
from anyone's real profile.
What it does
- Import HTML, CSV and JSON bookmark files — including Chrome's own
Bookmarksfile from the profile folder and Firefox's JSON backups, the copies you have when a browser will not start. A full preview comes first: counts, folders, depth, duplicates and warnings before anything is written. - Choose how: into a new dated folder (the safe default), merged into the folders you already have (reused, not copied), or replacing everything. Replace tells you exactly what it will delete, saves a JSON safety backup first, and deletes nothing until that backup is proven — and restoring that backup puts the Bookmarks bar, Other and Mobile bookmarks back where they were.
- Export everything, or just the folders you pick, to HTML (Chrome, Edge, Brave, Firefox, Safari, Vivaldi, Opera), JSON, CSV or Markdown.
- Edit the tree: search, rename, drag to move or reorder, sort a folder A→Z, create folders, delete, and find duplicate links — every action reachable from the keyboard.
Accessibility
Everything works without a mouse, a screen reader is told what is on screen and what an import did, contrast themes and reduced motion are respected, and the page declares the language you chose. The goal is WCAG 2.2 AA; it is a goal, not a claim — nobody has audited it.
ACCESSIBILITY.md has the detail: the keys, what was
tested and with which screen reader, what is known not to work well yet, and
how to report a barrier.
Privacy
This is the whole point of the project, so it is worth being precise.
- No network access at all. Not analytics, not telemetry, not update pings.
There is no server, and the code makes no network calls. The browser backs
that up: the extension's content security policy — the same in Chrome, Edge
and Firefox — makes the browser refuse fetch, XHR, WebSocket, EventSource and
beacon requests, and remote images, fonts, media and frames. On top of that,
npm run check:manifestscans both shipped packages for network APIs (WebRTC included, which no CSP directive covers) andnpm run guardscans the source. - Exactly two permissions:
bookmarksandstorage. No host permissions, no content scripts, no background worker. Two gates enforce it: a unit test overwxt.config.ts, andnpm run check:manifest, which CI runs against the builtmanifest.json— because a build can add what the config never asked for. - Zero runtime dependencies. Nothing is installed at runtime; the only
third-party code in the package is what the build compiles in — the Svelte
runtime with its
clsxhelper and WXT's one-line browser shim, all MIT (legal/THIRD_PARTY_NOTICES.md). The build fails if anything else would ship. - A short diagnostics log (error codes and counts, never titles or addresses) lives in memory while a tab is open, so you can copy it into a bug report. It never leaves your computer unless you paste it somewhere.
- Settings use
chrome.storage.local, neverstorage.sync, so even your preferences stay off any vendor cloud.
Full policy: legal/PRIVACY.md.
Honest limitations
- Favicons cannot be imported — the bookmarks API has no favicon field.
- Imported bookmarks get today's date. Browsers do not let an extension set a bookmark's original creation date. Your exported files keep the real ones.
- Firefox separators are not kept. They show in the Edit tab as lines, but no file BookmarkMagic writes can hold one: exports and backups leave them out, imports skip the ones a file holds and say how many, and Replace — which deletes them with everything else — tells you so before it starts.
- Firefox refuses bookmark addresses longer than 65,536 characters (they are skipped, and counted) and shortens titles longer than 4,096.
- On Firefox, entries a file leaves loose at its top level go into the Bookmarks Menu, where Firefox's own import puts them. For an HTML file exported by Chrome itself, that means Chrome's Other and Mobile bookmarks; BookmarkMagic's own exports name every root and land where they came from.
- CSV is a flattened view: empty folders and "which folder is the toolbar" are not preserved. Use HTML or JSON for a faithful backup.
- Markdown is share-only — BookmarkMagic cannot read it back.
Install
| Browser | Where | Requires |
|---|---|---|
| Chrome, Brave, Vivaldi, Opera | Chrome Web Store | Chrome 136 or later (April 2025), or a Chromium browser of the same vintage |
| Microsoft Edge | Edge Add-ons | Edge 136 or later |
| Firefox (desktop) | Firefox Add-ons | Firefox 140 or later. Firefox for Android has no bookmarks API for extensions |
On an older browser the store keeps the version you already have and simply stops updating it.
Each GitHub Release carries
the exact packages sent to the stores, with SHA256SUMS.txt. Firefox only
installs add-ons Mozilla has signed, so its -firefox.zip there is for
checking the store build, not for installing.
From source (Node.js 26) — BUILD.md has the details:
npm ci && npm run build # Chromium: load .output/chrome-mv3/ at chrome://extensions (Developer mode)
npm run build:firefox # Firefox: about:debugging → Load Temporary Add-on → .output/firefox-mv3/manifest.json
Development
npm run dev
npm run verify is the gate everything else answers to — lint, type-check
(svelte-check on the TypeScript 6 API, then tsc 7), knip, the grep gate, the
licence gate and the test suite, in that order. It must be green before every commit;
npm run verify:full adds coverage, the build and the built-manifest check,
and must be green before anything release-bearing.
node scripts/screenshots.mjs serves the built extension with sample
bookmarks and a fake chrome, for looking at every page without loading the
extension (--shoot also captures the store screenshots).
The docs/ directory is the binding specification, not notes: where
code and docs disagree, the docs win. Start with CLAUDE.md, then
docs/00–docs/02.
Contributing
Bug reports and translation fixes are welcome —
the issue forms
ask for what is needed, and none of them requires you to write code. The
project is in maintenance mode, so a request for a feature that is not on the
roadmap is closed automatically (MAINTENANCE.md).
If a bookmark file will not import, that is the most useful report there is, because the sample becomes a permanent test. Sanitize it first:
node scripts/sanitize-bookmarks.mjs your-bookmarks.html
That strips every address and title but keeps the structure, encoding and timestamps a parser bug depends on — so the sanitized file still reproduces the problem without handing over your browsing history.
CONTRIBUTING.md has the rest: the setup, the rules that are
not negotiable, and how a reported file becomes a regression test.
Security issues: please follow SECURITY.md rather than opening
a public issue.
Contact
| For | Write to |
|---|---|
| Security vulnerabilities (if you have no GitHub account) | security@poli0981.dev |
| Privacy questions, removing a sample you sent | privacy@poli0981.dev |
| An accessibility barrier (if you have no GitHub account) | accessibility@poli0981.dev |
| The terms (EULA, disclaimer) | legal@poli0981.dev |
| Licensing and permission questions | copyright@poli0981.dev |
| Formal copyright (DMCA) notices | dmca@poli0981.dev |
| A copy or listing pretending to be BookmarkMagic | takedown@poli0981.dev |
| Contributing and code of conduct | code@poli0981.dev |
| Sponsorship · collaboration · press | sponsor@ · collab@ · press@poli0981.dev |
Bugs are best as issues and ideas as Discussions — they help the next person too. The extension itself never shows or uses any of these addresses.
Support development
Entirely optional — BookmarkMagic is free software either way.
GitHub Sponsors · Ko-fi · Buy Me a Coffee · Patreon · PayPal
Licence
Copyright © 2026 skullmute (poli0981).
GPL-3.0-or-later. Also see legal/EULA.md,
legal/DISCLAIMER.md and
legal/THIRD_PARTY_NOTICES.md. Licensing
questions: copyright@poli0981.dev.
The BookmarkMagic name and icon identify this project. The GPL lets anyone fork the code; it does not let a fork present itself as this project.
Not affiliated with or endorsed by Google, Chrome, Mozilla, Firefox, Microsoft, Edge or any browser vendor. Browser names are trademarks of their respective owners.



