I will build a custom chrome extension for your team, manifest v3


About this gig
A Manifest V3 Chrome extension for your team, living where they already work: the browser.
I've shipped 60+ releases of a Chrome extension used daily by sales teams: uploads, page capture with automatic pagination, screenshot OCR, and a compose tool that talks to a backend API. Yours gets the same build discipline: Manifest V3, least-privilege permissions, tests, and a handover your developer can maintain.
What you send
- What the tool should do, in plain words, and on which sites
- Your API, if it needs to save or fetch anything
- Who uses it: your team (unpacked install) or the public (Web Store)
What you get
- Full source, MV3, no unnecessary permissions
- Popup, content scripts, options page, background sync or browser automation as needed
- Two builds if you need them (production and local test)
- Install guide for your team, or a complete Web Store submission package
- Tests for the logic and a manual checklist for the UI
Ground rules: no scraping behind logins the user does not own, no data collection beyond what the listing states, no permissions the tool does not need. Message me with what it should do before ordering and I'll confirm feasibility and the package.
Get to know Carter DuBois
Junior Data Architect
- FromUnited States
- Member sinceSep 2026
- Avg. response time3 hours
Languages
English, Spanish
My Portfolio
Other Software Development Services I Offer
FAQ
Do I own the code?
Yes. Full source is delivered in your GitHub or as a zip, with no license restrictions and no dependency on me. The handover includes a walkthrough so your developer can maintain it.
Can it connect to my existing system?
Yes. Standard and Premium include calls to your API with authentication. I need the API docs or an example call; I never store your users' data anywhere except where you tell me to.
Will you publish it on the Chrome Web Store?
Premium includes the full submission package: icons, screenshots, promo tile, listing text, privacy policy and the review answers. Publishing happens from your developer account so you keep control of it.
Which permissions will it need?
Only what the feature requires, listed and justified before I build. Broad host permissions are avoided; sites are named explicitly or requested at runtime when the user chooses.
Can it work on any website?
Anything the user can open in their browser and is allowed to use. I don't build tools to bypass logins, paywalls or a site's terms.

