Konode
Add to Chrome
No server. No telemetry. Open source.
Bookmarks, tabs, history and your extension list, in step across every Chromium based browser. Stored in your own Google Drive, GitHub or WebDAV, with no Konode account and no server in between.
What syncs
Your whole tree lands on every device with the folders and the nesting intact. Add one on the laptop and it is on the desktop, so the organizing you already did stays done. A folder you would rather keep to one device, such as one another extension fills, can stay out of the sync.
Close the laptop mid-thought and pick the same tabs back up on another machine, tab groups included. Restoring opens only the tabs you do not already have. Your session stops belonging to one device.
That page you found last week is still there on the machine you are sitting at now. One de-duplicated list instead of one per device, so searching your history finds things.
Set up a new machine and see at a glance which of your extensions are missing from it. Konode keeps the list in step, and never installs or removes a thing by itself.
When two devices disagree, you choose how it's resolved: newest wins, always prefer this device, always prefer the other, or resolve it yourself from the popup.
Your storage
Three backends underneath: Google Drive, a GitHub repository, or any compliant WebDAV server. Everything below is one of those three, so if your provider speaks WebDAV, it already works.
Signs in with your own Google account and asks only for the narrow drive.file scope, so Konode can touch the files it created and nothing else in your Drive.
Point it at a single private repository with a fine-grained token. Every sync lands as a commit, so you get a version history you can read, diff, and roll back by hand.
Connects over WebDAV, so your sync files sit on the server you already run. Use an app password rather than your account login, especially with two-factor on.
Turn on WebDAV access in your pCloud account and paste the endpoint into Konode. It writes into one folder you pick and leaves the rest of your drive alone.
Koofr exposes a WebDAV endpoint, so it works the same way. Generate an app password for it and your main Koofr login never goes into the extension.
Fastmail's file storage speaks WebDAV too. Same three fields as any other server: endpoint URL, username, and an app password scoped to files.
The way in from mainland China, where Google Drive cannot be reached. Sign in with your Nutstore email and a third-party app password, and there is nothing else to set up.
The generic route, and the one the five above travel on. Any compliant server works, Synology and kDrive included. No provider-specific code and nothing to lock you in.
If your provider exposes WebDAV, it already works, so try it first. If not, open an issue and name it. That is how S3-compatible storage got on the roadmap.
End-to-end encryption
Encryption is optional and stays off until you set a passphrase. Switch it on and every file Konode writes is sealed on this machine first, so the provider holding it is holding something it cannot read.
Inside your browser
The same one on every device you sync, typed in on each. Konode keeps no copy of it and has nowhere to keep one.
On this machine, from that passphrase. It never crosses the network in either direction, so there is no moment at which it could be intercepted.
Bookmarks, tabs, history and your extension list become ciphertext before a single byte is uploaded.
What your storage provider receives
Encryption off
"title": "Mortgage rates 2026", "url": "https://…"
Encryption on
"payload": "9f3c7a1e5d2b8c4f…"
Konode never gets the key, and there is no Konode server to send it to.
That cuts both ways, and it is meant to. Nobody can read these files back without the passphrase, and nobody includes you. Turning encryption on also only changes what gets written from then on, so delete anything already synced in readable form if you want none of it left.
Privacy & security
Three parties can touch your synced data. Here is exactly how much of it each one gets, with encryption off and with it on.
On any device you have signed in on, with the passphrase you chose.
Google, GitHub, or whoever runs the WebDAV server you pointed Konode at.
The extension you install, and us, the people who wrote and publish it.
Two stops, and with a passphrase set, ciphertext for the whole crossing between them. Every other sync tool keeps a server in the middle of this picture. There is nothing to put there.
Step 1, on your device
Konode reads the streams you switched on and, if you set a passphrase, encrypts them here. The key is derived on this machine and never leaves it.
Step 2, your account
The file lands in your own Drive, repository or WebDAV folder. With a passphrase set it arrives as ciphertext that nobody can read back without it.
Konode installs able to read one thing. The browser only prompts for the rest when you switch that stream on, so anything you leave off stays unreadable. Try it.
Known limits
A threat model that only lists wins is marketing. These are the three places where Konode cannot help you, stated before you install rather than after something goes wrong.
Browser extensions cannot reach the operating system keychain, so your backend credentials sit in ordinary local extension storage. Anyone using your unlocked profile can read them.
Encryption keys are derived on your device and never leave it. Lose the passphrase and the uploaded data cannot be decrypted, by you or by us. There is nothing to reset.
Encryption hides what is inside a file, not that the file exists. Your provider can still see file names, sizes and when they last changed, whether encryption is on or off.
The file format
{
"device": "laptop",
"type": "bookmarks",
"updated": "2026-07-27T09:41:00Z",
"checksum": "sha256:a3f9…c2b7",
"e2ee": true,
"payload": "<AES-256-GCM ciphertext>"
}Alongside itlaptop-tabs.jsondesktop-bookmarks.jsondesktop-history.json
This is an illustrative shape. The repository has the exact schema. Every sync pulls each peer's file, merges non-destructively, then pushes back. Bookmarks use tombstones so deletions travel between devices without resurrecting old entries.
Alternatives
Pick by what you need. Your browser's own sync is the least work if you use one browser everywhere, and Firefox and Brave encrypt it end to end by default. Floccus is the one to look at if you want your bookmarks in a phone app, or synced to Nextcloud Bookmarks, Linkwarden or Karakeep. Konode is for mixing browser families, Chromium and Firefox, and syncing open tabs, history and the extension list along with your bookmarks, to storage you already have.
| Feature | Konode | Floccus | Built-in sync |
|---|---|---|---|
| What syncs | Bookmarks, open tabs with their groups, history, extension list | Bookmarks, or open tabs (one per profile) | Bookmarks, tabs, history, passwords, settings and more |
| Where it is stored | Google Drive, GitHub, WebDAV | Nextcloud Bookmarks, WebDAV, Git, Google Drive, Dropbox, Linkwarden, Karakeep | The browser maker's servers |
| Mixes Chromium and Firefox | Yes | Yes | No, each syncs only with itself |
| On phones | Firefox for Android: open tabs and the extension list | Android and iOS apps, with your bookmarks inside the app | Everything, in the browser's own app |
| End-to-end encryption | Optional, on every backend | Optional, on WebDAV, Google Drive and Dropbox | Firefox and Brave always. Chrome only with a sync passphrase |
| Account | None beyond your storage | None beyond your storage | A Mozilla or Google account. Brave uses a sync code |
| Around since | 2026 | Years, with a much larger user base | As long as the browser |
| Open source | Yes, MPL-2.0 | Yes, MPL-2.0 | Clients open. Firefox's server too, Chrome's not |
Floccus syncs open tabs as an alternative to bookmarks inside one profile, so doing both takes two profiles, and its phone apps keep your bookmarks inside the app rather than in the phone's browser. Chrome's sync passphrase covers everything except payment methods and addresses. xBrowserSync, which this table used to list, has had no release since 2020. Checked in November 2026 from each project's own documentation and store pages.
Questions
No. There is no account to create and no Konode server to sign in to, because there isn't one. You connect storage you already have, and that is the setup.
Chrome, Edge, Brave, Helium and ungoogled-chromium through the Chrome Web Store, and Firefox and Firefox-based browsers through Firefox Add-ons. On Firefox for Android it syncs open tabs and the extension list, because that browser gives extensions no bookmarks or history. A Microsoft Edge Add-ons listing is in review. The roadmap has the detail.
Three backends: Google Drive, a GitHub repository, or any compliant WebDAV server. Nextcloud, ownCloud, pCloud, Koofr, Fastmail, Nutstore, Synology and kDrive all qualify. The setup guide walks through each.
On your device only, in the browser's local extension storage. They authenticate to the backend you chose and are never transmitted to us. There is no server to transmit them to.
Then the uploaded data cannot be decrypted, by you or by anyone else. No Konode server holds your key, so there is nothing to reset and no recovery path.
Two places, both yours. Uninstalling clears what the extension put on your device, credentials included. Deleting Konode's folder on your own backend clears the synced files. There is no third place.
Get involved
It is an independent project under an MPL-2.0 licence. There is no company behind it and nothing to sell you, so the ways to help are the open source ones.
Found a bug, or missing a backend you use?
File an issueWould rather write the fix yourself?
Open a pull requestSpeak a language Konode does not yet?
Help translateNot taking the privacy claims on trust?
Read the sourceNothing to fix, but want it to keep going?
Buy me a coffeeGet started
Install it, point it at a backend you already pay for or already run, and add your second device. Nothing to sign up for along the way.
Free and open source under MPL-2.0. Read the code.