Brave is a Chromium-based web browser for Windows, macOS, Linux, Android, and iOS, released under the MPL-2.0 licence, and this repository is the project's public issue tracker, release channel, and developer wiki rather than the home of its source code.
What it is
Brave is a cross-platform web browser whose topic list names brave, browser, chromium, linux, macos, and windows. It is distributed under the MPL-2.0 licence, has 23,646 stars and 3,214 forks on GitHub, and is published through the project site at brave.com. The browser itself is built from source held in a separate repository, brave/brave-core, and the README states plainly that this repository is not needed for building the browser.
The concrete problem this repository solves is coordination, not compilation. It concentrates bug reports, feature requests, release binaries, and developer documentation in one place so that the source repository at brave/brave-core can stay focused on code. Releases are published on the GitHub Releases page and tracked against the Brave Release Schedule wiki, while documentation for developers, administrators, and power users lives in the wiki, kept separate from the user-facing Brave help center at support.brave.app. The README does not name a specific product that Brave replaces.
Key capabilities
- Distributes builds for Windows, macOS, Linux, Android, and iOS, covering desktop and mobile from a single release channel.
- Runs on the Chromium engine, as recorded in the repository topic list.
- Publishes release artifacts through GitHub Releases, with timing documented in the Brave Release Schedule wiki.
- Hosts a wiki with documentation aimed at developers, administrators, and power users, distinct from the end-user help center.
- Collects bug reports and feature requests through the issue tracker, which currently shows 10,752 open issues.
- Supports community Q&A at community.brave.app, including support-and-troubleshooting and brave-feature-requests categories.
- Accepts translations through Transifex at explore.transifex.com/brave/brave_en/, and points contributors to CONTRIBUTING.md and security reporters to SECURITY.md.
Who uses it and how
- Everyday users download the latest stable release from brave.com/download and receive updates through the normal browser release channel.
- Bug reporters and feature requesters file against the GitHub issue tracker, where the open backlog runs to 10,752 items.
- Developers build Brave by following the wiki and the technical guides in brave-core/docs/README.md, working from the source in brave/brave-core rather than from this repository.
- Translators contribute locale work through the Brave project on Transifex instead of through GitHub pull requests.
- Administrators, power users, and community members use the wiki and the community.brave.app forum, with a community-guest channel also available on Brave Software's Slack workspace.
Getting started
End users install the current stable build from brave.com/download, or take a specific build from the GitHub Releases page for this repository. Anyone building from source, or preparing a contribution, must move to brave/brave-core and follow the wiki instructions, since this repository holds no browser source.
How it compares
The provided facts list no paid products that Brave replaces, and no competing browser is named. On the available evidence Brave stands alone in this registry, with its only stated lineage being the Chromium engine it is built on. MPL-2.0 licensing and the public issue tracker and releases pages are the comparison points the facts actually support.
When to use it — and when not to
Pick this repository if you need to file a Brave bug, request a feature, read developer or administrator documentation on the wiki, grab a release binary, or find the translation and community entry points. Do not pick it if you intend to build, patch, or audit the browser, because the README explicitly says the source lives at brave/brave-core and the build instructions are on the wiki. The README is short and does not describe runtime dependencies such as a database, storage layer, or mail service, and the last recorded push was 16 September 2026, so anyone expecting active code changes here will be looking in the wrong place.