The price, line by line

How Much Does It Cost to Build a Chrome Extension? Five Decisions, the Store Fees and Our Floor

Three developers price the same extension three ways, and none of them explains the gap. The gap is usually five decisions nobody wrote down. Here they are, with our own floor, every fee the stores publish, and the cases where the right budget is zero.

November 16, 2026 · 9 min read

store developer pages · read November 2026
What the stores charge, beside the build
Store fees, and where a custom extension starts
Published
Chrome Web Store registration, one time$5
Microsoft Edge Add-ons registrationNo fee
Apple Developer Program, for Safari99 USD a year
Firefox add-on signingNo fee stated
DataCram custom extension buildFrom $1,500
published fees as of November 2026; Apple's price may vary by region; DataCram's price depends on complexity

The short answer

A custom Chrome extension costs what five decisions make it cost: how many sites it touches, whether it needs a backend, whether users sign in and pay, how many browsers it ships to, and how much store work it needs. DataCram builds them from $1,500, depending on complexity. As of November 2026, Google's one-time developer fee is $5, Microsoft charges none, and Apple's program is 99 USD a year.

On this page
  1. Three quotes for one idea, and the decisions hiding behind them
  2. The five decisions that move the number
  3. What each store charges a developer, as of November 2026
  4. The bills that arrive after launch day
  5. Charging your own users: what GatorCrawl's model shows
  6. When the right budget is zero
  7. Five questions that make any extension quote comparable

Three quotes for one idea, and the decisions hiding behind them

The idea fits in a sentence: show our price next to a competitor's product page. One developer comes back with a small number. Another comes back with a large one. Both may be honest, because they heard different extensions. The first pictured a script that reads one site and shows a figure. The second pictured user accounts, a billing page, four browsers and a server keeping the prices fresh. Same sentence. Different products.

That is why our price is a floor and a method rather than a menu. DataCram builds custom browser extensions from $1,500, depending on complexity, with a fixed written estimate before work starts. Store submission, the privacy disclosures and the permission plan are part of every build. The rest of this page shows what lifts a project above the floor, so you can read anyone's quote, ours included, with the right questions in hand. The full process lives on our custom Chrome extension development page.

An extension's price is set by the decisions in the first conversation, not the hours in the last week.

The five decisions that move the number

What pushes an extension estimate up, and why
DecisionNear the floorWell above itWhy it costs
Sites it touchesOne site, like GatorCrawl's single content script on Google resultsMany sites, each with its own page structureEvery site's layout is code to write, test and repair when that site redesigns
A backendCalls an API you already runNeeds a new server, database and admin screensThe server holds the logic Manifest V3 will not let an extension download
Accounts and billingNo login, or your existing oneNew sign-in, plans, credits and a billing pageCharging runs through your own site, since Chrome Web Store payments are deprecated
BrowsersChrome, then EdgeChrome, Edge, Firefox and SafariFirefox needs a different background setup, and Safari needs an Xcode project
Store workOne public listingSeveral listings, private domain publishing, long disclosuresEach listing needs text, images, a privacy policy and a reason for every permission

Notice what is missing: the number of buttons. Interface work matters, but the expensive surprises live in those five rows, and the first row hides the biggest. An extension that reads someone else's website depends on that site's markup, and the site owes you no warning before it changes. The GatorCrawl case study shows how keeping to one site and one existing API kept our own build small.

Bright blue duotone of a single puzzle piece balanced on a short stack of coins, with solid circles and triangles floating behind it
Most of an extension's cost is fixed by a handful of choices made before any code exists.

What each store charges a developer, as of November 2026

Store fees are the smallest line in any extension budget, and the only one with a published number. We read each on the store's own pages.

Developer fees by store, as of November 2026
StoreFeeWhere it is stated
Chrome Web Store$5, one timeAn April 30, 2026 entry on Chrome's What's new page; the register page says only "one-time registration fee"
Microsoft Edge Add-onsNo registration feeMicrosoft's developer account page says so in those words
Apple, for Safari99 USD per membership yearApple's program page; local prices may vary, and eligible nonprofits, schools and government bodies can ask for a waiver
Firefox add-onsNone statedThe Mozilla signing overview and submission pages we read name no fee, so we quote none

Chrome's fee buys an account, not a listing. Google's publishing docs say a new publisher is limited to two published extensions at first, which matters only if you plan a family of tools. Register the account in your company's name. The listing, its users and every future update ride on it.

One cost has disappeared entirely. Google's notice on Chrome Web Store payments, which we read through an archived copy because the page now returns an error, says that system is "now deprecated" and lists February 1, 2021 as the date existing items stopped charging through it. An extension that charges money now bills through your own site, and the store's payment policy says you must "clearly identify that you, not Google, are the seller."

The bills that arrive after launch day

The build is the visible cost. These are the quieter ones. A fair estimate names them even when it cannot price them yet.

  • Updates and maintenance. Quoted when needed. Google's review process page says updates go through the same review as new items, so even a one-line fix waits in line.
  • Platform changes. Chrome's timeline records that all remaining Manifest V2 extensions were removed from the store on August 31, 2026. Anything built on the old format needs a rebuild, not a patch. Our Manifest V3 page explains the move.
  • Periodic policy reviews. Google reviews published items from time to time, and for minor violations publishers are "typically given 7 to 30 days" to fix them, as of November 2026.
  • A new permission. When an update adds a permission with a warning, Chrome disables the extension until each user accepts it. That is paid in users, not dollars, and it is cheapest to avoid in the first build.
  • Running costs upstream. If the extension calls your server, an AI model or a data provider, those charges land on whichever accounts run them, at those providers' own rates.

Our page on extension maintenance describes what a typical update involves, and browser extension security covers the account protection that costs nothing and prevents the most expensive day of all.

Charging your own users: what GatorCrawl's model shows

Some readers need the other half of the math: what to charge. GatorCrawl Keywords, the keyword app we built along with its Chrome extension, is one worked answer. Its site says the extension is free to install and that lookups use the plan's credits. As of November 2026, plans list at $19, $49 and $129 a month, with 20,000, 55,000 and 145,000 keyword credits, and every plan starts with a seven-day trial for $5.

What the builder pays

  • One build, from $1,500 with DataCram, depending on complexity
  • A $5 one-time Chrome developer fee, as of November 2026
  • Server and data costs behind every lookup
  • Updates, quoted when they are needed

What a user pays, in GatorCrawl's model

  • Nothing to install the extension
  • A plan, with the extension "Included with every plan"
  • Credits, where the site says "One credit is one keyword with data"
  • A $5 trial for seven days before the plan begins, as of November 2026

Credits suit an extension where each lookup costs you money upstream. A flat plan suits one that costs nothing per use. Our guide to monetizing a browser extension compares the models, and the SaaS companion page shows how an extension shares an app's account so billing never has to live inside the extension.

When the right budget is zero

The cheapest extension is the one you never commission. We say this on the first call, and we say it here so you can save yourself the call.

If the idea passes those tests and the open question is what to build first, a few hours with a fractional CTO can cost less than a wrong build. Our extension or web app guide argues both sides fairly, and the browser extensions hub lists every kind of extension we build.

Five questions that make any extension quote comparable

  1. 1

    Where is the permission list?

    If the quote does not say what users will be asked to allow, the developer has not decided yet, and the price can move when they do.

  2. 2

    Where does the logic run?

    Manifest V3 allows no remotely hosted code. A quote that keeps rules and keys on a server you control describes a sounder build than one that crams them into the package.

  3. 3

    Whose developer account?

    The listing and its users belong under your account. Ask what happens to them if the relationship ends.

  4. 4

    Is the store work included?

    Listing text, screenshots, privacy disclosures and permission justifications are real work. Ours are part of the build.

  5. 5

    What happens after launch?

    A fair quote says how updates are priced. Ours are quoted when needed. Nobody honest promises a review date.

Then compare like with like. How long a build takes explains the part of the calendar nobody controls, and our API integration service covers the server side, where connections to your own systems go live the same day. Or call (210) 346-0848 and describe the job in a sentence.

Questions owners ask about custom browser extensions

Shrink the job. One site, one existing API, Chrome only, no new login and a single listing keep a build near our $1,500 floor, depending on complexity. Add Edge later, since Microsoft says a Chromium extension can be submitted there without a rewrite. Before any of that, check whether a maintained extension or a bookmarklet already does it.

Yes, a one-time registration fee. Chrome's What's new page, in an April 30, 2026 entry, puts it at $5, as of November 2026; the register page itself names no amount. Google also requires 2-Step Verification on the developer account before you publish or update anything, and new publishers start with a limit of two published extensions.

Microsoft's documentation says there is no registration fee for submitting extensions to the Edge program, as of November 2026. For Firefox, the Mozilla signing and submission pages we read state no fee in either direction, so we do not quote one. Apple, for Safari, lists its developer program at 99 USD per membership year.

No. Google's payments notice, read through an archived copy, says Chrome Web Store payments are deprecated and that existing items stopped charging through it on February 1, 2021. Extensions now bill through the developer's own site and processor, and store policy requires you to make clear that you, not Google, are the seller.

Because each developer pictures a different product from the same sentence. The five decisions that move cost are the sites the extension touches, a backend, accounts and billing, the number of browsers, and store work. Ask each developer to list those five in writing, along with the permissions the extension will request, and the quotes become comparable.

No. Store submission, the permission plan and the privacy disclosures are part of the build; updates and maintenance after launch are quoted when needed. The usual reasons for an update are a change on a site the extension reads, a browser platform change, a store policy change, or a feature you decide to add.

Keep reading

Free · No obligation

Get the five decisions priced in writing

Describe the extension in a sentence or two. We reply with the questions that set the price, then a fixed written estimate from $1,500, or a straight answer that a cheaper tool already exists.

Which of these sounds like you? (pick any)

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

CallGet a quote