Quick summary
Where to hire Chrome extension developer talent: Upwork for one clear job, a vetted network such as Lemon.io, Arc or Toptal if you want candidates screened for you, an agency for a large build, or a development subscription if the extension is part of a SaaS product that keeps changing.
What it costs: Lemon.io averages $57 an hour for Chrome extension developers and Arc says $60 to $100 or more. Vendor guides put a simple extension at about $3,000 to $10,000 to build, and one with accounts, a backend and payments at $10,000 to $35,000.
What to check: that they build on Manifest V3, ask for the fewest permissions the extension needs, and publish under a Chrome Web Store account your company owns.
Hire Chrome Extension Developer at a Glance
| Where to hire | What it costs | How fast | Best for |
|---|---|---|---|
| Freelance marketplace (Upwork) | Each freelancer sets a rate; it varies widely | Days | One small, clear job, if someone can review the code |
| Vetted network (Lemon.io, Arc, Toptal) | Lemon.io averages $57 an hour; Arc says $60 to $100+; Toptal quotes per developer | Lemon.io 24 to 48 hours, Toptal under 24 hours to match, Arc about 72 hours | Skipping the first round of vetting |
| Agency | A fixed quote per project | Weeks, after scoping | A large build with several people at once |
| Development subscription | A flat monthly fee | Days | An extension that is part of a live SaaS product |
| Full-time employee | A median $135,980 a year for a US software developer, before benefits | Months | Years of full-time extension work ahead |
Before you hire, ask every candidate these three questions:
- Question 1, "What happens to our extension's data when Chrome shuts down the service worker?" In Manifest V3, the background part of an extension is a service worker, and Chrome stops it after 30 seconds of inactivity. Google's docs warn that "any global variables you set will be lost." A good answer is "we save it to storage", without looking it up.
- Question 2, "Which permissions will it ask for, and why each one?" Chrome Web Store policy says to request "the narrowest permissions necessary." Broad permissions scare users at install and slow down Google's review.
- Question 3, "Whose Chrome Web Store account will it be published under?" The answer should be yours. Whoever controls that account controls every update your users get automatically.
Then run a short paid trial on a real task, in a code repository your company owns.
Need a Chrome extension for your product?
A senior developer on subscription: $2,995 a month, as many requests as you like, each shipped within 2 business days, and your money back if the first 14 days don’t prove it.
In this article
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
This guide is for founders who need a Chrome extension built or fixed: usually a companion to a SaaS product (save something from any page into your app, show your app's data inside Gmail or a CRM), sometimes an extension that is the product. It is written in plain English for the person paying, not for developers.
What a Chrome Extension Developer Builds
A Chrome extension is a small program that runs inside the browser. Most are made of a few parts, and knowing the names makes it easier to brief a developer and judge their answers.
Popup and side panel
What the user clicks: a small window under the toolbar icon, or a panel that opens beside the page. This is where most of your product's look shows up.
Content scripts
Code that runs inside the web pages a user visits, to read something from the page (a LinkedIn profile, an email, a product price) or add a button to it.
Service worker
The background part that handles events, talks to your servers and keeps things in sync. In Manifest V3 it starts and stops on its own, which is the most common source of extension bugs.
Your backend
If users log in, pay or sync data, the extension talks to your web app's server. For a SaaS company, this is often most of the work, and it is the same work as any other feature.
That last point matters when you choose who to hire. An extension that only changes a page is a small, separate job. An extension that logs into your product and syncs data is a feature of your product, and whoever builds it needs to work in your main codebase too.
Where to Hire a Chrome Extension Developer
Freelance marketplaces: Upwork
Upwork has many developers who list Chrome extension work, at whatever rate each one sets, so prices range widely. You post the job, compare proposals and do the vetting yourself. It suits a small, clear job such as a page tweak or a one-off tool, as long as someone on your side can review the code. Our list of Upwork alternatives compares the other places to look.
Vetted networks: Lemon.io, Arc and Toptal
These networks screen developers before you meet them.
- Lemon.io says every Chrome extension developer passes a live interview with a senior engineer and that it accepts 1.2% of applicants. Its calculator puts them at an average of $57 an hour (typically $41 to $60), with profiles usually within 24 hours (its FAQ says 48) and a paid trial of up to 20 hours.
- Arc says its Chrome extension developers come from the top 2% of applicants and typically charge $60 to $100 or more an hour, with a match in about 72 hours.
- Toptal says fewer than 3% of applicants are accepted, the average match takes under 24 hours, and you can hire in about 48 hours, with a trial of up to two weeks. It does not publish rates. Our Toptal alternatives guide compares it with other networks.
You pay more per hour than on an open marketplace, in exchange for a shorter list of stronger candidates. You still manage the person.
Chrome extension development services: agencies
An agency scopes the extension, quotes a fixed price and builds it with a small team. It suits a large build where several people need to work at once, or a company that wants one vendor to own the whole thing. Expect a longer start (scoping comes first) and a higher price for the same work: Cadence, which sells developers, says agency prices for the same scope usually run 4x to 8x higher than engineer time alone.
A development subscription
A development subscription gives you a senior developer for a flat monthly fee: you send requests (build the extension, add a side panel, fix the login, publish the update) and they come back one at a time. It suits a SaaS founder whose extension is part of the product and will keep changing with it. Our guide to developer as a service explains how these work.
A full-time hire
A full-time developer makes sense only if there are years of full-time extension work ahead. The median US software developer earned $135,980 in May 2025, before benefits, and hiring takes months. Our guide on how to hire a software developer covers that route.
What It Costs to Hire a Chrome Extension Developer
Hourly rates only tell you part of the story. Two vendor guides published in 2026 give build costs by size, and they line up closely:
| Size of extension | Example | Cadence (May 2026) | MetaDesign Solutions (Sept 2026) |
|---|---|---|---|
| Simple | A popup and a script on the page, no backend | $3,000 to $8,000, 1 to 3 weeks | $3,000 to $10,000, 2 to 4 weeks |
| Medium | User accounts, a backend and payments, or a SaaS side panel with login | $10,000 to $25,000, 3 to 6 weeks | $10,000 to $35,000, 6 to 12 weeks |
| Complex | Several integrations, single sign-on, AI features, admin dashboards | $30,000 to $80,000+, 8 to 16 weeks | $35,000 to $80,000+, 12+ weeks |
Both are companies that sell development, and MetaDesign calls its figures "illustrative ranges, not benchmarks", so use them to sanity-check a quote, not as a price list.
Then add the running costs:
- Chrome Web Store registration: a one-time fee, $5 since Google introduced it, paid once per developer account.
- Upkeep: MetaDesign suggests budgeting 15% to 25% of the build cost each year, because Chrome changes and the sites your extension works on change too.
- Safari: publishing there needs an Apple Developer Program membership, $99 a year.
- Your backend: if the extension logs into your product, the server side is ongoing work on your main app.
For a SaaS founder, the medium tier is the common case. If you already have a developer working on your product, the extension is often cheaper as another feature of that work than as a separate project with a new person who has to learn your backend first. Our guide to developer hourly rates compares hourly, fixed and monthly pricing in more detail.
Browser Extension Development Services: Chrome, Edge, Firefox and Safari
Chrome is the browser to build for first. In the US it had 62.63% of desktop browsing in October 2026, according to Statcounter, ahead of Safari at 13.35%, Edge at 13% and Firefox at 5.82%. Most browser extension development services quote Chrome first and treat the others as add-ons.
Edge and Brave
Both are built on Chromium, the same engine as Chrome, so the same extension code usually runs with little or no change. Edge has its own Add-ons store to list it in.
Firefox
Firefox uses the same WebExtensions approach, with some differences. Mozilla signs every extension through its add-ons site, even one you distribute yourself, and does not allow obfuscated (deliberately scrambled) code.
Safari
Safari needs the extension wrapped inside a Mac or iPhone app using Apple's Xcode, which has a tool to convert an existing extension. Publishing needs an Apple Developer Program membership.
Ask a developer which browsers they have published to before, and to price each browser separately, so you can start with Chrome and add the rest when customers ask.
What to Check Before You Hire
Manifest V3, the only format Chrome runs now
Manifest V3 is the current set of rules for Chrome extensions. Google disabled extensions built on the older Manifest V2 for every Chrome user with Chrome 138 in July 2025, and removed the remaining Manifest V2 extensions from the Chrome Web Store on August 31, 2026. Two Manifest V3 rules catch out developers who learned on the old version:
- The background stops on its own. Chrome shuts down an extension's service worker after 30 seconds of inactivity, so anything kept only in memory disappears. The fix is to save it to storage.
- No code from the internet. Google's docs say "all of your extension's logic must be part of the extension package." An extension cannot download and run code from a server, so every change goes through a new release and a new review.
If you are inheriting an older extension, ask the candidate to look at the code first. One still on Manifest V2 needs a migration before anything else.
Permissions and Chrome Web Store review
Every permission an extension asks for appears to the user at install. Chrome Web Store policy asks for "the narrowest permissions necessary", a "single purpose that is narrow and easy to understand", and an accurate privacy policy for any extension that handles user data.
Permissions also set the pace of releases. Google says most extensions are reviewed within a few days, but it can take up to a few weeks, and that "reviews may take longer for extensions that request broad host permissions or sensitive execution permissions". New developer accounts, new extensions and big code changes get a closer look too. A developer who asks to read "all websites" when your extension only needs one site is making every future release slower.
Questions that show real Chrome extension experience
- "Show me an extension you published to the Chrome Web Store. What did it do, and what did you build yourself?"
- "Which permissions would ours need, and which could we avoid?" Listen for narrow site access instead of "all websites".
- "What happens when the service worker stops?" The answer should involve saving state to storage.
- "How will users log in, and where do our secret keys live?" Keys belong on your server, never inside the extension, where anyone can read them.
- "What would slow down our Web Store review, and how would you avoid a rejection?"
- "Which other browsers have you published to?" Ask for Edge, Firefox or Safari examples if you need them.
Who Owns the Chrome Web Store Account
This is the check founders skip most often, and it matters more than the hourly rate. Chrome updates extensions automatically, so whoever can publish to your listing can put new code on every user's browser.
The same goes for the code: it should live in a GitHub or GitLab repository your company owns from the first commit, so you can change developers without losing anything. Our guide to software development contracts covers putting ownership in writing.
How to Hire a Chrome Extension Developer, Step by Step
- 1
Write down the one job the extension does
One or two sentences: who uses it, on which websites, and what it saves them. Chrome's single-purpose rule makes this a requirement, not just good practice. Our guide on how to write software requirements has a template.
- 2
Decide whether it talks to your product
If users log in or sync data with your app, you are hiring for a product feature and the developer needs access to your backend. If not, it can be a separate small job.
- 3
Pick the route
A marketplace for a small separate job, a vetted network or agency for a larger standalone build, a subscription if the extension will keep changing with your product.
- 4
Ask the questions above and run a paid trial
A small real task, such as a working popup that reads one thing from a page, shows how they work faster than any interview.
- 5
Set up the accounts in your company's name
The Chrome Web Store developer account, the code repository and any backend hosting, before the first line of code.
- 6
Plan for review and upkeep
Leave a few days to a few weeks for the first Web Store review, and budget for updates every year.
Which Route Fits You?
Keep the job tightly defined and pay for a short trial first.
Get the price per browser and the permissions list in writing before you start.
One developer builds the extension and the backend it talks to, so nobody has to hand off between them.
How StackTie Fits
Browser extensions are one of the things we build, alongside web apps, integrations and the backend they need. StackTie is a development subscription for SaaS founders: you send requests (build a Chrome extension that saves leads into your app, add a side panel, connect it to your login, publish the update) on your own Trello board. We work them one at a time in the order you set, and each comes back within 2 business days as a pull request with a plain-English summary of what changed and why. Bigger builds like a whole extension are split into smaller requests and shipped in pieces. The code lives in your company's repository, the Web Store listing stays under your account, and everything we build belongs to you. One senior developer, Michael, leads every build. There is no contract, you can pause when the work is quiet, and there is a money-back guarantee. We do not build native iOS or Android apps, and we are not a whole team working in parallel. The flat monthly price and what is included are on the homepage.
