Brave

Layered over Chromium as a set of changes, APIs and scripts, Brave inherits the web platform work that Chromium does while replacing the parts its authors did not want to ship.

The work is split across two repositories. This one holds issues, releases and the wiki, while brave-core carries the source and the build tools that fetch and sync Chromium through depot_tools, mount brave-core at src/brave and maintain patches for third party Chromium code.

A few details of that arrangement matter if you are evaluating it.

• Ad blocking engine: adblock-rust implements the blocker and is linked into the browser through a foreign function interface.
• Pinned Chromium: the build sets an explicit Chromium branch rather than tracking head.
• Platform coverage: development environments are documented for Android, Linux, iOS, macOS and Windows.
• Build tooling: two package manager scripts drive init and then component, release, static or debug builds.
• Translations: interface strings are translated by the community on Transifex.

Building from source downloads the Chromium history, tens of gigabytes of it, and takes a long time, so most people should take a stable release from the website instead. Technical documentation and guides sit in brave-core, while a separate community forum handles support questions and feature requests.