Brave Core: Brave Browser Engine Source
/brave-core
Brave Core is the repository that holds Brave's actual Chromium patches, build scripts, and ad-blocking integration — not a browser you install, but the source tree you build one from. Reach for it if you want to compile Brave yourself or inspect exactly what it changes in Chromium. Skip it if you just want to run Brave day to day — grab the compiled build from brave.com/download instead.
What is Brave Core?
Brave Core is the GitHub repository (brave/brave-core) that contains the changes, APIs, and scripts Brave uses to customize Chromium into the Brave browser. It's mounted at src/brave inside a Chromium checkout, maintains patches against third-party Chromium code, and links in the adblock-rust ad-blocking engine via adblock_rust_ffi. Issues, releases, and the wiki live in a separate repository, brave-browser, rather than here.
Key Components and Customizations
- ✓Maintains patches against third-party Chromium source rather than hosting a full duplicate fork, applied and re-applied through the pnpm run sync and apply_patches commands.
- ✓Fetches and pins the exact Chromium branch and other dependencies declared in package.json and src/brave/DEPS, using depot_tools to pull Chromium itself.
- ✓Wires in Brave's adblock-rust engine (from the separate brave/adblock-rust repo) via the adblock_rust_ffi component under components/.
- ✓Exposes a pnpm-based command surface — init, build, start, sync — on top of Chromium's own build system, instead of requiring raw gn/ninja invocations.
- ✓Builds in four variants: Component (the default), Release, Static (slower to build, faster to start), and Debug.
- ✓Covers desktop platforms (Linux, macOS, Windows) and mobile, with dedicated --target_os flags for Android and iOS builds.
- ✓Documents a security review process inherited from Chromium — security rules and IPC review guidelines — alongside a Brave-specific Rust usage doc.
Who Should Use Brave Core?
- •Compiling the Brave desktop browser from source on Linux, macOS, or Windows instead of installing the prebuilt release.
- •Auditing or contributing to the specific patches Brave applies on top of stock Chromium.
- •Building Brave for Android or iOS using the target_os init and build flags documented in the repo.
- •Working on Brave's ad-blocking engine integration, since adblock-rust is wired in here through adblock_rust_ffi.
- •Enabling and testing Google Safe Browsing locally by supplying your own GOOGLE_API_KEY, as the README walks through.
Setting Up Your Development Environment
Start with the platform prerequisites: the README links out to separate brave-browser wiki pages for Android, Linux, iOS, macOS, and Windows development environments — read the one for your platform before cloning. Once those are in place, clone brave-core into a src/brave path (`git clone [email protected]:brave/brave-core.git path-to-your-project-folder/src/brave`), `cd` into it, and run `pnpm run init`. That step fetches Chromium itself alongside brave-core, and the README warns it downloads gigabytes of Chromium history, so expect it to take a while on a normal connection. Android builds add `--target_os=android --target_arch=arm` (or your target CPU) to that init command, and iOS builds add `--target_os=ios`. Extra configuration is covered in a separate Build-configuration wiki page rather than in this README.
Building and Running the Browser
The default build is a Component build, started with `pnpm run build`; add `Release` for a release build, `Static` for a statically linked build that's slower to compile but starts faster, or `Debug` for a debug Component build. The README is upfront that a full build can take a few hours depending on your processor and memory, and that Release builds in particular are slow and RAM-hungry, especially on Linux with the Gold LLVM plugin. Once built, launch it with `pnpm start [Release|Component|Static|Debug]`. To pick up upstream changes later, `pnpm run sync` updates Chromium and brave-core to a given ref, re-applies patches, and updates dependencies — pass `--force` to hard-reset both to their latest commits, or `--init` to reset fully to the versions pinned in package.json.
Strengths
- ✓Patches, not a duplicate fork: Chromium is fetched fresh via depot_tools and brave-core's changes are reapplied on top, which keeps the diff visible instead of buried in a full copy of Chromium's tree.
- ✓One command surface (init/build/start/sync) covers five platforms — Android, iOS, Linux, macOS, Windows — instead of separate build docs per OS.
- ✓adblock-rust is integrated as its own component (adblock_rust_ffi) rather than hand-patched into Chromium's network stack.
- ✓Four build variants — Component, Release, Static, Debug — let you pick faster iteration or faster startup depending on what you're doing.
- ✓MPL-2.0 is a permissive license with copyleft only on modified files, so you can see exactly what Brave changed without proprietary licensing friction.
Challenges and Considerations
- △Brave Core isn't a standalone, buildable browser on its own — building Brave means also fetching Chromium and the separate adblock-rust engine through this repo's init/sync scripts, not compiling brave-core in isolation.
- △The initial `pnpm run init` downloads Chromium's full source history, which the README describes as gigabytes of data, so first setup needs real disk space and time.
- △A full build can take a few hours, per the README, and Release builds are called out as especially slow and memory-heavy on Linux.
- △Issue tracking, release notes, and the wiki live in the separate brave-browser repository, so this repo alone won't show you open bugs or version history.
- △Exact prerequisite install steps per platform aren't in this README — it defers to brave-browser wiki pages, so you'll be reading two repos' documentation, not one.
Alternative Browser Projects
Common Questions
Brave Core is licensed under the Mozilla Public License 2.0 (MPL-2.0), as listed in the GitHub repository metadata.
GitHub lists C++ as Brave Core's primary language; its build tooling runs on pnpm/Node scripts, and the linked adblock-rust component is written in Rust.
Brave Core's README points contributors to its CONTRIBUTING.md guidelines and to the brave-browser wiki for setting up a development environment first.
Brave Core's build scripts do cover mobile: the README documents an Android init/build flow with --target_os=android and a separate iOS flow with --target_os=ios plus an Xcode project.
Brave Core is a layer of patches, APIs, and scripts mounted at src/brave inside a Chromium checkout — it customizes and builds on top of Chromium rather than replacing or forking it into a separate codebase.
The README says a full build can take a few hours depending on processor and memory, on top of the initial Chromium source download, which it separately flags as gigabytes of data.
The problem it solves
Brave changes Chromium's behavior in a lot of places — ad blocking, privacy defaults, UI — and every time upstream Chromium moves, those changes need to be reconciled instead of rewritten from scratch. Brave Core exists to make that reconciliation repeatable: it stores Brave's changes as patches against a pinned Chromium branch, syncs and re-applies them with one command, and wires in a separately maintained ad-blocking engine (adblock-rust) rather than bolting ad-blocking logic directly into forked Chromium files. That's narrower than "how do I build a browser" — it's specifically how Brave keeps its Chromium fork maintainable across five platforms and a moving upstream target.
Who should try it — and who should skip
Try Brave Core if you're a developer who wants to build Brave from source, review or contribute to the specific patches it carries on top of Chromium, or work on its adblock-rust integration. Skip it if you just want to use Brave day to day — get the compiled build from brave.com/download — or if you want a small, self-contained codebase you can build without also pulling down Chromium's full source tree.
Want a second opinion on brave-core?
Ask an AI that can read this page — one click and you get its take on brave-core.