Bookmark Atlas

Open the app

Downloads

Your bookmarks are encrypted on your device. The server stores only ciphertext and never learns their contents — that holds for every client below.

Every client ships with its source. The extensions are built from one tree — the browsers differ only in the manifest and the background wrapper — so a single archive rebuilds both. Checksums are listed in SHA256SUMS, and the packaging is reproducible: building the same sources twice yields the same file.

Chrome, Brave, Edge, Vivaldi, Opera

Bookmark Atlas Connector 1.1.1 · requires Chrome 110 or newer

Ready

Syncs your whole bookmark tree in both directions — bar, other bookmarks and any nested folders. Supports sign-in with a second factor (TOTP code or recovery code). Chrome has no bookmarks-menu root of its own, so that container appears as an ordinary folder inside Other Bookmarks.

Download extension (.zip) Source code Checksums
How to install
  1. Unpack the archive into a permanent folder — deleting it uninstalls the extension.
  2. Open chrome://extensions (in Brave: brave://extensions).
  3. Turn on Developer mode in the top right.
  4. Click Load unpacked and select the unpacked folder.
  5. Click the Bookmark Atlas icon and sign in.

Why developer mode? Chromium installs extensions from outside the Web Store only this way. A signed release needs a Google developer account and review; until then installation is manual.

Firefox

Bookmark Atlas Connector 1.1.1 · requires Firefox 115 or newer

Ready

Syncs your whole bookmark tree in both directions. Firefox has all four native roots — toolbar, menu, other and mobile — so each maps directly onto its container in the vault, and a tree synced from Chrome arrives complete.

Download extension (.xpi) Source code Checksums
How to install
  1. Open about:debugging#/runtime/this-firefox.
  2. Click Load Temporary Add-on… and select the downloaded .xpi.
  3. Click the Bookmark Atlas icon and sign in.

A temporary add-on is removed when Firefox closes. For a permanent install, release Firefox requires the add-on to be signed by Mozilla. Until that review is done, a lasting install needs Developer Edition, Nightly or ESR with xpinstall.signatures.required set to false in about:config.

Safari on macOS

Native application 1.1.1 · not an extension

Source code

Safari gives extensions no bookmarks API. Unlike Chrome and Firefox, Apple never implemented browser.bookmarks. Syncing Safari requires a native app using a private system API — which is why there is no extension here and why one cannot be written.

A sync layer you compile into the Bookmark Sync app. Building requires a Mac with clang and libsodium.

Download sources (.tar.gz) Checksums
How to build
  1. Install the dependency: brew install libsodium.
  2. Unpack the archive and enter BookmarkAtlasSync/Tests.
  3. Run ./run-tests.sh — it checks that the crypto matches every other client. This step also works on Linux and needs no application sources.
  4. Go up one level and run ./build.sh /path/to/BraveToSafariSyncApp.
  5. Grant the app Full Disk Access in System Settings — without it Safari's bookmarks cannot be read.

Verification status. The crypto core is tested against the same vectors as the web app and the Chromium extension (75 checks). The Objective-C layer was written off-Mac and has not been compiled — expect build fixes on the first attempt. Details in README.md inside the archive.

The app uses the private Safari.framework API, which Apple can change in any system update. The code checks that the API is available at startup and refuses to run rather than risk corrupting bookmarks.

Verifying your download

Compare the checksum of the downloaded file against SHA256SUMS: 

sha256sum bookmarkatlas-chromium.zip

A checksum protects against corruption in transit. It does not protect against substitution by whoever runs this server — the files and the checksums come from the same place.