One build, four browsers

Cross-Browser Extension Development: One Codebase for Chrome, Edge, Firefox and Safari, and the Four Places It Splits

Your customers do not all use Chrome. Some run Edge because IT put it there, some will not give up Firefox, and the sales team lives in Safari on an iPhone. One extension can reach most of them from one codebase, if someone plans for the places the browsers part ways.

November 17, 2026 · 9 min read

browser makers' developer pages · read November 16, 2026
What each browser asks of a publisher
Four stores, four account rules
Published
Chrome Web Store registration$5, one-time
Microsoft Edge Add-onsNo registration fee
Firefox signing on AMONo fee stated
Apple Developer Program, for Safari99 USD a membership year
DataCram custom extension, built onceFrom $1,500
fees as published by each browser maker as of November 2026; Apple prices may vary by region

The short answer

Cross-browser extension development means writing one WebExtensions codebase and packaging it for each browser. Chrome and Edge take the same package, per Microsoft. Firefox needs its own extension ID and a background script entry, because it does not support extension service workers. Safari needs the extension wrapped in a macOS or iOS app. DataCram builds them from $1,500, depending on complexity.

On this page
  1. Most of the code already speaks every browser's language
  2. Where Chrome, Edge, Firefox and Safari part ways
  3. What a second, third and fourth browser add to the build
  4. GatorCrawl Keywords, held up against four browsers
  5. When one browser is plenty
  6. Price, ownership and the accounts in your name

Most of the code already speaks every browser's language

Twenty years ago a company that wanted a browser add-on paid for four of them. One for each browser, each in its own format, each installed through a download page with a progress bar and a prayer. The toolbar era left a lot of people with a lasting dislike of the whole idea, and with some reason.

That era is over. MDN, Mozilla's developer documentation, describes the WebExtensions APIs as "broadly compatible across the major browsers: Google Chrome, Apple Safari, Microsoft Edge, and Opera." An extension is HTML, CSS and JavaScript plus a manifest file. The same source can serve every browser your customers use, which is the starting premise of every custom browser extension we build.

Broadly compatible is not identical, and MDN says so on its Chrome incompatibilities page, read in November 2026: "there are significant differences between Chrome (and Chromium-based browsers), Firefox, and Safari." The same page offers good news on an old headache: "Support for the browser namespace and promises are no longer a source of incompatibility." Chrome's own API reference now shows "browser.* since Chrome 148", so code written against the shared namespace no longer needs a translation layer for Chrome.

Where Chrome, Edge, Firefox and Safari part ways

The differences cluster in four places: how the extension is packaged, what the manifest must declare, which account publishes it, and how each store describes its review. Here is each browser as its maker documents it, read in November 2026. Fees are as of November 2026 and can change.

How a Chrome build becomes a Chrome, Edge, Firefox and Safari release, per each browser maker's documentation as of November 2026
BrowserWhere it shipsWhat changes from the Chrome buildAccount feeReview, in the store's words
ChromeChrome Web StoreNothing: this is the Manifest V3 baselineA one-time registration fee, $5 per Chrome's What's new page"For most extensions, review is completed within a few days, but it can take up to a few weeks."
EdgeMicrosoft Edge Add-ons, through Partner CenterRemove the update_url field; rebrand if the name or description says Chrome"There is no registration fee""The certification process can take up to seven business days after you submit the extension."
Firefoxaddons.mozilla.org (AMO), listed or self-distributed, signed by Mozilla either wayAn extension ID in browser_specific_settings, background scripts beside the service worker, a data collection declarationNone stated on the Mozilla pages read"It can take up to 24 hours for your submission to be signed and published, or longer if your submission is selected for manual review."
SafariThe App Store, or signed with a Developer ID outside the Mac App StoreWrapped in a macOS or iOS app by Apple's packager and built in XcodeApple Developer Program, "99 USD per membership year""Apple reviews all extensions and updates to ensure they work reliably."

Sources for the table: Chrome's review process page and its What's new page (April 30, 2026 entry); Microsoft's porting guide, developer account page and publishing page; Mozilla's signing overview; Apple's Safari extensions page and program page. None of these is a promise, and we make none either. The Chrome Web Store review page covers what slows a submission down.

What a second, third and fourth browser add to the build

Firefox and Safari are where the real work sits. Firefox does not run extension service workers: MDN's background key page says "background.service_worker is not supported" and advises cross-browser Manifest V3 extensions to "specify both scripts and service_worker in the background key." Chrome reads one, Firefox the other. The background code has to be written so it behaves under both, which is a design decision made on day one, not a patch made in month three.

  1. 1

    Write one permission plan

    List every site and permission the extension needs once, so every store gets the same short, honest list and the same justification.

  2. 2

    Build the shared core

    Content scripts, the options page, storage and messaging written against the shared WebExtensions APIs, with browser checks kept in one small file.

  3. 3

    Add Firefox's entries

    An extension ID in browser_specific_settings, which MDN says is mandatory for signing Manifest V3 extensions because "AMO does not assign an ID", plus the background scripts entry and the data collection declaration.

  4. 4

    Package for Safari

    Run Apple's packager to create the Xcode project and read its report of manifest keys Safari does not support.

  5. 5

    Test in each browser

    Load unpacked in Chrome and Edge, use Load Temporary Add-on in Firefox's about:debugging page, and run the Safari build from Xcode.

  6. 6

    Submit under your accounts

    Chrome Web Store, Partner Center, AMO and App Store Connect, each in your company's name.

Layered colored-paper cutout of four blank browser windows of different shapes joined by one paper puzzle piece, with soft shadows
One codebase sits at the center, and each browser gets its own wrapper around it.

Safari is the other outlier. Apple describes a Safari web extension as something you "implement as a macOS, visionOS, or iOS app extension." The extension ships inside an app. Our Safari extension page walks through the packager, Xcode and the App Store, and the Firefox extension page covers AMO signing and Mozilla's source code rules.

GatorCrawl Keywords, held up against four browsers

DataCram built GatorCrawl Keywords, a keyword research web app, and its Chrome extension. The extension is a Manifest V3 build with a service worker, an options page, two permissions (storage and contextMenus) and a content script that runs on one address pattern, Google's results pages. It ships on the Chrome Web Store. Here is what each other browser would ask of it, based on the documentation above.

Edge

Microsoft says Chromium extensions need no rewrite. Neither the name GatorCrawl Keywords nor its store description contains the word Chrome, so the rebrand step in Microsoft's porting guide would not apply.

Firefox

Its background is declared only as a service worker, which Firefox does not support. A port adds a scripts entry beside it, an extension ID, and a data collection declaration for AMO.

Safari

Apple's packager would build the Xcode project and list any manifest keys Safari does not support. We would read that list before writing an estimate, not after.

All four

One job, one site, a short permission list. A small extension is easier to port, easier to explain on four privacy forms, and easier to review.

The last card matters more than it looks. Chrome's review page says reviews "may take longer for extensions that request broad host permissions", naming patterns like <all_urls>. An extension that asks only for what its single job needs avoids that flag on Chrome and keeps every store's privacy form short. The full part-by-part build is in how we built the GatorCrawl extension.

When one browser is plenty

Cross-browser work costs money, and some extensions do not need it. If the extension is for your own staff and IT already manages Chrome, one build covers everyone, and force-installing it by policy is covered on the internal team extensions page. If the job could be a web page, a bookmarklet or a feature in your app, the extension versus web app comparison may save you the whole project.

Build for several browsers when

  • Your customers choose their own browser and you sell to all of them
  • Your users work on Macs and iPhones, where Safari is the default
  • A competitor already ships a Firefox or Edge version and buyers ask why you do not
  • The extension is the front door to a paid web app, so every missing browser is a missing signup

Stay with one when

  • Every user is on a company-managed Chrome or Edge install
  • You are testing whether the idea earns installs at all
  • The budget is tight and Edge alone, which takes the Chrome package, covers the second group
  • The extension relies on a feature one browser lacks and no fallback makes sense

A sensible order for many products: ship Chrome, submit the same package to Edge, watch who asks for what, then add Firefox or Safari when the demand is real. The code written for Chrome on day one should not have to be thrown away when that day comes.

Price, ownership and the accounts in your name

Custom browser extensions from DataCram start at $1,500 to build, depending on complexity, with a fixed written estimate before work starts. Each additional browser is one of the things that moves the estimate, alongside the number of sites the extension touches, whether it needs a backend, and accounts and billing. Our extension pricing page lays out those drivers, and the custom Chrome extension development page describes the build from discovery to handover.

  • Store submission, privacy disclosures and the permission plan are part of the build, for every browser in scope.
  • You own the code and the listings. We recommend publishing under your own developer accounts: Chrome Web Store, Partner Center, AMO and the Apple Developer Program.
  • Connections to your own APIs and systems, a CRM, a web app, an AI model or payments, go live the same day through our API integration work.
  • Updates after launch are quoted, and the extension maintenance page explains what four browsers mean for upkeep.

DataCram is a web studio in San Antonio, Texas, building for the web since 1999, working with businesses across the US by phone, video and a shared project page. If the extension is the front end of something bigger, our web app development team builds that too. See our work, or call (210) 346-0848.

Questions owners ask about custom browser extensions

Yes, from one codebase, with packaging and a few manifest entries per browser. MDN calls the WebExtensions APIs broadly compatible across the major browsers, and Microsoft says Chromium extensions run in Edge without a rewrite. Firefox needs its own extension ID and background scripts, and Safari needs the extension wrapped in a macOS or iOS app.

Microsoft's documentation says the extension APIs and manifest keys Chrome supports are code-compatible with Edge, and you can submit a Chromium extension to the Edge Add-ons site without rewriting it. Its porting guide asks you to remove the update_url field and rebrand if Chrome appears in the name or description. Edge charges no registration fee, as of November 2026.

A common reason is the background service worker. MDN says Firefox does not support background.service_worker and uses background scripts instead, so a cross-browser manifest lists both. Firefox also requires an extension ID in browser_specific_settings to sign a Manifest V3 extension. Mozilla must sign the extension before release versions of Firefox will install it.

As of November 2026: Chrome Web Store has a one-time registration fee, which Chrome's What's new page puts at $5. Microsoft says there is no registration fee for Edge. Apple's Developer Program, which Safari extensions require, is 99 USD per membership year. The Mozilla pages we read state no fee for AMO.

Usually, yes. Each browser adds packaging, testing and a store submission, and Safari adds an Xcode project. Our builds start at $1,500, depending on complexity, and the written estimate lists each browser in scope. Edge is the inexpensive one, because it accepts the Chrome package.

You should. We recommend publishing under your own Chrome Web Store, Partner Center, AMO and Apple Developer accounts, so the listings, reviews and update rights stay with your company if you ever change developers.

Keep reading

Free · No obligation

Find out which browsers your extension needs

Tell us who your users are and what the extension does. Someone at DataCram replies with the browsers we would target first, what each adds, and a fixed written estimate.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote