zhom

donutbrowser: Manage Isolated Browser Profiles

Donut Browser is a desktop Chromium-based browser for running separate profiles with distinct fingerprints, cookies, and network settings. It suits privacy-conscious users and teams managing multiple accounts, with optional sync and automation integrations.

View on GitHub Compare
Stars
4k
Forks
421
Stars, last 30 days
+254

Our take

Health score

67/100

How it is scored
Activity
90
Community
37
Issues
67
Pull requests
75

+254 stars in the last 30 days

  • Releases more often than 93% of the projects we track
  • Merges more pull requests than 77% of the projects we track

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

4,331

Forks

450

Change since Nov 17, 2026: +15 stars·0 forks

Overview

Donut Browser is a desktop application for creating and managing isolated browser profiles. Each profile keeps its own browser data and can use a separate fingerprint, proxy, or VPN, helping reduce cross-account links caused by shared browser characteristics.

The project uses Wayfern, a Chromium fork, for fingerprint handling. Profile data is stored locally by default, with optional encrypted sync. It is aimed at people who need profile separation, rather than users looking only for ordinary private browsing.

Key Features

  • Create multiple profiles with separate cookies, extensions, and stored data.
  • Configure fingerprints, HTTP/SOCKS proxies, and WireGuard VPN settings per profile.
  • Import profiles from Chromium-based browsers, including Chrome, Edge, and Brave.
  • Organize profiles into groups and manage cookies and extensions.
  • Use a local REST API and CDP connections with browser automation tools; automation and remote MCP are listed as paid-plan features.
  • Optionally sync profiles across devices, or run a self-hosted sync server.
  • Keep profiles on the device by default, with optional password-protected and ephemeral profiles.

Use Cases

  • Account managers who need separate browser sessions and network settings for different clients or projects.
  • Privacy-conscious users who want separate browsing profiles without sending profile data to a required account service.
  • Automation developers who want to connect Playwright, Puppeteer, or Selenium to managed browser profiles.
  • Teams experimenting with MCP-driven browser workflows, where a paid plan and remote MCP access fit their needs.

Getting Started

Install with Homebrew on macOS:

brew install --cask donut

Installers are also listed on the GitHub releases page. See the README for platform-specific installation instructions, setup, and documentation links.

Considerations

  • This is a specialized anti-detect browser, not a general-purpose replacement focused solely on everyday browsing.
  • The README describes automation and remote MCP as paid-plan features; check the project documentation for plan details.
  • Optional sync involves a server. Users can use Donut Sync or follow the self-hosting guide.
  • The project is licensed under AGPL-3.0, which may affect redistribution or modifications in some deployment contexts.
  • The README makes claims about fingerprint resistance, but effectiveness can vary as websites and detection systems change.

Found this useful?

Share it with someone who would like donutbrowser.

Comparisons