Does Brave Have Extensions? Yes, 3 Things to Know (2026)
Brave installs Chrome Web Store extensions directly. The button reads 'Add to Brave.' What breaks silently: MV2 holdovers, optional permissions, and Shields.
You hover the install button in Brave and it reads “Add to Brave.” Yes, Brave runs MV3 Chrome Web Store extensions directly. Three failure modes hit with no error: Manifest V2 holdovers with no store listing, ungranted optional permissions, and Shields blocking a site dependency.
Key takeaways
- Brave runs Chrome Web Store extensions natively. The button reads “Add to Brave,” MV3 extensions behave identically to Chrome, and no separate Brave store for MV3 exists.
- Three failure modes are silent. MV2 extensions vanished from the store in August 2026, optional permissions are never granted at install, and Shields can block a dependency on one site without a warning.
- Check Shields state before you uninstall. A feature that works everywhere except one site can be a per-site Shields block, not a broken extension.
Yes, Brave Runs Chrome Web Store Extensions
The install path is the Chrome Web Store you already use. Search for an extension, open its listing, and the install button reads “Add to Brave.” Manifest V3 extensions behave as they do in Chrome.
Brave does maintain four MV2 extensions on its own backend, reachable at brave://settings/extensions/v2. The support is best-effort. Chrome removed all MV2 listings from the Chrome Web Store on August 31, 2026 (two months before this article’s October 2026 publication). Any MV2 extension you ran in Chrome is no longer installable from the store. If a MV3 equivalent exists, install that. If it does not, check whether it is one of the four MV2 extensions Brave hosts at brave://settings/extensions/v2.
Install steps:
- Open the Chrome Web Store in Brave by typing the store URL in the address bar.
- Search for the extension you want.
- Click the install button. It reads “Add to Brave.”
- If the extension declares non-optional permission keys, a consent warning appears before the install completes.
Manage: Open brave://extensions. This page lists installed extensions, toggles, and permission grants. It is a management surface, not an install surface.
Three Ways an Extension Fails Silently
None of these produce an error dialog. You notice the missing feature long after and cannot tell which mode caused it.
| Failure mode | What you notice | Why it happens | Fix |
|---|---|---|---|
| MV2 extension removed from store | The extension has no store listing to install from | Chrome removed all MV2 CWS listings; Brave’s four MV2 extensions run on a separate backend | Install the MV3 equivalent if one exists, or check brave://settings/extensions/v2 |
| Optional permission not granted | A feature (cross-origin data, access to a specific domain) silently does nothing | optional_permissions and optional_host_permissions are granted at runtime, never at install | Open brave://extensions, find the extension, grant the specific permission |
| Shields blocks a dependency | Extension works on most sites but one feature fails on a specific page | Shields blocks a script the extension depends on; the per-site toggle is on | Click the Shields icon in the address bar, turn it off for that site, or add a filter exception at brave://settings/shields/filters |
The MV2 row bites hardest during a migration. You install your Chrome set, the MV3 extensions land fine, and the MV2 holdovers have no store listing left to install from. The optional-permission row is subtler: the extension installs, loads, shows its icon, and one feature quietly does nothing because you never granted the runtime permission. The Shields row is the easiest to fix once you know to look. The extension is fine. The site’s blocking state is the problem.
Five Permission Keys: What You Control at Install
Chrome’s extension manifest declares five permission keys. Two of them, optional_permissions and optional_host_permissions, are granted by you at runtime and never at install. Changes to the non-optional keys surface a consent warning before install or at runtime, so you see what is being requested.
| Key | Type | When granted |
|---|---|---|
permissions | Known permission strings (tabs, storage, contextMenus, etc.) | At install, with consent warning |
content_scripts.matches | URL match patterns for content-script injection | At install, with consent warning |
host_permissions | URL match patterns for cross-origin requests | At install, with consent warning |
optional_permissions | Additional permission strings beyond permissions | At runtime, by you |
optional_host_permissions | Additional URL patterns beyond host_permissions | At runtime, by you |
Two access flags sit outside the install flow entirely. file:// scheme access and incognito access are enabled on the extension’s details page, not at install. You right-click the extension icon, choose “Manage Extension,” and scroll to enable them. In Brave, the extension management page is brave://extensions.
Migrating Your Toolbar: Two Paths
Get the permission model right before you batch-install your Chrome set. The cost of doing it after is the three silent failures above.
If you are moving your full Chrome extension set: install from the Chrome Web Store (the button reads “Add to Brave”), and when a feature misbehaves on one site, check that site’s Shields state before you uninstall. The cause can be the per-site Shields toggle rather than the extension.
If you only came to Brave to add an ad blocker: stop. Shields covers ad and tracker blocking at the browser level with per-site toggles and no extension process. Spend the extension slot on a real gap instead. Brave Extensions: 6 BEST Picks for What’s Missing covers what that gap looks like.
Frequently Asked Questions
Can you use Chrome extensions in Brave?
Where do I manage extensions in Brave?
Do Manifest V2 extensions work in Brave?
Don't miss the next release
Be first to know when we ship something new.
Related Articles
Brave Extensions: 6 BEST Picks for What's Missing (2026)
Brave extensions: skip the ad blocker, Shields already covers it. 6 picks fill the real gaps: timed suspension, workspaces, session recovery. Aug 2026.
Brave Shields vs uBlock Origin 2026: 3 Reasons to Add It
Does Brave Shields make uBlock Origin redundant? Mostly — it runs the same filter lists natively. The 3 tools uBlock still adds, as of July 2026.
Brave vs Chrome Performance: Which Is Faster? (2026)
Brave vs Chrome performance: both share one engine, but defaults set the floor. 34 auto-protected apps, 186K+ rules, a 5-min timer neither ships. (2026)
AI Tab Organizer vs Tab Manager: 6 TESTED (2026)
6 AI tab organizers tested on CWS vs real tab managers. AI groups by content. You work by project. That gap costs more than you think. Real comparison inside.