Documentation
Donut Browser documentation.
On this page
Donut Browser is a desktop app for macOS, Windows and Linux that runs many isolated browser profiles. Each profile has its own fingerprint, cookies and proxy or VPN, so sites see each one as a different device. The app is open source, needs no account and sends no telemetry. Profiles stay on your disk unless you turn on sync.
Get started
- Install and first profile: download, first start and your first profile.
- Import profiles: bring Chrome, Edge, Brave and other Chromium profiles over, with their cookies and passwords.
Use the app
- Profiles and fingerprints: the operating system a profile shows, fingerprint editing, templates, statuses, 2FA codes and the trash.
- Proxies and VPNs: proxy types, checks, IP rotation, WireGuard, DNS, blocklists and leak protection.
- Groups, tags and bookmarks: keep many profiles in order.
- Extensions: add Chrome extensions and load them by group.
- Cookies: import, paste, export and copy cookies and storage state.
- Locked and ephemeral profiles: password encryption, memory-only profiles and clear-on-close.
- Synchronizer: repeat one profile’s actions in many.
- Settings and shortcuts: every setting, keyboard shortcut and the command palette.
Cloud and teams
- Sync and backup: cloud backup, end-to-end encryption and restore points.
- Self-hosted sync server: run the sync server yourself with Docker and any S3 storage.
- Team: roles, profile locks, access by group and the activity log.
- Cookie Bot: warm profiles on a schedule while your computer is off.
- Remote browsers: run a profile on a Windows, macOS or Linux machine in Donut’s fleet.
AI agents
Donut contains no AI model. You connect the agent you use.
- AI agents: set up Claude Code, Cursor, Codex or OpenClaw, or keep the agent on your machine over CDP with a local model. One profile and one proxy per account.
- Agent page and recipes: answer questions, take over profiles, record recipes and schedule them.
- MCP tools: what an agent can do, and which tools stay in the app.
- Remote MCP: the endpoint, credentials, toolsets and what the relay sees.
Local API
- API quickstart: turn on the API on
127.0.0.1:10108and make the first call. - Authentication: the bearer token and error codes.
- API reference: every endpoint, with examples in four languages.
- Wayfern and Playwright: attach Playwright to a profile and humanize mouse, typing and scroll.
- OpenAPI spec: the machine-readable spec and client generation.
Guides
- Step-by-step guides: one task per page, from an authenticated SOCKS5 proxy or a WireGuard profile to bulk profiles, parallel Playwright runs and Selenium.
What each plan includes
| Feature | Free | Solo | Pro | Team |
|---|---|---|---|---|
| Local profiles, proxies, VPNs, cookies, extensions | Unlimited | Unlimited | Unlimited | Unlimited |
| Cloud profiles | None | 20 | 50 | 100 |
| Fingerprint editing, other operating systems, Synchronizer | No | No | Yes | Yes |
| Local API: manage profiles, proxies, groups | Yes | Yes | Yes | Yes |
| Local API: launch and drive browsers | No | No | Yes | Yes |
| Remote MCP | No | Without browser tools | Yes | Yes |
| Cookie Bot and scheduled recipes | No | Yes | Yes | Yes |
| Recipes on demand, remote sessions on demand | No | No | Yes | Yes |
| Remote hours a month | None | 40, for Cookie Bot and scheduled recipes | 200 | 200 per paid seat, shared |
| Team roles and profile locks | No | No | No | Yes |
Prices are on the pricing page. Commercial use needs a paid plan after a 2-week trial.
For AI agents
Every docs page is also Markdown: add .md to its path, for example /docs/quickstart.md. All pages in one file are at /llms-full.txt, the site index is /llms.txt, and the REST API spec is /openapi.json.
Checked against the app on .
