How Much Does a Chrome Extension Cost to Build in 2026?

Chrome Extension Development Cost: Agency Estimates vs a Fixed Price

Chrome extension development costs $700–$1,800 as a fixed-price, AI-assisted build delivered in 6–14 days. Published agency estimates start at $3,000 and reach five figures once the extension talks to a SaaS backend.

PINCLER is an AI-first custom software development studio. We build browser extensions, API backends, SaaS MVPs and integrations at fixed prices between $500 and $2,500. On an extension, AI coding tools draft the TypeScript project, messaging and storage; senior engineers review the permission list and security model by hand, and your team pilots the build on the real pages it uses.

Read the agency rows as estimates, not quotes. MetaDesign Solutions calls its ranges directional and says they cover development only, with design, QA and project management usually priced separately; Cadence, which matches founders with engineers, prices by engineer time and lists $300–$1,000 for store submission and first-pass review fixes.

What Changed When Google Removed Manifest V2 Extensions?

Manifest V3 is now the only format Chrome runs. The Chrome Web Store stopped accepting new Manifest V2 extensions in 2022, Chrome 138 disabled the old format for every user on 24 July 2025, and on 31 August 2026 Google removed the remaining Manifest V2 extensions from the store. On Chrome 138, only companies using a Chrome admin policy could keep them switched on; Chrome's timeline says Chrome 139 and later do not run them at all, and installed copies get no more updates.

The rewrite is real work, not a version bump. Manifest V3 replaces the always-on background page with a service worker that Chrome stops when idle, so state held in memory must move to storage. It also bans logic fetched from a server: Chrome's security guide says "all of your extension's logic must be part of the extension package".

A migration runs like any other build: a fixed quote, a working preview, then review, as the build process shows. The steps for an old extension:

1. Check manifest_version in manifest.json: a 2 means the extension must move.
2. Move background-page logic into a service worker and keep state in extension storage.
3. Remove scripts loaded from a server, and eval() or new Function() outside sandboxed frames.
4. Cut host permissions down to the sites the extension actually needs.
5. Update the privacy policy and the store's data-use answers to match the new version.
6. Resubmit, and allow days, not hours, for review before staff receive the update.

What Do You Get for $700, $1,200 and $1,800?

Each tier adds to the one below, and all three ship as Manifest V3 TypeScript in your own repository, set up for your own developer account, with privacy policy text, documentation, a handover video and a 30-day bug-fix warranty. Edge and Brave run the same build; Firefox needs small manifest changes, an optional extra once the Chrome version ships.

Price the whole job, not only the part in the browser. The $1,800 tier connects to a backend you already run; if there is none, or it has no API the extension can call, that is a separate build, and so is billing. The table maps each piece to PINCLER's published catalogue, and SaaS MVP development cost covers the product side.

• Popup tool, $700: a popup-only extension with local storage, keyboard shortcuts and auto-update. Good for a lookup, calculator or one-click capture.
• Page-aware build, $1,200: adds content scripts that read or annotate pages, a side panel, context-menu actions and badge notifications. Good for highlighting or pulling data from pages.
• Synced product, $1,800: adds login and secure sync with your backend, encrypted cloud storage, store listing assets and review handling until approval.

What Does It Cost to Publish and Run an Extension?

At the time of writing (October 2026), Google charges a one-time $5 fee to register as a Chrome Web Store developer, collected at sign-up since March 2020, and Microsoft charges no registration fee for Edge Add-ons. Google also requires 2-Step Verification before you publish or update.

A popup tool that keeps data on the user's machine needs no server. A synced extension needs a backend: at the time of writing, Supabase's pricing page lists Pro from $25 a month with 100,000 monthly active users included, or $900 over three years. Its free plan pauses a project after a week of inactivity, so keep that for a pilot.

The store will not take payments for you. 9to5Google reported in September 2020 that Google was shutting down Chrome Web Store payments, with paid extensions losing them on 21 February 2021. A paid extension bills through its own provider and checks each user's plan on your backend, which is a payment gateway integration.

Before maintenance, with every input shown: a popup tool is $700 + $5 = $705. A synced build on a hosted database is $1,800 + $5 + $900 of Supabase Pro = $2,705, before any API work. The bottom of MetaDesign's simple range is $3,000 + $5 = $3,005, for development alone and with no backend.

The table adds MetaDesign's rule of thumb of 15–25% of the build cost a year for maintenance to every column, but a percentage of a lower price can understate the work, so treat those figures as a floor; page-aware extensions also break when sites change their layout. PINCLER's optional care plans start at $99 a month, or your own developer can take over the code.

How Long Does Chrome Web Store Review Take, and What Gets an Extension Rejected?

Chrome's review guide says most reviews finish within a few days, some take a few weeks, and you should contact support if one is pending after three weeks. The page was last updated in December 2021 and says its enforcement details are accurate only as of that date, so treat them as a guide.

Reviews slow down for new developers and new extensions, broad host permissions such as <all_urls>, sensitive permissions such as tabs or downloads, and large or hard-to-read code; obfuscation is not allowed. Chrome's quality guidelines also require a single, narrow purpose. A minor problem found after publishing usually earns a warning and 7–30 days to fix it.

The cheapest way to save review time is to ask for less. The activeTab permission grants temporary access to the current tab only when the user invokes the extension, and shows no warning at install. Before the first upload:

1. Turn on 2-Step Verification for the developer account.
2. Register with a company email you will always control; Chrome says it cannot be changed later.
3. Write the extension's single purpose in one sentence.
4. Request activeTab or named sites instead of <all_urls>.
5. Ship all code inside the package, unobfuscated.
6. Link a privacy policy covering what data you collect, how you use it and who receives it.
7. Answer the dashboard's privacy questions to match the policy and the code.
8. Give reviewers a test login if features sit behind sign-in.
9. Prepare screenshots and listing text that match what the extension does.
10. Keep the last good version tagged so you can resubmit it quickly.

How Do You Keep an Extension and Its Publisher Account Safe?

An extension updates itself, which is convenient until the wrong person publishes. Cyberhaven, a security company, told customers that an attacker had compromised the one admin account it used to publish to the Chrome Web Store and pushed a malicious version early on 25 December 2024; it was detected that afternoon, removed, and replaced by a clean version. TechCrunch reported on 27 December, citing the company's email, that the code could send logged-in sessions and cookies to the attacker, and that the store listing showed about 400,000 corporate users. Cyberhaven's own follow-up, reported by BleepingComputer on 31 December 2024, said an email that pretended to be from Google led an employee to give a malicious app access to the account, without any password being stolen.

Auto-update delivers each release to every installed copy, so treat the publisher account and release process like a production server. Whether AI-generated code is safe for production covers code review, taking a vibe-coded app to production covers the backend checks, and monitoring and alerting is a 3–7 day build that tells a person when errors spike after a release.

Do You Need an Extension, a Web App or Both?

Build an extension only when the work happens on someone else's pages. If users come to your product to do the job, a web app is cheaper to change and needs no store review. If the job is collecting data from many pages on a schedule with nobody browsing, that is a web scraper and data pipeline, not an extension. The tree carries no price on purpose.

Many products need both: the extension captures data where people already work, and a web app is where the team uses it. Before asking for quotes, list the pages, actions and data involved; how to write software requirements shows a format a developer can price.

Do users need it while they are on other sites?
  NO  -> build a web page or app, not an extension
  YES -> Does it need to read or change the page?
           NO  -> popup tool
           YES -> Does it save data to your product?
                    NO  -> page-aware build
                    YES -> synced build, plus an API
                           if you do not have one

Who Should Build a Custom Chrome Extension, and When Is an Existing One Enough?

Build one when the same copy-and-paste happens many times a day, or when your product would be used more one click away on the pages customers already visit. As an illustration, not a measured result: five people saving two minutes on each of 30 captures a day get back five hours a day between them.

An existing extension is enough when the job is generic, such as clipping pages, filling forms or saving tabs. If a store extension does it well for a small fee, pay the fee, and do not build one for a feature users would rarely open.

• Good fit: a SaaS product that wants one-click capture or lookups on the pages its customers use.
• Good fit: sales, recruiting or research teams copying the same web data into a CRM or sheet daily.
• Good fit: an internal Manifest V2 tool that no longer updates and must be rebuilt.
• Good fit: a product whose users would keep a side panel open while they work.
• Poor fit: a feature opened once a month, where a bookmark or web page does the job.
• Poor fit: no one to own the backend, fixes and store account after launch.
• Poor fit: enterprise single sign-on or policy deployment from day one; split that into phases.

What Are the Most Common Mistakes When Building a Chrome Extension?

Most extension problems are decided before any code is written, in the permission list, the account setup and the business model, and each has a cheap fix if caught early.

If a contractor builds it, keep the code, the store listing and the developer account in your company's name from day one; who owns your code lists what to put in the contract.

1. Asking for every site. <all_urls> slows review, alarms users at install and widens the damage of a breach.
2. One admin account. If one person holds the only login, losing it stops every update.
3. Loading code from a server. Store policy no longer allows remotely hosted code.
4. No privacy policy. Any extension that handles user data needs an accurate one.
5. Planning to charge through the store. Bill through your own provider and check plans on your server.
6. Ignoring the rules of the sites it reads. Check a site's terms before building a feature that copies its data.

PINCLER's Perspective on Extension Builds

Across the 79 builds in PINCLER's published fixed-price catalogue, the median advertised price is $1,450 and the median quoted delivery 13 days. The browser extension sits in the Integrations category, whose five builds have a median advertised price of $1,200 and a median quoted window of 10 days, and its 6–14 day window puts it among the 33 builds quoted at two weeks or less. The price holds because AI drafts the scaffold, messaging and storage, and senior engineers spend their time on permissions, the security model and testing on real pages.

These are advertised prices and quoted windows for published catalogue builds — a published price list rather than a delivery record. The data is in what you can build, the fixed pricing bands are the ones quoted on a call, and the cost calculator gives a first estimate.

There are limits. An enterprise extension with single sign-on, data-loss-prevention hooks and policy deployment does not fit one fixed price: we split it into phases, each inside the band, or decline it. Whoever builds yours, keep the build and the hosting separate on the quote. What a Telegram Mini App costs runs the same arithmetic for another product that lives inside someone else's software.

The Bottom Line

A custom Chrome extension costs $700–$1,800 as a fixed-price build in 6–14 days, because AI drafts the code and senior engineers review the permissions, security model and store submission. Published agency estimates start at $3,000 for development alone, and publishing adds a one-time $5 on Chrome and nothing on Edge.

Decide on use, not novelty. If people would open it daily on pages you do not control, build it with one purpose and the fewest permissions; if an existing extension or a web page does the job, use that. A free 30-minute call returns a written fixed quote within a working day, and the browser extension build page shows what each tier includes.