Fixed quotes, no hourly surprises

Chrome extension development, Manifest V3 and privacy first

We build Chrome and Edge extensions on Manifest V3: a service worker in the background, a popup or side panel, scripts that read the page only when needed and an optional link to your web account. We handle permissions, privacy disclosures and Web Store submission. Projects typically cost $5,000 to $20,000, most around $10,000.

Use cases

What we build for your business.

Page checkers and scanners

Grade a page for security headers, SEO or accessibility as the user browses.

Sales and CRM helpers

Save a profile or lead from the page into your CRM with one click.

Internal productivity tools

Shortcuts, templates and checks for the web apps your team uses all day.

Companion to your SaaS

Let signed-in users save results from any site back to their account.

AI helpers in the browser

Summarize or translate selected text with Chrome built-in AI, keeping text on the device.

Manifest V2 migrations

Move an older extension to Manifest V3 so it keeps working and can be updated.

Trends we track

What's new in 2026 and how we use it.

Changes we have checked against the official documentation, and only the ones we can deliver today.

Manifest V2 is gone

Chrome disabled Manifest V2 extensions for all users from Chrome 138 (July 2025), and remaining V2 items were removed from the Web Store by August 31, 2026. New work is Manifest V3 only.

Source: developer.chrome.com

Built-in AI APIs in Chrome

The Summarizer, Translator and Language Detector APIs are stable in Chrome 138 for web pages and extensions, and the Prompt API is available to extensions, all running on a built-in model.

Source: developer.chrome.com

Privacy by design

Local analysis with on-device models means page content does not need to leave the browser, which also simplifies the Web Store privacy disclosures.

Source: developer.chrome.com

Project planner

How a project runs, phase by phase.

Typical durations for a focused first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Browser Extension Development project plan

Typical time to launch: about 9 weeks, then support

  1. 01

    Discovery

    About 1 week

    What the extension must do, which sites it touches and the smallest set of permissions that allows it.

  2. 02

    Architecture

    About 1 week

    Service worker, popup, options and injected scripts, message flow, storage and the account link.

  3. 03

    Build

    3 to 5 weeks

    Working builds you can load unpacked, with a light and dark UI and a settings page.

  4. 04

    Test

    1 to 2 weeks

    Many real sites, worker sleep and restart, permission prompts, Chrome and Edge.

  5. 05

    Launch

    About 1 week

    Store listing, screenshots, privacy fields and policy page, then Chrome Web Store review.

  6. 06

    Support

    Ongoing

    Chrome API changes, store policy updates and new features.

Architecture

A typical Manifest V3 extension at a glance.

The stack we usually start from. We adapt it to the tools you already pay for.
Web page Any site the user opens Injected script Runs on demand Service worker Events, headers chrome.storage Session and local Built-in AI Optional, on device Popup and options Results, settings Your web API Only if signed in
  • Input
  • Logic and services
  • Data
  • AI step
  • People
  • Output

How it flows

  1. 1 The service worker listens for browser events (navigation, response headers) and wakes only when needed.
  2. 2 Scripts are injected into the page on demand with chrome.scripting, read what is required and return a result.
  3. 3 Results are kept in chrome.storage so they survive the worker going to sleep; optional built-in AI runs on the device.
  4. 4 The popup and options page show results and settings, and talk to your web API only if the user connects an account.

Tech we use

Manifest V3 Service worker chrome.scripting chrome.storage webRequest and webNavigation Shadow DOM Chrome built-in AI Vanilla JS or TypeScript Chrome Web Store Microsoft Edge Add-ons

Pricing

$5,000 to $20,000

Most projects land around $10,000 per extension.

Fixed quote after discovery. The one-time Chrome Web Store developer fee is paid by you.

Book a free 20-minute call

FAQ

Browser Extension Development questions, answered.

Still have a question?

Talk to us

Our fixed quotes run from $5,000 to $20,000, typically around $10,000. A focused single-purpose extension sits at the lower end; account sync, a backend, AI features and multi-browser support push it up.

Review times vary. Many updates clear within a few days, while new items or those asking for broad permissions can take longer. We keep permissions narrow and the privacy fields accurate to avoid delays.

Manifest V3 is the current Chrome extension platform. It replaces background pages with a service worker and limits remote code. Manifest V2 extensions no longer run in current Chrome, so any new or updated extension must use V3.

As few as possible. We start from the job (such as reading headers or injecting a script on click) and request only the permissions and host access that job needs, explaining each one in the store listing.

Yes. Edge, Brave and Opera run Chromium extensions with little or no change, and we can publish to Microsoft Edge Add-ons as well. Firefox needs some adjustments, which we scope separately.

Yes. Your site can hand the extension a scoped token after the user signs in, and the extension calls your API only when the user asks, such as saving a result to their account.

Free 20-minute call

Tell us what you want to build

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call