How to Build a Chrome Extension MVP: Cost, Timeline, Store Review

A Chrome extension MVP costs $2,000-$5,000 if it works alone inside the browser, and $5,000-$18,000 once it needs accounts, billing or AI, which most paid extensions do. The build takes 1-3 weeks for the simple version and 3-6 weeks with a backend, plus 1-3 days of Chrome Web Store review that can stretch to two weeks if you ask for broad permissions. An extension is the right first build only when the value happens inside a website the user already has open; if the value is a standalone workflow or must work on a phone, a web app is the better MVP.

What a Chrome extension can and cannot do

An extension is a small program that runs inside the user's Chrome and can see and change the pages they visit, within the permissions the user approves. That makes it unbeatable for one class of product and useless for another. Before you pay anyone, check which class yours is in.

What an extension does well

• Read the page the user is on. Pull the job listing, the LinkedIn profile, the product price or the email thread and do something useful with it, without the user copying anything.
• Add buttons and panels to tools the user already lives in. A "Save to CRM" button on Gmail, a reply generator inside a support desk, a price-history panel on Amazon.
• Fill forms and automate clicks on the current site. Applying to jobs, posting listings, filling the same supplier form 40 times a day.
• Ship fast through one channel. The Chrome Web Store reaches more than 3 billion Chrome users on desktop, charges a $5 one-time listing fee, and an install takes one click.

What an extension cannot do

• Run on phones. Chrome on Android and iPhone does not support extensions at all. Your mobile users get nothing.
• Work when Chrome is closed. No scheduled jobs overnight, no "watch this price while I sleep" unless a server does the watching.
• Hold secrets. Anything inside the extension can be read by the user. API keys for AI models or paid data sources must live on your server, never in the extension.
• Take payments. Google retired Chrome Web Store payments, so there is no in-store checkout. Billing happens on a web page you control.
• Bypass site protections. If a site blocks scraping, rate-limits requests or changes its layout, your extension breaks and you ship a fix.

Manifest V3 limits that shape your scope

Every new Chrome extension must follow Manifest V3, the rulebook Google finished enforcing in 2025 when it switched off the last Manifest V2 extensions. Four of its rules directly change what your MVP can promise and what it costs.

1. No code downloaded at runtime

All the extension's code must be inside the package Google reviewed. You cannot pull new logic from your server after approval. That kills the "ship a shell now, add features later without review" shortcut. Every feature change is a new version through review, usually a one-day turnaround for updates, but a day nonetheless. Content and settings can still come from your server; code cannot.

2. The background process goes to sleep

The old always-on background page is gone. It is replaced by a service worker that Chrome shuts down after roughly 30 seconds of inactivity and restarts when something wakes it. Anything that needs to stay running, such as polling a site every minute, keeping a connection open or processing a long queue, must be redesigned around alarms, events and a backend. Builders who have not shipped under V3 underestimate this and lose a week.

3. Network blocking is declarative only

Extensions can no longer inspect and rewrite every network request with custom code. They declare static rules instead, with a cap on how many rules can be active. Ad blockers, privacy tools and anything that depends on modifying traffic on the fly either fit inside those rules or do not get built. Reading page content and talking to your own API are unaffected.

4. Permissions are narrow and visible

The user sees exactly which sites the extension can access, and Chrome lets them restrict it to "when I click the icon". Asking for access to all websites triggers a scary install warning and a slower review. A good spec names the 2-5 domains the MVP actually needs and asks for nothing else.

These rules push the "real" work to a backend, which is the single biggest reason extension quotes vary.

What a Chrome extension MVP costs in 2026

Prices below are what we see across freelancers, small studios and fixed-price shops for a scoped MVP, not a polished product. The spread inside each tier comes from how many sites the extension must handle and whether the builder has shipped under Manifest V3 before.

Three line items surprise founders most. Each additional site adds $800-$2,000 because it has its own page structure. A side panel instead of a popup adds $500-$1,500. A Firefox or Safari port adds 20-40% of the build, so leave it out of the MVP. For a feature-by-feature view of the backend part, see what each MVP feature costs in 2026, and run your own list through the free MVP cost calculator.

Ongoing cost is low because the user's browser does the computing. The exceptions are AI usage, which scales with every call, and fixes when a site you automate changes its layout, typically $200-$800 each and 2-4 a year. The general picture is in what an MVP costs to run each month.

Timeline from kickoff to store listing

A realistic extension MVP calendar has four blocks, and the one founders forget is the store listing.

• Days 1-2: scope and permissions. Decide the 3-5 features, name the exact sites the extension touches, and write the permission list. This step decides your review time later.
• Days 3-14: build. A browser-only extension is usable by day 5-7 and finished by day 10-14. Add 2-3 weeks when a backend with login and billing is in scope.
• Days 10-16: listing assets. The store requires a 128 px icon, 1-5 screenshots at 1280x800, a description, a privacy policy URL and a written justification for every permission. Rejections for missing or vague justifications are the most common delay and are entirely avoidable.
• Days 15-19: review. Most new extensions clear in 1-3 days. Broad host permissions, page-content reading on all sites, or anything that touches personal data can take 1-2 weeks, and a rejection restarts the clock.

Put the blocks together and a browser-only MVP is in the store in 3-4 weeks; a backend extension in 5-8 weeks. The build itself fits in 14 days when the scope is cut properly. Compare this with how long it takes to build an MVP across other product types.

Chrome Web Store review: what gets rejected

Review is automated first and human second, and the rejections follow a short list. Fix these before you submit.

• Permissions the extension does not visibly use. If you request access to all sites but only act on two, expect a rejection asking you to narrow the list.
• Missing or generic privacy policy. Any extension that reads page content or sends data to a server needs a policy URL that says what is collected and why. A policy page costs an hour to write and saves a week.
• Single purpose rule. One extension, one clear job. A "productivity suite" with five unrelated tools gets flagged. Split or cut.
• Remote code. Loading scripts from a server violates Manifest V3 and is caught automatically.
• Misleading listing. Screenshots or descriptions that promise features the package does not contain.
• Affiliate and data practices not disclosed. If the extension inserts affiliate links or collects browsing data, the listing must say so in plain words.

Two more facts that matter for planning. The $5 developer fee is per account, not per extension. And an extension can be published "unlisted" for a private beta with 10-50 testers before the public listing, so you never burn the launch review on an unfinished version. Make sure the developer account is yours from day one; the full list of accounts a founder must control is in which accounts a founder must own before the build.

Billing and accounts: why most extensions need a small web app

Google's in-store payments have been gone since 2021, so an extension that charges money cannot charge inside Chrome. The working pattern in 2026 is the same for almost every paid extension:

1. The user clicks "Upgrade" in the extension and lands on a web page you own.
2. They pay through Stripe, Paddle or Lemon Squeezy, which handle cards, tax and invoices.
3. Your backend records the subscription against the user's account.
4. The extension asks your backend "is this user paid?" and unlocks features accordingly, with a cached answer so a short network failure does not lock the user out.

That page, the login behind it and the license check are a small web app, and they add $2,500-$6,000 to a browser-only build. There are two ways to keep that number down. Charge a one-time license through a checkout link and store the key in the extension, which works for simple tools and skips the login entirely. Or launch free, collect installs and reviews, and add billing in version two once you know people stay. Both are legitimate MVP moves. The mechanics of the checkout side are in how to add payments to your MVP.

When a web app is the better MVP

An extension wins when the product lives on top of someone else's page. A web app wins when the product is the page. The table is the decision in one glance.

One pattern fails often: the web app wearing an extension disguise. A founder wants a CRM, decides "people live in Gmail", and asks for the whole CRM as a Gmail side panel. The result is a cramped interface, a long review and a desktop-only product. The right MVP is a web app with a thin Gmail extension that captures contacts into it. The B2B SaaS MVP guide covers the web-app side of that split.

Whichever you choose, the spec must name the exact sites by URL, say where the interface lives (popup, side panel or injected into the page), and state which data leaves the device. Those three answers set the permission list, the review risk and most of the cost; everything else follows how to write an MVP spec.

FAQ

How much does a Chrome extension MVP cost in 2026?

A simple extension with no accounts and no backend costs $2,000-$5,000 from a freelancer or small studio. An extension with login, a hosted backend and Stripe billing runs $5,000-$12,000. An AI-powered extension with usage limits and a dashboard runs $8,000-$18,000. The Chrome Web Store itself charges a one-time $5 developer registration fee.

How long does Chrome Web Store review take?

Most new extensions are reviewed within 1-3 days, and updates are often approved within 24 hours. Extensions that request broad host permissions, read page content on every site, or handle personal data can sit in review for 1-2 weeks, and a rejection restarts the clock. Plan for a week of buffer in your launch date.

Can a Chrome extension charge a subscription?

Yes, but not through the Web Store. Google retired its in-store payments, so the extension must send the user to a web page where they pay through Stripe or a similar processor, and the extension then checks a license from your backend. That means a paid extension MVP always includes a small web app for accounts and billing.

Does a Chrome extension work on mobile?

No. Chrome on Android and iPhone does not run extensions, so a Chrome extension MVP reaches desktop and laptop users only. If a large share of your users are on phones, build a web app or mobile app first and add the extension later as a desktop companion.

What is Manifest V3 and why does it matter for my MVP?

Manifest V3 is the current set of rules every Chrome extension must follow. It bans code downloaded from a server at runtime, replaces the always-on background page with a service worker that Chrome shuts down after about 30 seconds of inactivity, and limits how extensions can block or rewrite network requests. Any feature that needs a long-running process or remote scripts has to move to your backend.

Should I build a Chrome extension or a web app first?

Build the extension first only when the core value happens inside another website the user already has open, such as reading a page, filling a form or adding a button to a tool they use all day. If the value is a standalone workflow, a dashboard, a marketplace or anything users must reach from a phone, build a web app first. Most paid extensions end up needing a small web app for billing anyway.

All third-party names and trademarks belong to their respective owners and are used for identification only. Any market figures reflect our experience building MVPs and typical ranges as of October 20, 2026, and may change at any time. Spotted something outdated or inaccurate? Email talk@squadprime.com and we'll correct it promptly.

Related: How to Build a B2B SaaS MVP That Companies Will Pay For · The Best Tech Stack for an MVP in 2026