Twine

Keep your bookmarks in sync across browsers and profiles through a private GitHub repository.

Twine keeps your bookmarks in sync across browsers and profiles through a private GitHub repository that you own. Twine has no server and no account of its own. Your bookmarks are stored in your browsers and in one JSON file per profile in your repository, and the developer never receives them. Every change is a commit, so earlier versions stay in the repository's history. You need a GitHub account, a private repository, and a fine-grained access token limited to that repository. The options page walks you through it. Browsers that pick the same profile keep the same bookmarks, so work and home can stay separate. Twine syncs the bookmarks bar and Other bookmarks, including titles, URLs, folders, and order, a few seconds after a change, at browser startup, and every 10 minutes. When two devices change at once, Twine merges the changes. If both changed the same bookmark, this browser's version wins, the other stays in the repository's history, and the badge tells you. A sync that would remove a large share of your bookmarks pauses and asks which version to keep, and Twine won't apply an empty or invalid file over your bookmarks. The toolbar badge shows what state Twine is in: SET when it needs you, AUTH when GitHub rejects the token, ERR when a sync fails, and ! when a sync discarded or overwrote something. Twine can't see your tabs, your browsing history, or the contents of any page. Known limit: Twine syncs one bookmarks bar and one Other bookmarks folder. If Chrome keeps your Google Account bookmarks separately from bookmarks on this device, Twine syncs only one of those sets. Mobile and managed bookmarks are not synced.