Planning and cost
How much does a custom Chromium browser cost?
By Imran Ahmed, Browser Projects Manager
Technically reviewed by Ahmed Raza, Head of Browser Development
Published Last updated 6 min read
A browser with your name, icons and defaults and a browser with new privacy behavior in its network stack are both called a custom browser, but the second can take many times the effort of the first. This guide explains what moves the cost, so you can see where your project sits before you ask for an estimate.
The four things that drive cost
1. How deep the changes go
Branding, default settings, a new-tab page and a set of bundled features are configuration and interface work. New behavior in the network stack, the privacy model, process isolation or rendering means working in Blink, V8 or the browser process itself. That is engine-level engineering, and it costs more to write, to test and to carry forward on every upgrade. For example, a custom new-tab page is interface work; changing what canvas or WebGL report to web pages, or adding your own URL protocol, is engine work.
2. How many platforms you ship
Windows, macOS and Linux each need their own build, installer, code signing and test pass, so each platform you add brings its own track of work. Starting on one desktop platform and adding the others in later milestones spreads that cost out.
Mobile is a separate decision. Android is its own Chromium build. On iOS, every browser must use Apple’s WebKit engine, except under Apple’s alternative browser engine entitlements in the EU and Japan, so an iOS version is usually a separate project.
3. Release infrastructure
A browser is not finished when it compiles. Users need signed installers, an auto-update channel, crash reporting and a way to push a security fix quickly. Building that pipeline is part of the project, and skipping it is how teams end up with a browser they cannot safely update.
4. How long you will maintain it
Chrome now ships a new major version every two weeks (since Chrome 153 on 8 September 2026), with security fixes in between, and its Extended Stable channel moves every eight weeks. Your changes have to be rebased onto the versions you follow and tested again for as long as the browser has users. Budget this as a yearly cost, separate from the build. The fewer upstream files your changes touch, the lower it stays.
Costs outside engineering
Some costs are not engineering hours, and some of them take weeks to arrange, so start them early:
- Build machines and CI. Chromium’s build instructions ask for at least 100 GB of free disk space and recommend 16 GB of RAM or more, and a full build can take hours.
- Code-signing certificates for Windows, and an Apple Developer Program membership to sign and notarize macOS builds.
- Hosting for the update server and for crash reporting.
- A Widevine license agreement with Google, if users need DRM-protected streaming.
- Your own sync and sign-in services, if you need them. Chrome Sync and other private Google APIs have been closed to third-party Chromium browsers since March 2021.
What different scopes look like
| Scope | Typical work | Relative build effort | Ongoing maintenance |
|---|---|---|---|
| Branded build | Name, icons, defaults, new-tab page, bundled settings | Low | Low: few files differ from upstream |
| Feature-rich browser | Built-in features, custom UI, policies, search and partner integrations | Medium | Medium: every UI patch must be rebased |
| Engine-level browser | Network stack, privacy and fingerprinting, process model, custom protocols | High | High: patches sit in internal APIs that change often |
Examples from our case studies: XFII Browser is a branded build with a custom new-tab page and extensions turned off. Kahf Browser adds built-in features, including AI that blurs inappropriate images. The Anti-Fingerprint Chromium Browser is engine-level work on canvas, WebGL, audio and font signals. If a branded build is all you need, see our white-label browser development service. Our guide on how to rebrand Chromium lists everything a rebrand touches.
Does it have to be a custom browser?
The cheapest browser is often the one you do not build. If your idea works inside the extension APIs, a browser extension costs less to build and much less to maintain (see what a Chrome extension costs). If you need to show web content inside your own application, an embedded browser (CEF or WebView2) or a desktop framework such as Electron or Tauri may fit. Our guide to Chromium compares the four options. Choosing the smaller option, when it is enough, is the biggest saving available.
How to plan the budget
- Separate the build budget from the yearly maintenance budget, and approve both.
- Decide the platforms and the base (Chromium, Brave or Firefox) before asking for estimates.
- Ask which changes live in the engine and which are configuration, since that split drives effort.
- Require a written upgrade runbook so maintenance does not depend on one engineer.
- Start with a short scoping call and a written estimate before you commit to a build.
The ongoing side is covered in the version porting playbook and on our version porting and maintenance page. For typical time ranges by project type, see how long it takes to build a custom browser.
Final takeaway
Decide scope and platforms first, get the build and the yearly maintenance estimated separately, and choose the smallest option that does the job.
Frequently asked questions
How much does a custom Chromium browser cost?
We do not publish a price list, because the cost depends on how deep the changes go, how many platforms you ship on, the release infrastructure you need and how long you will maintain the browser. After a short scoping call we send a written estimate that prices the build and the yearly maintenance separately.
What do you need from us to write an estimate?
What the browser must do, which platforms it ships on, the base you prefer (Chromium, Brave or Firefox) if you already know, any launch date, and who will maintain it after launch. The first step is a 30-minute scoping call; the written estimate follows.
Is building on Brave or Firefox cheaper than Chromium?
Sometimes. Brave already includes features such as Shields and Wallet, so there is less to build, but you then track two upstreams (Brave and Chromium). Firefox uses a different engine and toolchain, so the cost profile is different rather than lower across the board. The right base depends on which features you need already built and which you must write.
Do I own the source code?
The work lives in a repository your team controls, and ownership terms are written into the contract before work starts. Chromium itself stays under its BSD-style license and the licenses of its third-party components.
Get a written estimate
Tell us what your browser needs to do. After a short scoping call we send a written estimate for the build and for keeping it current. The work itself is described on our Chromium browser development page.