How Bookmark Manager Zero Syncs Bookmarks to Mobile with GitLab

Updated

Bookmark Manager Zero gets bookmarks onto your phone by syncing them through a private GitLab repository in your own account. You connect the app with a GitLab personal access token (PAT), your bookmarks are written to that private repo, and the web app or Android app then reads from it on any device. This is an optional step: on desktop, the browser extensions work directly with your native Firefox or Chrome bookmarks and need no sync at all. GitLab sync exists because mobile browsers and web apps can't access native browser bookmarks due to platform restrictions.

Why GitLab instead of a built-in account

The project chose GitLab because it is free, secure, and takes minutes to set up — you only generate a personal access token. Unlike Google or other OAuth-based sync options, you never enter your actual login credentials on devices you don't fully trust. That matters if you're syncing on a public computer or a tablet you share.

GitHub was considered first, but per the project's own notes its API made the integration impractical.

What you need before starting

  • A GitLab account.
  • A GitLab personal access token with access to create and write to a private repository.
  • Bookmark Manager Zero installed in Firefox or Chrome on your desktop (the source of your bookmarks), or bookmarks already present in the web app.
  • The web app open, or the Android app installed (it is a dedicated wrapper around the web app).

Step-by-step setup

  1. Generate a GitLab personal access token. In your GitLab account settings, create a token with the scopes needed to create a private repository and read/write its contents. Copy the token — you won't see it again.
  2. Connect Bookmark Manager Zero to GitLab. In the app's sync settings, paste the PAT. The app uses it to create or access a private repository in your own GitLab account.
  3. Run the first sync from your desktop. Your bookmarks are written to that private repository. Because the browser extension treats your native bookmarks as the source of truth, this pushes what's already in your browser.
  4. Open the web app or Android app on your phone or tablet. Sign in to the same sync setup and point it at the same repository. Your bookmarks download to the device.
  5. Verify. Add or rename a bookmark on one device, sync, and confirm it appears on the other. Check that the repository in GitLab is private and contains your bookmark data.

How sync handles changes (and why nothing disappears silently)

Sync is two-way, but it is deliberately cautious about destructive operations. New bookmarks travel on their own in both directions. Anything that would remove, rename, or move a bookmark stops and asks first, showing exactly what would change and on which device.

The logic behind that: a rename you make yourself syncs silently, because you clearly meant it. A rename arriving from another device waits for confirmation, because it would overwrite something you may have chosen deliberately. Nothing destructive happens without you seeing it.

This is the main thing to expect in practice — the first sync after editing on two devices may prompt you to confirm changes rather than applying them automatically.

Common snags

  • Token scope too narrow. If the repository can't be created or written to, regenerate the PAT with broader repository permissions.
  • Confirmation prompts on sync. These are expected, not errors. Review the listed changes and approve them.
  • Expecting mobile to read native bookmarks. It can't — mobile browsers block that access. GitLab sync is the bridge, so set it up before relying on the phone app.
  • Trusting a shared device. The PAT is the credential on that device, not your GitLab password. Revoke the token in GitLab if you used a public computer.

Is this the right setup for you?

Use GitLab sync if you want bookmarks on phones, tablets, or public computers and are comfortable creating a token and a private repo. Skip it if you only use Bookmark Manager Zero on one desktop browser — the extension already reads and writes your native bookmarks with no lock-in or migration.