docs/13 §6 stated as present-tense fact that "GitHub issues — templates route bug reports with sample files", and docs/12 §5 carried the same as an unticked box. Neither was true: .github/ held only FUNDING.yml, dependabot.yml and workflows. Meanwhile the entire v1.0.x roadmap is "fixture + test per report", which cannot happen if reports arrive without the file that broke. Five issue forms plus a chooser, blank issues disabled. parser_report.yml is the one that matters: it requires the sanitized sample, asks which browser *version* produced the file, and asks explicitly for consent to commit the sample as a GPL-3.0 fixture — it lives in a public repo forever, and nothing previously asked. scripts/sanitize-bookmarks.mjs makes "attach a sanitized sample" something a reporter can actually do. It works by span replacement rather than by reparsing, so every byte outside a replaced address or title is provably untouched: BOM, doctype, line endings, tag and attribute case, quoting, indentation and every timestamp survive, and so do the properties a parser branches on — port, path depth, trailing slash, query-parameter count and order, percent-escapes, HTML entities, and the distinctness of hosts that dedupe depends on. Its test asserts the promise rather than the implementation: for every fixture in the repo, the sanitized file must detect as the same format, parse to the same stats, warnings and topology — or fail with the same error code — and leak no original hostname. Writing it immediately found three real defects: a data: URL containing markup broke the title regex and left that bookmark's title unsanitized; an & in an HREF came back as a bare &, silently repairing the escaping of the file being reported; and Firefox's ICON_URI leaked a full hostname past every other check. The last one is why URL-valued attributes are now swept by value shape instead of by an enumerated list. scripts/gen-fixture.mjs is the generator docs/11 §2 named, .gitignore has always reserved a directory for, and the 2 s parse budget needed in order to be measurable at all. CONTRIBUTING.md collects the five-file ritual for turning a user's file into a regression test, which was previously spread across CLAUDE.md, docs/04 and docs/11 with no single entry point — including the .gitattributes rule that stops EOL normalization destroying the bytes a bug depends on. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
BookmarkMagic
Move your bookmarks between browsers the simple way: with a file. No account, no cloud sync, 100% offline.
A Chrome (MV3) extension for importing, exporting and editing bookmarks and folder trees. English · Tiếng Việt · 日本語.
Screenshots
| Edit | Export |
|---|---|
![]() |
![]() |
| Settings | About |
|---|---|
![]() |
![]() |
What it does
- Import HTML, JSON or CSV bookmark files, with a full preview first — counts, folders, depth, duplicates and warnings before anything is written.
- Choose how: into a new dated folder (the safe default), merged into your existing folders, or replacing everything. Replace saves a JSON safety backup first and deletes nothing until that backup is proven.
- 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 & drop, create folders, delete, and find duplicate links — every action reachable from the keyboard.
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. A grep gate (
npm run guard) fails the build if anyone addsfetch,XMLHttpRequest,WebSocket,EventSourceorsendBeacon. - 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 third-party ships in the extension.
- 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. Chrome does not let an extension set a bookmark's original creation date. Your exported files keep the real ones.
- 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
From the Chrome Web Store: here
From source:
npm ci && npm run build
Then load .output/chrome-mv3/ at chrome://extensions with Developer mode on.
Development
npm run dev
npm run verify is the gate everything else answers to — lint, type-check,
knip, the grep gate and the test suite, in that order. It must be green before
every commit.
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.
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.
Support development
Entirely optional — BookmarkMagic is free software either way.
GitHub Sponsors · Ko-fi · Buy Me a Coffee · Patreon · PayPal
Licence
GPL-3.0-or-later. Also see legal/EULA.md,
legal/DISCLAIMER.md and
legal/THIRD_PARTY_NOTICES.md.
Not affiliated with or endorsed by Google, Chrome, or any browser vendor. Browser names are trademarks of their respective owners.



