---
title: "Self Hosted Browser Profile Sync: Setup and Security Guide"
description: "How does self hosted browser profile sync work? You run a sync server with S3 storage, a token and TLS. Learn setup, security and conflict-avoidance steps."
url: "https://donutbrowser.com/ja/self-hosted-browser-profile-sync/"
---

1. [ホーム](https://donutbrowser.com/ja/)

2. [ブログ](https://donutbrowser.com/ja/blog)

3. Self Hosted Browser Profile Sync: Setup and Security Guide

# Self Hosted Browser Profile Sync: Setup and Security Guide

November 8, 2026

self-hosting browser profile sync s3 storage

**Self hosted browser profile sync means running your own sync server with S3-compatible storage, protected by a token and TLS, so profile data never sits on a third-party cloud. Treat the session cookies in a profile like credentials. [Donut Sync](https://donutbrowser.com/docs/self-hosting/), the server behind Donut Browser’s sync, runs as one container and is free to self-host, but you run it.**

If you run client, brand or regional accounts, each profile holds logged-in sessions, and you probably want the same ones on a laptop and a desktop. Where that session data lives is a client-trust decision as much as a convenience.

After reading, you can pick an architecture, set up a server, lock it down and avoid conflicts when two devices open one profile. I make Donut Browser, so I weigh trade-offs openly, and the steps also work with other tools.

> **Key Takeaways**

> - Profile sync moves logged-in sessions, extensions and proxies, so a leaked bucket can expose working logins.

> - Store the end-to-end encryption password in a shared password manager before you turn encryption on.

> - Open a profile on one device at a time.

> - A synced profile brings its proxy and fingerprint, so match timezone and IP on the new machine.

## What is browser profile sync, and how is it different from bookmark sync?

Browser profile sync copies the whole state of a browser identity between devices: cookies, local storage, extensions, proxy settings and fingerprint settings. Bookmark and tab sync moves only saved pages and open windows.

![Illustration for What is browser profile sync, and how is it different from bookmark sync?](https://api.birchseek.com/m/ZNKL53CA-lW966vWn3f-H7aYdoqGKQd0.webp)

Bookmark tools never touch session data by design. [TabbySync](https://tabbysync.com/), a self-hosted example, describes its job as “Sync your bookmarks and your open tabs”.

Profile sync is wider. [Donut’s self-hosting docs](https://donutbrowser.com/docs/self-hosting/) say Donut Sync handles “profiles with their browser data, proxies, VPNs, groups and extensions.”

Chromium keeps each profile in a folder inside its user data directory. Not everything in that folder should travel.

- **Sync it:** extensions and their settings, preferences, and fingerprint settings. The fingerprint has to stay identical, or the identity changes on the second device.

- **Sync with care:** cookies and local storage, because they hold logged-in sessions and work like passwords. Proxy settings also belong here: the IP must still match the profile’s timezone and language on the new machine.

- **Don’t sync:** caches, which rebuild themselves and only add bulk, and lock files, which mark a profile as open on one machine. Copy a lock file and the other device may think the profile is still running.

Copying one profile folder from a laptop to a desktop moves more than a bookmark list. It moves that client’s logged-in sessions, extensions and proxy, so the desktop opens straight into the same accounts.

That makes a profile a full identity, which is the idea behind an [anti-detect browser](https://donutbrowser.com/what-is-an-anti-detect-browser/). Importing an existing Chromium profile is a separate, one-time operation: the [profile import docs](https://donutbrowser.com/docs/profile-import/) cover bringing in folders or ZIP archives once. Sync keeps the same profile current on every device afterward.

## Which self hosted browser profile sync setup fits you?

A server with S3 storage fits daily use on several machines, a simple endpoint fits low-risk data, and manual export fits profiles you rarely move.

| Criterion | Server + S3 storage | Simple endpoint | Manual export/import |
| --- | --- | --- | --- |
| Setup effort | Container plus a bucket | One destination and a token | None |
| Who runs it | You | You, or a free no-server option | You, by hand |
| Privacy | Data stays in storage you control | Depends on where the endpoint lives | Files stay where you put them |
| Stale copies between devices | Sync keeps them current | Sync keeps them current | Stale until you repeat the move |
| Ongoing work | Updates, TLS, token care | Low | Every single move |

Server plus S3 storage is the architecture Donut Sync uses. The [Donut Sync self-hosting guide](https://donutbrowser.com/docs/self-hosting/) says the server is one container that talks to any S3-compatible bucket, and that for production you can point it at “Cloudflare R2, Backblaze B2, AWS S3 or any other S3 API.”

The same guide draws the cost line: “Sync through Donut’s cloud is a paid feature. A server you run yourself is free, and the data stays in storage you control.”

Before choosing among R2, B2 and AWS S3, check each provider’s official docs for three things: the S3 API endpoint format for your region, presigned URL support, and whether you can scope an access key to one bucket. The server won’t connect unless those line up.

The simple-endpoint pattern exists in other tools. [TabbySync](https://tabbysync.com/) says everything “talks to one sync destination, one token and one sync name”, pointing at “a server you control, or a free no-server alternative if you don’t have one.” It syncs bookmarks and tabs, not cookies, so it shows the pattern rather than a profile solution.

Manual export and import needs no infrastructure. When you copy a profile to a second machine, its proxy and fingerprint settings travel with it. Check that the operating system, timezone and IP still tell one story.

**Best for, server + S3:** daily use on two or more machines, or any setup where client session data must stay in storage you own.

**Best for, simple endpoint:** people who want automatic sync and no server to patch, and whose data is low-risk.

**Best for, manual:** a profile you move a few times a year, where stale copies don’t matter.

A solo operator who switches machines rarely can start manual and move to a server when the copying gets old. A small agency should run the server with its own bucket from the start, because several people share the same session data and client trust depends on where it lives.

## How do you set up self hosted browser profile sync?

Self hosted browser profile sync takes five steps: start the server, attach storage, set a token, put TLS in front and connect a client, then verify. Donut Sync is the worked example here. Steps 2 to 5 apply to any tool built on a server plus a bucket.

The [Donut self-hosting docs](https://donutbrowser.com/docs/self-hosting/) describe the server as “one container that talks to any S3-compatible bucket.”

1. **Start the server.** Copy the docker-compose example from the docs and run it. The quick start runs a small S3 server next to the container, so everything stays on one machine. Check that `docker compose ps` shows the container running and that the logs hold no errors.

2. **Attach S3-compatible storage.** For production, the docs say to point the server at Cloudflare R2, Backblaze B2, AWS S3 or any other S3 API. Set `S3_ENDPOINT` to the address the server uses to reach the bucket; if you also set `S3_PUBLIC_ENDPOINT`, use an address your laptop can reach, because a Docker-internal hostname only resolves inside the host. Create a dedicated bucket and an access key limited to it, and keep the bucket private.

3. **Set a long random `SYNC_TOKEN`.** Generate it with `openssl rand -hex 32` and store it in a password manager. Profiles hold session cookies, so treat the token like a password and keep it in an environment file that stays out of git.

4. **Put TLS in front, then connect the client.** Run a reverse proxy such as Caddy or nginx with a certificate so clients connect over `https`. Enter the server URL and the token in the client’s sync settings. Paste the token with no trailing whitespace.

5. **Verify, then sync a throwaway profile.** Request `/health` and `/readyz` through the public `https` address, not `localhost`. Then create a profile, log in to a test account, sync it, and open it on a second device. Success means you’re still logged in and new objects appear in the bucket.

If a check fails, find your symptom in the troubleshooting section of the self-hosting docs before you change settings.

Run your first self hosted browser profile sync test entirely on the quick start. Set `SYNC_TOKEN`, leave `S3_ENDPOINT` pointing at the bundled storage, and confirm that `/health` and `/readyz` both respond. Only then add the client and sync a profile you don’t care about.

When that works, swap `S3_ENDPOINT` for a Backblaze B2 or Cloudflare R2 address. Repeat steps 4 and 5 before moving real client profiles.

## How do you secure self hosted browser profile sync?

You secure self hosted browser profile sync by treating the session cookies in each profile as passwords, because anyone who can read them can replay a logged-in session. If your agency holds a client’s Instagram or ad account sessions, a readable storage bucket is a leaked login.

The sync token is a bearer token. [RFC 6750](https://www.rfc-editor.org/rfc/rfc6750) defines it so that “any party in possession of the token” can use it, whoever that party is. Handle yours accordingly:

- **Use TLS only.** Put a reverse proxy with a certificate in front of the sync server so no plain HTTP request ever carries the token.

- **Keep it out of URLs and logs.** RFC 6750 says “Bearer tokens SHOULD NOT be passed in page URLs”. Send it in a header, and strip it from any proxy access logs.

The bucket is the second target. Keep it private with no public read access, and give the server a key that works on that one bucket only. The server’s own docs cover this under [self-hosting Donut Sync](https://donutbrowser.com/docs/self-hosting/). You run the server, the certificate and the keys yourself.

End-to-end encryption (E2EE) protects the contents from the storage host and from whoever operates the server. Data is encrypted on your device with a password before it uploads, so the bucket holds unreadable files.

That password is known only to you. Decide now where your team stores it, such as a shared password manager.

E2EE isn’t the right fit for every profile, so decide profile by profile. Any profile you leave unencrypted depends entirely on a private bucket and a secret token.

For each client, ask who could read the bucket today and whether you’d tell the client that.

## What happens when two devices open the same profile?

When two devices open the same profile, each one writes its own cookies, and whichever uploads last can erase the newer data from the other.

Say a laptop opens a client profile first. A desktop then opens the same profile and logs in again, which creates a fresh session cookie. When the laptop closes and uploads its copy, the server holds the laptop’s older cookies, and the desktop’s login is gone.

A **session lock** prevents this: one device holds the profile at a time, and others wait or open it read-only.

### Overwrite or merge?

Merging works when data is a list of separate items. Bookmark tools such as [TabbySync](https://tabbysync.com/), which syncs “your bookmarks and your open tabs”, can compare both edits to the last common version (a three-way merge) and keep both changes.

A profile is a folder of databases and settings that the browser edits while it runs. Two copies can’t be combined line by line without risking a corrupt cookie store, so whole-profile sync usually picks a winner.

### How does a server reject a stale write?

HTTP has a built-in check. The server labels each stored version with an ETag, and the client sends that label back in an `If-Match` header when it uploads.

[IETF RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html) says the 412 (Precondition Failed) status code “indicates that one or more conditions given in the request header fields evaluated to false when tested on the server.”

With that check, the laptop’s upload carries the ETag it saw when it opened the profile. The desktop’s upload already changed the stored version, so the server answers 412 and keeps the newer copy.

### Habits that avoid conflicts

- Close the profile on one device before opening it on another.

- Wait for the upload to finish before you switch.

- Sync a test profile first, with no real client logins, and check that the cookies arrive.

## Does moving a profile keep its identity consistent?

A moved profile keeps its identity only when the fingerprint and proxy travel with it and still tell a believable story on the new machine. [Donut Sync](https://donutbrowser.com/docs/self-hosting/) carries proxies along with browser data, so the proxy moves with the cookies.

A profile is a package. [Persona Studio’s README](https://github.com/TechQaiser/persona-studio) describes each one as having “a coherent fingerprint, its own proxy, and a persistent session.” If any part of that package changes on the way, the site sees a different device or a different place.

After a move, check three things:

- **OS and fingerprint.** A profile that reports Windows should still report Windows on a Mac or Linux machine. The fingerprint belongs to the profile, not to the hardware. Our [guide to browser fingerprinting](https://donutbrowser.com/browser-fingerprinting/) lists the signals to compare, such as canvas, WebGL, audio and fonts.

- **Timezone and language against the proxy IP.** A New York IP with an `Asia/Ho_Chi_Minh` timezone gets flagged. Match the named zone, not only the UTC offset: a Berlin proxy with a Prague timezone is still a mismatch.

- **One proxy per profile.** Two profiles on one proxy share an IP, which links them. Our [proxy guide for anti-detect browsers](https://donutbrowser.com/proxies-for-anti-detect-browsers/) shows how to assign them one to one.

To verify, open the profile on the new machine and run it through BrowserLeaks, Pixelscan or CreepJS. All three are free.

Compare the IP location, timezone, language and platform with what the same profile showed before the move. If they differ, fix the profile settings before you log in to any account.

## Where does Donut Browser fit in a self hosted sync setup?

Donut Browser fits a self hosted sync setup as the desktop client for Donut Sync, a server you run yourself and can test by following the [self-hosting guide](https://donutbrowser.com/docs/self-hosting/). Each part comes with a trade-off.

1. **A paid account can still use your server.** The same docs list “Sign in with a paid Donut account” for a self-hosted server, so a plan and your own bucket can coexist.

2. **Cloud sync is a paid feature.** On [the pricing page](https://donutbrowser.com/pricing/), the Team plan lists cloud sync for 100 profiles. Solo and Pro list cloud profile backups (20 and 50) instead.

3. **It’s desktop only.** [Donut Browser](https://donutbrowser.com) runs on macOS, Windows and Linux. There’s no mobile app.

4. **It sells no proxies and guarantees no bans.** Bring your own proxy. Sync moves your settings between machines, and account safety still depends on behavior and platform rules.

5. **The code is open.** The source is on [GitHub under AGPL-3.0](https://github.com/zhom/donutbrowser), so you can read what talks to your server.

If you use another browser, steps 2 to 5 of the setup still apply.

## Frequently asked questions

### How does self hosted browser profile sync work?

**You run a sync server and S3-compatible storage, and each browser client syncs to them instead of a vendor’s cloud.** [Donut Sync](https://donutbrowser.com/docs/self-hosting/) is one container that talks to any S3-compatible bucket. Profiles upload to your storage, and your other devices pull them down.

### Is self hosted profile sync free?

**Self-hosting Donut Sync is free, and you run the server yourself.** You cover your own hosting and storage costs. Sync through Donut’s cloud is a paid feature, and the [Team plan](https://donutbrowser.com/pricing/) includes cloud sync for 100 profiles.

### Should every synced profile use end-to-end encryption?

**Use it for profiles that stay on your own devices.** It keeps the bucket contents unreadable to anyone without the password, so store that password where your team can find it.

### Who can read my profiles if I turn on end-to-end encryption?

**Only someone who knows your encryption password.** Anyone else with bucket access sees unreadable files.

### Can I sync a profile to my phone?

**No, Donut Browser is desktop only.** Self hosted browser profile sync works between your macOS, Windows and Linux machines.

## Next steps for self hosted browser profile sync

**Today:** Pick your architecture and list the profiles that carry client or high-value sessions.

**This week:** Start the server, set the token, put TLS in front, then check `/health` and `/readyz` with a throwaway profile.

**This month:** Decide on end-to-end encryption, write down where the password lives, and test a two-device handoff.

**Further reading**

- [Self-hosting Donut Sync](https://donutbrowser.com/docs/self-hosting/): the Docker and S3 steps in full.

- [Proxies for anti-detect browsers](https://donutbrowser.com/proxies-for-anti-detect-browsers/): keep each synced profile’s IP story consistent.

- [Browser fingerprinting explained](https://donutbrowser.com/browser-fingerprinting/): what travels with a profile.

- [Import profiles](https://donutbrowser.com/docs/profile-import/): bring existing Chromium profiles in first.

## Sources

[Self-hosting Donut Sync · Docs — Donut Browser](https://donutbrowser.com/docs/self-hosting/) · [TabbySync — self-hosted bookmark and tab sync for Chrome…](https://tabbysync.com/) · [RFC 6750: The OAuth 2.0 Authorization Framework: Bearer…](https://www.rfc-editor.org/rfc/rfc6750) · [RFC 9110: HTTP Semantics](https://www.rfc-editor.org/rfc/rfc9110.html) · [TechQaiser/persona-studio: Persona Studio - GitHub](https://github.com/TechQaiser/persona-studio) · [Pricing: Free Forever, Solo, Pro and Team — Donut Browser](https://donutbrowser.com/pricing/) · [Private anti-detect browser — Donut Browser](https://donutbrowser.com) · [zhom/donutbrowser: Donut Browser](https://github.com/zhom/donutbrowser)

## Google で当サイトをもっと見る

ワンクリックで Donut Browser を Google アカウントの優先ソースに設定すると、トップニュース、AI モード、AI による概要で当サイトの記事が表示されやすくなります。

Google で優先ソースに設定

## On this page

- What is browser profile sync, and how is it different from bookmark sync?

- Which self hosted browser profile sync setup fits you?

- How do you set up self hosted browser profile sync?

- How do you secure self hosted browser profile sync?

- What happens when two devices open the same profile?

- Overwrite or merge?

- How does a server reject a stale write?

- Habits that avoid conflicts

- Does moving a profile keep its identity consistent?

- Where does Donut Browser fit in a self hosted sync setup?

- Frequently asked questions

- How does self hosted browser profile sync work?

- Is self hosted profile sync free?

- Should every synced profile use end-to-end encryption?

- Who can read my profiles if I turn on end-to-end encryption?

- Can I sync a profile to my phone?

- Next steps for self hosted browser profile sync

- Sources
