Donut Browser
Donut Browser manages any number of isolated browser profiles. Each profile keeps its own fingerprint, cookies, extensions and data, and runs on Wayfern, a Chromium-based engine that Donut downloads on first use.
- Per-profile HTTP, HTTPS, SOCKS4 and SOCKS5 proxies, and WireGuard configs
- Per-profile DNS blocklists for ads and trackers
- Profile import from Chrome, Edge, Brave and other Chromium browsers
- Cookie and extension management
- A local REST API and a Model Context Protocol server for automation
- Optional end-to-end encrypted sync to Donut cloud or a self-hosted server
Compatibility: Uses the C library of the system (may need glibc 2.35 or later)
GitHub Download Donut_Browser Website Donut_Browser Bugtracker
Usage
Donut_Browser is available as an AppImage which means "one app = one file", which you can download and run on your Linux system while you don't need a package manager and nothing gets changed in your system. Awesome!
AppImages are single-file applications that run on most Linux distributions. Download an application, make it executable, and run! No need to install. No system libraries or system preferences are altered. Most AppImages run on recent versions of Arch Linux, CentOS, Debian, Fedora, openSUSE, Red Hat, Ubuntu, and other common desktop distributions.
This AppImage uses the C library of the system and may need glibc 2.35 or later. It does not run on distributions that use a different C library (such as musl on Alpine Linux) or an older glibc.
Running Donut_Browser on Linux without installation
Unlike other applications, AppImages do not need to be installed before they can be used. However, they need to be marked as executable before they can be run. This is a Linux security feature.Beware! AppImages are usually not verified by others. Follow these instructions only if you trust the developer of the software. Use at your own risk!
Download the Donut_Browser AppImage and make it executable using your file manager or by entering the following commands in a terminal:
chmod +x ./*.AppImageThen double-click the AppImage in the file manager to open it.
Sandboxing Donut_Browser
If you want to restrict what Donut_Browser can do on your system, you can run the AppImage in a sandbox like Firejail. This is entirely optional and currently needs to be configured by the user.
Updating Donut_Browser
If you would like to update to a new version, simply download the new Donut_Browser AppImage.
The Donut_Browser AppImage also can be updated using AppImageUpdate. Using this tool, Donut_Browser can be updated by downloading only the portions of the AppImage that have actually changed since the last version.
Integrating AppImages into the system
If you would like to have the executable bit set automatically, and would like to see Donut_Browser and other AppImages integrated into the system (menus, icons, file type associations, etc.), then you may want to check the optional appimaged daemon.
Note for application authors
Thanks for distributing Donut_Browser in the AppImage format for all common Linux distributions. Great! Here are some ideas on how to make it even better.
Pro Tips for further enhancing the Donut_Browser AppImage
Please consider making the Donut_Browser AppImage self-contained, so that it does not depend on the C library of the system and runs on more distributions: ship the C library including its loader (ld-linux-*.so.*) and use it to launch the application, or link statically.
Thanks for shipping AppStream metainfo inside your AppImage. Please open a pull request on https://github.com/AppImage/appimage.github.io/blob/master/data/Donut_Browser if you have changed it and would like to see this page updated accordingly.
If you would like to see a donation link for the application here, please include one in the AppStream data.