Vanadium
What Vanadium is
Vanadium is a free, open-source Android browser and WebView built by GrapheneOS, where it serves as the default browser and WebView implementation. It uses the Chromium engine and adds protections including hardware memory tagging for its main allocator, type-based control-flow integrity, a strong stack protector, and automatic zero-initialized variables. Strict site isolation and sandboxed iframes are enabled. In the browser, JavaScript just-in-time compilation is disabled by default but can be enabled for individual sites; WebView has separate controls, with JIT enabled by default for user-installed apps. Content filtering uses EasyList, EasyPrivacy, and related lists, including regional lists based on enabled browser languages. Third-party cookies, payment support, background sync, sensor access, protected media, and hyperlink auditing are disabled by default. Android autofill and credential manager support enable passkey use. WebGPU is disabled, and a WebRTC IP handling policy toggle is available. The project says nearly all remote services are disabled or removed; by default, Vanadium connects to GrapheneOS servers for component updates and optional DNS-over-HTTPS connectivity checks. It is currently built for GrapheneOS, with broader availability planned once it has more features.
Who it suits
Vanadium suits Android users who use GrapheneOS and want its Chromium-based default browser and WebView with added security protections and content filtering. It may also suit users who value open-source software and native Android autofill and passkey support.
What it does well
- Free and open source.
- Includes strict site isolation and sandboxed iframes.
- Content filtering uses EasyList and EasyPrivacy.
- Supports Android autofill and passkeys.
- Third-party cookies and several other features are disabled by default.
What to know first
- Currently built for GrapheneOS.
- No extension support is planned.
- Cross-device sync beyond OS backup is not planned.
- Most browser data is currently excluded from OS backups.
Limits
Vanadium is currently built for GrapheneOS. Most browser data is currently excluded from OS backups, and the project does not plan to support extensions or sync beyond the OS backup service.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Vanadium | Included with GrapheneOS; Android browser and WebView | Free |
As grapheneos.org lists them, read 10 Oct 2026. The maker's own page has the final word.
Getting started
- Visit the Vanadium feature page on the GrapheneOS website.
- Use Vanadium as the browser and WebView included with GrapheneOS.
- Adjust JavaScript JIT settings for individual sites if needed.
- Use community platforms for support.
Verdict
Choose Vanadium if you use GrapheneOS and want a free Chromium-based browser with additional security hardening and content filtering. Look elsewhere if you need extensions, cross-device sync, or a browser for desktop or iOS.
Questions
Is Vanadium free?
Yes. The Vanadium plan is listed as free and is included with GrapheneOS.
Is Vanadium open source?
Yes. GrapheneOS describes the project as open source and non-profit.
Which platforms does Vanadium support?
Vanadium is currently built for GrapheneOS, an Android mobile operating system.
Does Vanadium support browser extensions or cross-device sync?
Extension support and sync beyond the OS backup service are not planned.
What browser engine does Vanadium use?
Vanadium uses the Chromium browser engine.
How can users get support?
The project directs users to its community platforms and asks them not to contact developers directly for support requests.
Facts from Vanadium's own pages
- Autofill and passkeys
- It has native Android autofill and credential manager support for passkeys, avoiding the need for sandboxed Google Play for those functions. · grapheneos.org, 10 Oct 2026
- Availability
- Vanadium is currently built for GrapheneOS, and the project says it plans to make it available outside GrapheneOS once it has more features. · grapheneos.org, 9 Oct 2026
- Browser engine
- chromium · grapheneos.org, 23 Sept 2026
- Browser security
- Vanadium adds hardware memory tagging for its main allocator, type-based CFI, a strong stack protector, and automatic zero-initialized variables. · grapheneos.org, 9 Oct 2026
- Built-in ad blocking
- Yes · grapheneos.org, 23 Sept 2026
- Compatibility trade-off
- Content filtering and other compatibility-impacting features are mostly available in the browser rather than the WebView library. · grapheneos.org, 10 Oct 2026
- Content filtering
- The browser includes a content-filtering engine using EasyList, EasyPrivacy, and EasyList’s Adblock Warning Removal List as primary filters, with supplementary regional lists based on enabled browser languages. · grapheneos.org, 10 Oct 2026
- Cross-device sync
- No · grapheneos.org, 23 Sept 2026
- Extensions
- Extension support is not planned because GrapheneOS says it conflicts with site isolation and anti-fingerprinting. · grapheneos.org, 10 Oct 2026
- Extension support
- none · grapheneos.org, 23 Sept 2026
- Free plan
- Yes · grapheneos.org, 23 Sept 2026
- JavaScript
- JavaScript JIT is disabled by default in the browser, with a per-site toggle; WebView JIT behavior for user-installed apps has separate global and per-app controls. · grapheneos.org, 10 Oct 2026
- Open source
- Yes · grapheneos.org, 23 Sept 2026
- Passkeys and autofill
- Vanadium includes native Android autofill and credential manager support for passkeys, avoiding the need for sandboxed Google Play for those features. · grapheneos.org, 9 Oct 2026
- Platform availability
- The maker describes Vanadium as the browser and WebView included with GrapheneOS, a mobile operating system; the cited Vanadium feature page does not list desktop or iOS versions. · grapheneos.org, 10 Oct 2026
- Supported platforms
- mobile · grapheneos.org, 23 Sept 2026
- Privacy defaults
- Third-party cookies, payment support, website background sync, sensors access, protected media, and hyperlink auditing are disabled by default. · grapheneos.org, 10 Oct 2026
- Project
- GrapheneOS describes itself as a non-profit, open source project and says it was founded in 2014. · grapheneos.org, 9 Oct 2026
- Project model
- GrapheneOS describes itself as a collaborative open-source, non-profit project supported by donations and company support. · grapheneos.org, 10 Oct 2026
- Remote services
- Nearly all remote services are disabled or removed; by default, Vanadium only connects to GrapheneOS servers, with component updates and optional DNS-over-HTTPS connectivity checks listed as default services. · grapheneos.org, 10 Oct 2026
- Security hardening
- It adds protections including hardware memory tagging for the main allocator, type-based CFI, a strong stack protector, and automatic zero-initialized variables. · grapheneos.org, 10 Oct 2026
- Site isolation
- It enables strict site isolation and sandboxed iframes. · grapheneos.org, 10 Oct 2026
- Support
- The project directs users to its community platforms for support and asks them not to contact developers directly for support requests. · grapheneos.org, 9 Oct 2026
- Sync and backups
- Sync beyond the OS backup service is not planned; most browser data is currently excluded from OS backups. · grapheneos.org, 9 Oct 2026
Where Vanadium stands on Freedom251
- Web browsers#36 of 154
- Privacy browsers#15 of 32