Chrome extension development
Chrome Extension Developer — Manifest V3 Extensions Built to Ship
I build Chrome extensions from an empty folder to a Web Store listing — Manifest V3, side panels, keyboard shortcuts, content scripts, background service workers and synced settings. TabPilot AI, a keyboard-first tab controller, is my own extension, so the workflow below is one I run on my own products as well as client work.
What you get
Workflow automation extensions
Extensions that remove a repetitive task from your team's day — bulk actions, auto-fill, scraping into a spreadsheet, one-key shortcuts.
Side panel & popup tools
Chrome's side panel API and popup UI built in React, with synced settings so a user's setup follows them across devices.
Content scripts & page overlays
Injecting new controls into a site you use daily, without breaking its own scripts or styling.
Migration from Manifest V2
Porting a legacy extension to Manifest V3 — service workers, new permissions model, and getting it approved again.
Web Store submission
Icons, screenshots, privacy disclosures and the listing copy, so review passes the first time instead of the third.
How it works
- 01
Scope the surface
We agree exactly which pages the extension touches and which permissions it needs — smaller permission sets pass review faster.
- 02
Build with a loadable dev build
You get an unpacked build to load in your own Chrome from week one, so you're testing the real thing throughout.
- 03
Package and submit
I produce the store assets, submit for review, and stay on hand for review feedback.
Frequently asked questions
How much does it cost to build a Chrome extension?
I quote per project, not per hour. A single-purpose extension with a popup is at the lower end; something with a side panel, an account system and a sync backend costs more. Send the scope and you get a fixed price and a delivery date the same day.
Do you handle Chrome Web Store submission?
Yes. I prepare the icons, screenshots, description and privacy disclosures, submit the extension for review, and handle any review feedback until it is published.
Can you migrate my Manifest V2 extension to V3?
Yes. Manifest V3 replaces background pages with service workers and changes how permissions and remote code work. I port the extension, rework anything that relied on V2-only behaviour, and resubmit it.
How long does a Chrome extension take?
A focused tool is usually one to two weeks. An extension with accounts, sync and a side panel UI is typically three to five weeks, plus Web Store review time.