Manifest V3, TypeScript, tested before it ships

Chrome Extension Development Services

Chrome extension development that starts from a written brief and ends with a build you can load, review and publish: the popup, the page scripts, the background logic and the permission notes a store reviewer reads.
  • Popup and side panel
  • Content scripts
  • Service worker
Packages from $319 in USD, one extension
  • Fixed prices in US dollars
  • TypeScript source handed over
  • Every permission explained in plain words
Overviewchrome-extension / why-build-one

Why put the tool inside the browser

If you want to build a chrome extension, the reason is usually simple: your users already live in a browser tab, and a toolbar button is one click from the page they are working on. Our chrome extension development services turn that idea into a working package with a clear scope and a fixed price.

An extension is not a small website. It is several separate pieces that must agree with each other: a manifest that declares what the extension is allowed to do, a popup or side panel for the interface, content scripts that run inside other people’s pages, and a background service worker that wakes for events and goes back to sleep. Most failed builds fail at the seams between those pieces, not inside any one of them.

Two rules in the platform shape every decision we make. Under Manifest V3, an extension can only run JavaScript that ships inside its own package, so nothing can be fetched and executed later. And a service worker is shut down after 30 seconds of inactivity, so anything it needs to remember must be saved to storage instead of kept in a variable.

We write the extension in TypeScript, test it on the exact sites you list, and keep the permission list as short as the feature allows. A short list is not only tidier for your users. Chrome Web Store reviewers look harder at broad access, so it is also the fastest route to approval.

Who it is forchrome-extension / audience

Who needs custom chrome extension development

Extensions pay off when the work happens on someone else’s page. These are the people who most often come to us.

SaaS product teams

Your customers copy data between your app and another site all day. A companion extension reads the page they are on and sends it to your product without a tab switch.

Sales and support teams

Reps want the CRM record beside the profile they are reading. An extension can show it in a side panel and write notes back, with no copy and paste.

Agencies with client requests

A client asks for a button that fixes something on a site you do not control. An extension changes the page for their staff only, and nothing on the live site is touched.

Researchers and analysts

Collecting prices, listings or citations by hand is slow. A small tool can capture the fields you care about into a table as you browse.

Internal tool owners

An ops lead wants a checklist overlay on an internal admin screen. A private extension adds it for the team and leaves the vendor’s software alone.

Solo makers with an idea

You have a one-sentence idea for a utility and no time to learn the extension platform. A single-purpose build gets it into a real browser quickly.

Signschrome-extension / symptoms

Signs it is time to create a chrome extension

One of these is a hint. Three or four together mean a browser extension will save real hours.

Repeated copy and paste

People move the same fields from one web page into another several times a day, and mistakes creep in when they are tired.

A page you cannot change

A vendor site hides a button or buries a number you need. You cannot edit their code, but you can change how it looks in your own browser.

Your product lives in a tab

Users must leave the page they are on to use your service. A toolbar button or side panel keeps them where they are.

A bookmarklet that outgrew itself

The snippet works until a site changes its layout or blocks inline scripts, and nobody remembers how it was written.

A script that stopped working

A draft from an AI tool or an older Manifest V2 project loads with errors, or works once and then goes silent.

Staff share a workaround

The team passes around a screenshot of steps to follow. Turning those steps into one button removes the training and the drift.

This brief wants to read your idea

Describe the page it runs on and the one action you want. We reply with which package fits and which permissions we would ask for.

Includedchrome-extension / scope

What a chrome extension developer builds for you

The package you pick decides how many of these apply. The core of each is always written, tested and explained.

Manifest and permissions

A Manifest V3 file that asks only for what the features need. We prefer activeTab and optional permissions over broad host patterns, because access is then granted when the user acts.

Popup, side panel or options

The interface your users touch, built to load quickly and to follow the light or dark setting of the browser where you ask for it.

Content scripts

Code that reads or changes the page, tested on each site you list. It talks to the rest of the extension by messages, since page scripts cannot use most extension APIs directly.

Service worker logic

Event handling, alarms and storage written for a worker that sleeps. State survives a restart because it is saved, not remembered.

Outside services

Calls to the API you already use, with sensible messages for a failed request, an expired key or a slow reply. This part belongs to the Standard and Advanced scope.

Review preparation

Plain-language reasons for each permission and notes for the store reviewer, so a question from the review team has an answer ready.

Deliverableschrome-extension / package

Your chrome extension source code and what ships with it

You receive files you can open, build and hand to another developer, not a black box.

What you receiveWhat it is for
manifest.jsonThe declaration of permissions, entry points and the minimum Chrome version, with a note beside each permission explaining why it is there.
TypeScript sourceTyped code split into popup, content scripts and service worker, so the next developer can follow where each message goes.
Packaged buildA zip that loads unpacked from the extensions page for testing and is ready to upload to the store dashboard.
Build and run notesHow to install dependencies, start the dev build with live reload and produce the release package.
Permission explanationsWording you can paste into the store listing and privacy fields, checked against what the code does.
Test notesThe sites and cases we tried, so you can repeat the checks after any later change.

The Advanced package adds the full permission and privacy review and a build guide written for whoever maintains the code after us.

Pricing calculator

Build your price for a chrome extension built with ai or by hand

Tell us what the extension shows, who it talks to and where it will be published, then see a fixed price and delivery estimate before you pay. Nothing is preselected.


Choose the size of the extensionRequired

The package sets the core price. A single-purpose tool is the focused build; an extension that signs people in and talks to a service is a larger project.

A manifest, a popup and one clear feature, such as saving a note, restyling a page or copying a table. Choose it when the whole idea fits in one sentence.

  • Manifest V3 setup and popup
  • One feature built and tested
  • Load-unpacked install steps

A popup, an options page, a background worker and saved settings. Choose it when the extension must remember choices and behave differently from one site to the next.

  • Popup, options page and storage
  • Background worker and messaging
  • Test pass on the sites you name

An extension that signs people in and exchanges data with your service, with a permission review and a clean path for later updates. Choose it when the extension is part of a product.

  • Sign-in flow with safe token handling
  • Permission and privacy review
  • TypeScript source and build guide handed over

Extensions for several browsers, heavy page scraping or tools tied to a complex backend need a closer look, so we quote them individually and confirm a fixed figure before any work starts.

Where does the extension work?Required

Each part of the browser it touches is another set of permissions and another place to test.

What data does it use?Required

Where the data lives decides how much security and error handling the extension needs.

How will it be released?Required

Chrome Web Store review has its own requirements. Tell us how much of it you want handled.

How soon do you need it?Required

Priority and Express move your build ahead of the normal queue. The delivery estimate under each option updates with your choices.

Optional extrasOptional

Add only what your extension needs. Each one is priced separately and can be removed from the summary at any time.

Prices are in US dollars for one extension and are an unverified estimate until the owner confirms them. The Chrome Web Store developer registration, hosting and third-party service fees are not included, and the store decides whether and when an extension is approved.

Add-onschrome-extension / extras

Add-ons for your extension build

Dark mode

$119

Theme support for the popup, options page and any side panel, following the browser setting or a switch your users control.

Extra integration

$169

One more outside service connected, such as a spreadsheet, CRM or notes tool, with its own settings and error handling.

Build and test pipeline

$149

An automated build and test run on every commit, so a release package is produced the same way each time.

Edge and Firefox build

$219

The extension adapted and tested for Edge and Firefox, with every difference between the browsers written down.

Automated tests

$139

Tests for the main logic and the messages between parts, so later edits are safer for whoever maintains the code.

Maintenance guide

$69

A written guide to the code layout, how to build it and what to check when browser rules change.

Pricing factorschrome-extension / what-moves-price

What moves the price of an extension

Each factor is a choice in the calculator, so the figure you see is the figure you pay.

FactorWhy it changes the effort
Where it worksA popup alone is one surface. Page changes add content scripts that must be tested on every site, and a side panel adds another screen and more messages.
Permissions requestedBroad host access and sensitive permissions such as tabs, cookies or downloads slow the store review, so we justify each one and trim what the feature does not need.
Data and accountsStoring data in the browser is simple. Signing users in and talking to your server needs token storage, refresh and a clean sign-out.
Number of sites it runs onEvery site you name has its own layout and its own habit of changing it, so each one is a separate test.
Store submissionYou can publish yourself from a packaged build, or we prepare the listing and handle changes the review team asks for.
Delivery speedPriority and Express are priced from the real extra effort of queue changes and out-of-hours work, not a flat percentage.

$ extension --scope "what should the button do?"

Send one sentence and the address of the page it runs on. We answer with the package we would choose and any permission that worries us. Ask for a quote

Processchrome-extension / how-we-work

How we make a chrome extension from scratch

  1. Write the briefOne page: who uses it, which sites it touches, the single action it performs and what it must never do.
  2. Draft the manifestWe list the minimum permissions first, because they shape the design and the review.
  3. Build the thin versionA popup, one script and a worker that talk to each other, loaded unpacked so you can click it early.
  4. Add the real behaviourFeatures, storage and any outside service, with the worker written to survive a shutdown.
  5. Test on your sitesEach listed page is tried, then tried again after a reload and after the browser restarts.
  6. Package and hand overSource, build, permission notes and, if chosen, a prepared store submission.
Timelinechrome-extension / schedule

Timeline and what we need from you

Timing

The calculator shows a delivery range that updates with your choices, and the date is confirmed before you pay. Store review happens after we finish and is outside our control: Google says most reviews finish within a few days but some take weeks.

Access we ask for

The addresses of the pages the extension runs on, a login to a test account if they need one, and any API documentation. Publishing needs your own Chrome Web Store developer account.

What helps most

Screenshots of the workflow today, an example of the data you want captured and a list of things the extension must never touch.

Platformschrome-extension / stack

Tools, frameworks and formats we work with

We write TypeScript and build with Vite-based tooling. WXT, Plasmo and CRXJS are the common frameworks for that job, and each gives you a dev build that reloads as you edit. For a small extension we often use plain TypeScript with a bundler, because fewer layers mean less to maintain.

Interfaces can be plain HTML and CSS or React, Vue or Svelte. Chromium-based browsers share one codebase, though Edge has its own store; Firefox and Safari need separate packaging, and Safari ships inside an app, so those are priced as an extra.

Frameworks

WXT, Plasmo, CRXJS or none at all. We pick for the size of the project and say why, and you may choose one yourself.

Language and checks

TypeScript with strict settings and a linter, so message shapes between popup, page and worker are typed on both ends.

Delivery format

A zip for the store dashboard and an unpacked folder for testing, plus the repository files if you want a build pipeline.

Proofchrome-extension / shipped

Shipped extensions, reserved for real work

Reserved: store listing

Reserve this card for a real Chrome Web Store listing screenshot of an extension we built, shared with the owner’s consent.

Reserved: before and after

Reserve this card for a real pair of screenshots showing a page before and after the extension changed it.

Reserved: permission list

Reserve this card for a real manifest permission list that was trimmed to pass review.

Reviewschrome-extension / client-notes

What clients say after the first install

Reserved: product owner

Reserve this card for a real quote from a SaaS owner about a companion extension.

Reserved: operations lead

Reserve this card for a real quote from a team that replaced a manual workflow with one button.

Reserved: agency partner

Reserve this card for a real quote from an agency that passed a client request to us.

Relatedchrome-extension / next-to

Work that often sits beside an extension

Web application development

The dashboard and sign-in that an extension reports to.

API integration

Connecting the services your extension reads from and writes to.

Workflow automation

Moving captured data on to spreadsheets, CRMs and alerts.

Google Workspace add-ons

Tools that live inside Gmail, Docs or Sheets rather than the browser.

Web scraping tools

Collecting page data on a schedule when no browser is open.

Landing pages for your launch

A clear page that explains the extension and sends visitors to install it.

FAQchrome-extension / questions

Questions before you commission an extension

How is a chrome extension development project scoped and priced?

By three choices: where the extension works (popup only, page changes, or page plus background and side panel), what data it uses (browser only, one outside service, or sign-in with your own server) and how it is released. Packages start at $319 for one focused feature, $779 for several screens and $1,549 for an extension with accounts, and each choice adds a listed price.

Our chrome extension development with ChatGPT stopped working: can you repair it?

Usually, yes. AI drafts often carry habits from older extension styles, such as inline scripts, a background page where Manifest V3 expects a service worker, or state kept in variables that vanish when the worker sleeps. We read the draft, keep what is sound, rewrite what is not and tell you which parts were replaced. Send the code and the error shown on the extensions page.

Which chrome extension development documentation do you follow, and do I get my own?

We work from Google’s official extension documentation for Manifest V3, permissions, content scripts and the Chrome Web Store review process, because policy and API details change. You receive build notes for your own project, a permission explanation for each manifest entry and test notes you can repeat.

Do you follow a chrome extension development guide for Web Store review?

We follow the public review documentation. It says reviews are often finished within a few days but can take weeks, and that broad host permissions, sensitive permissions, new developers and large or hard-to-read code can slow them. So we request the narrowest access that works, avoid obfuscation and write reviewer notes in advance. No one can promise approval or a date.

Which chrome extension development framework do you use, and can I choose?

You can choose. WXT, Plasmo and CRXJS are the usual Vite-based options, and plain TypeScript with a bundler is often better for a small tool. We recommend one after reading your brief, based on the interface you need and who will maintain it, and we avoid locking you into a tool you do not want.

Will I get a chrome extension development hot reload setup to keep working on it?

Yes. The build notes explain how to install dependencies and start a dev build that rebuilds as you save, and how to produce the release zip. The exact reload behaviour depends on the framework we choose, and we say which one in the notes.

How long does Chrome Web Store review take after you finish?

Google’s documentation says most extensions are reviewed within a few days, with some taking up to a few weeks, and that a review pending beyond three weeks can be taken to developer support. Updates go through the same review as new items, so we leave room for it in any launch date.

Can you move my Manifest V2 extension to Manifest V3?

Yes, and it is the kind of job where the scope depends on the code. The platform change replaces the background page with a service worker, removes remotely hosted code and deprecates blocking webRequest in favour of declarativeNetRequest. Send the extension and we will confirm which package fits.

Do I get the code, and who owns the store listing?

You receive the TypeScript source and the packaged build. Publishing needs a Chrome Web Store developer account, and we recommend it is yours so the listing stays under your control. Ownership and revision terms are written into your quote before work starts.

Ready when you are

Get your chrome extension development services quote

Tell us what the extension should do and which pages it runs on. We reply with a fixed price, and nothing starts until you agree to it.

Care plan: a maintenance plan for Chrome and site changes is available and quoted separately once we have seen the extension.

Request your quote