Custom apps & software
Migrate Your Chrome Extension From Manifest V2 to V3
Chrome 139 and later no longer run Manifest V2 extensions — we convert yours to V3 without breaking what it already does.
Delivered in 5-7 working days
Fixed price · one-time · no hidden charges
or
Ask on WhatsApp before you buyA real person replies — usually within minutes during the day (IST).
How it works
- Pay ₹9,499Secure Razorpay checkout. Share your extension's source code and Chrome Web Store access.
- Migrated and testedmanifest.json, service worker and permissions updated; every existing feature re-tested.
- SubmittedUpdated build submitted to your Chrome Web Store account, in 5-7 working days.
The short answer
ZoopCoder migrates one existing Chrome extension from Manifest V2 to Manifest V3 for a fixed ₹9,499, delivered in 5-7 working days. Chrome 138 was the last version to run Manifest V2 extensions and they cease to function from Chrome 139, so an unmigrated extension is already dead for its own users; the real work is that Chrome stops a V3 service worker after 30 seconds of inactivity (and after any single request that runs past 5 minutes), so everything the old persistent background page kept in global variables must be rewritten to survive being stopped, and any blocking webRequest calls must become declarativeNetRequest rules — those two changes break most real extensions, not the manifest.json version number.
What you get
- manifest.json upgraded from V2 to V3 syntax
- Persistent background page converted to an event-driven service worker
- Blocking webRequest rules replaced with declarativeNetRequest where required
- Content scripts and permissions audited against V3's stricter host-permission model
- Testing of existing features to confirm nothing broke in the migration
- Updated build submitted to your Chrome Web Store developer account
| Price | ₹9,499 (fixed) |
|---|---|
| Source extension | 1 existing Chrome extension (Manifest V2 source code required) |
| Scope | manifest.json, service worker conversion, permissions audit |
| Store | Submitted to your own Chrome Web Store developer account |
| New features | Not included — this preserves existing behaviour |
| Other browsers | Not included — quoted separately, see our Firefox & Safari port service |
| Turnaround | 5-7 working days |
What we need from you
- The existing extension's source code (Manifest V2)
- Your Chrome Web Store developer account access to submit the updated build
- A list of the extension's features so we can confirm each still works after migration
Not included
- Chrome Web Store's review of the updated submission, which is Google's decision
- New features beyond what the extension already does
- Porting to Firefox or Safari — see Chrome Extension Port to Firefox & Safari, ₹9,999
- Extensions relying on remotely hosted code or a persistent background page Chrome will not support under any manifest version — flagged upfront if found
About this service
Manifest V3 is not a cosmetic version bump: Chrome has been actively disabling Manifest V2 extensions since 2024 and the Chrome Web Store stopped accepting new V2 listings, so an extension left on V2 eventually just stops loading for its users. The two changes that actually break a naive migration are the background page — V2's persistent page has to become an event-driven service worker that Chrome can start and stop at will, so any code assuming it stays alive needs rework — and blocking webRequest, which V3 replaces with the more limited declarativeNetRequest API for most ad-blocking and request-modification use cases. We do that conversion, audit the permissions V3 enforces more strictly, and re-test every existing feature before handing back a build ready to submit. If your extension genuinely depends on something V3 cannot support at all, we tell you that plainly before charging anything further.
Questions before you buy
Why does my extension need this if it already works?
If it still loads for you it is an exception, not the rule: Chrome 138 was the last version to run Manifest V2 extensions and they cease to function from Chrome 139. An unmigrated extension stops working for its own users even with no code changes on your end.
Will this change how my extension looks or behaves?
No — the goal is identical behaviour on Manifest V3. We test every existing feature after migration specifically to catch anything the conversion might have changed.
What if my extension uses blocking webRequest for ad-blocking or filtering?
That is one of the two changes this service handles — we replace it with declarativeNetRequest, V3's supported approach, which covers most but not all blocking use cases; we flag upfront if yours is an exception.
Do you also publish it to Firefox or Safari?
Not in this service — that is a separate scope with its own manifest and API differences. See our Chrome Extension Port to Firefox & Safari service, ₹9,999.
Is approval on the Chrome Web Store guaranteed?
No — Google reviews every submission independently. We submit a complete, tested build to give it the best chance.
Why does my migrated extension forget its data after a few seconds idle?
Because a Manifest V3 service worker is not a persistent page: per Chrome's own documentation it is terminated after 30 seconds of inactivity, when one request takes longer than 5 minutes, or when a fetch() response takes more than 30 seconds to arrive. Anything stored in global variables is lost on each restart, so state has to move to chrome.storage or be rebuilt on wake-up — this is the part of the migration that is rewritten, not just renamed.
Can my extension still load JavaScript from my own server or a CDN?
No. Manifest V3 requires all of an extension's logic to ship inside the package; Chrome Web Store policy no longer allows loading and executing remotely hosted files. If your extension relies on that, we flag it before charging anything further — bundling the code locally or using a sandboxed iframe are the supported routes.
Often ordered with this
About ZoopCoder · Terms · Privacy
© 2026 ZoopCoder