Engineering service
Brave Browser Extension Development
We build and verify extensions that keep working under Brave's defaults: Shields blocking, wallet provider injection and fingerprint randomization, tested from real Brave profiles.
- 15+ years of experience
- 300+ projects delivered
- Clients worldwide
- NDA available
Overview
What this is, and when it is the right call
Brave runs extensions from the Chrome Web Store, so most Brave extensions are Chrome extensions, and there is no separate Brave store. If yours is a plain Chrome extension, the Chrome extension page is the place to start.
The Brave-specific work is compatibility. Brave has built-in privacy features that change what pages and extensions can do, and we test and adjust for them so the extension behaves the same for Brave users as for everyone else.
Who this is for
- Teams whose Chrome extension misbehaves in Brave and who need to find out why.
- Wallet and web3 products where Brave's built-in wallet competes with an extension for page access.
- Extensions that depend on scripts, requests or page features that Brave blocks by default.
- Companies that want Brave listed as a tested browser before they promise support to users.
How it works
Architecture at a glance
How a Brave extension is put together
Popup, side panel, options
The interface users see. Talks to the background through messages.
Service worker (background)
Handles events, alarms and network rules. The browser stops it when idle, so state must live in storage.
Content script
Runs inside pages you choose. Can read and change the page, in an isolated JavaScript world.
Browser extension APIs
tabs, storage, scripting, alarms, declarative network rules, identity
Web page
Content you do not control. Treat everything from it as untrusted input.
What we offer
What we engineer: Brave Browser Extension Development
Shields compatibility testing
Every feature run in a clean Brave profile with default Shields settings, with a written list of what breaks and why.
Shields-safe fallbacks
Changes to how the extension loads or falls back when Shields removes a script, tracker or request it depends on.
Wallet provider detection
Logic that lets the user pick between Brave's built-in wallet and another provider instead of assuming one owns window.ethereum.
Fingerprinting protection fixes
Adjustments for features that read canvas or audio output, since Brave randomizes some of those results by default.
Chrome Web Store packaging
The extension built and published as a standard Chrome Web Store package, which is how Brave users install it.
New extension builds tested in Brave
If the extension does not exist yet, we build it as a Manifest V3 Chrome extension and verify it against Brave's defaults as part of the work.
Deliverables
What you get
- 01
Brave compatibility test
A run of every extension feature in Brave with default Shields settings, with a written list of what breaks.
- 02
Shields workarounds
Changes so the extension keeps working when Brave blocks scripts, trackers or requests that it or its target pages depend on.
- 03
Wallet provider handling
Detection and selection logic for the case where Brave's wallet and another provider both try to inject window.ethereum.
- 04
Fingerprinting protection fixes
Adjustments for features that read canvas or audio output, since Brave randomizes some of those results.
- 05
Chrome Web Store build
The extension packaged as a normal Chrome extension, since that is how Brave users install it.
- 06
Support notes for users
A short page for your help center covering Brave settings that affect the extension.
Compare
Brave-specific checks
These are the areas where a working Chrome extension most often runs into trouble in Brave.
| Area | What can go wrong | What we do |
|---|---|---|
| Shields content blocking | Shields can remove scripts or requests that your extension or the pages it targets rely on. | We test with default Shields settings, find what is blocked and change how the extension loads or falls back. |
| Built-in wallet | Brave injects a wallet provider into pages, which can compete with other wallet providers for window.ethereum. | We detect which provider is present, let the user choose, and avoid assuming the extension's provider wins. |
| Fingerprinting protection | Some canvas and audio results are randomized, so features that read them can give inconsistent output. | We find features that depend on those reads and use a different signal, or handle the variation. |
| Distribution | Assuming a separate Brave store exists. | We publish to the Chrome Web Store, which is how Brave users install extensions. |
Why it matters
What this gives you
Works with Shields left on
Fixes are built around Brave's default protections instead of asking your users to turn them off.
No assumptions about the wallet provider
Wallet and web3 features handle the case where Brave's own wallet is also present and competing for the same page APIs.
Fingerprinting-aware feature design
Canvas- or audio-based checks are identified early and replaced or adjusted so they do not silently fail in Brave.
Verified from a real Brave profile
Testing runs against Brave with default settings, not just Chrome, so compatibility claims are based on what we actually saw happen.
Our approach
How a Brave compatibility project runs
Baseline in Brave
We install your extension in a clean Brave profile with default settings and record how each feature behaves.
You get: A pass and fail list
Trace the causes
For each failure we identify whether Shields, the wallet, fingerprinting protection or something else is responsible.
You get: Root causes for each issue
Adjust the extension
We change the extension so it works with Brave's defaults instead of asking users to turn protections off.
You get: Code fixes and fallbacks
Retest and document
We rerun the tests, including with stricter Shields settings, and write down the results and known limits.
You get: A test report and support notes
When this is not the right fit
A few cases where this approach may not be the best choice for you.
- Your extension already works in Brave. A plain Chrome extension needs no Brave-specific work, so start there.
- You want features that need Brave privacy protections off for every user. We would respect the defaults instead.
- You want a Brave browser fork with built-in changes. That is browser modification, not extension development.
Tech stack
Technologies we use
The engines, APIs and tools behind our brave browser extension development work.
Chromium Extensions APIChrome Web StoreBrave Shieldswindow.ethereum / EIP-1193Canvas & AudioContext APIsService Workers
JavaScript
TypeScriptFAQ
Questions engineers ask before starting
No. Brave installs extensions from the Chrome Web Store, so a Brave extension is a Chrome extension that has been tested and adjusted for Brave.
Our services
Related services
Explore more services that work alongside this one.
Talk to a Browser Engineer
Make Your Extension Work in Brave
Tell us what the extension does. We will test it against Shields, the wallet and fingerprinting defaults and fix what breaks.
