Marketplace›Web and tech›Software and apps›Chrome extension fix or Manifest V3 migration
Chrome extension fix or Manifest V3 migration

Chrome extension fix or Manifest V3 migration

Software and apps · delivered in 2-10 days

What is included

  • Starter - $50.99, delivered in 2 days: one reproducible fault found, corrected and explained, source handed back in your own repository, bug investigation, a fix write-up and 1 revision.
  • Standard - $125.99, delivered in 4 days: up to 3 faults resolved, or a single-screen extension carried over to Manifest V3, with a summary, investigation notes, detailed code comments and 2 revisions.
  • Advanced - $275.99, delivered in 10 days: migration of up to 5 screens to Manifest V3, a written summary, any further issues spotted along the way listed out, plus investigation, detailed code comments and 3 revisions.

What you provide

  • The domain the order relates to
  • Your brief describing the problem or goal

This service suits businesses and independent developers whose extension already has an active user base. The rebuilt version stays as close as possible to the original, changed only where the repair or the Manifest V3 move genuinely demands it, so day-to-day users barely notice the difference.

Share the source code or the store listing along with a description of the fault. In return you receive a build you can load into developer mode and test yourself, a plain-language explanation of what went wrong, and the source code delivered into your own repository.

The Starter tier covers one reproducible fault, such as an empty popup, a permissions error, or a content script that no longer matches its target page. The Standard tier handles up to 3 such faults, or carries a single-screen extension across to Manifest V3. The Advanced tier migrates an extension spanning up to 5 screens and notes any other issues discovered during the work. A second, unrelated fault counts as a separate item, either an add-on or a new order.

Building extensions from scratch is handled elsewhere; this service starts from code that already exists.

Work that is declined, and flagged before any project begins, includes anything requiring someone else's login credentials, anything that collects personal data, or anything that operates a service outside its own terms.

Communication stays in writing throughout, including the explanation of what was actually broken.

How the work proceeds

  1. Reproduce or unpack - your extension is loaded in developer mode and the fault reproduced from your description, or the published build is unpacked if no source remains. If the issue cannot be reproduced, you are told the same day.
  2. Cause explained in writing - the actual trigger, whether a changed Chrome API, altered page markup, or a Manifest V2 feature the store no longer permits, set out in plain terms before any fix begins.
  3. Repair or migration - the fault is corrected, or the Manifest V3 changes are made: background pages become service workers, blocking request handling becomes declarative rules, and remote code is brought in-house. Each change comes with its reasoning.
  4. Testing and handover build - the corrected version is tested on a clean profile, then passed to you to load in developer mode and check on your own machine before approval.
  5. Delivery into your repository - source code lands in your own repository, the written summary is included on Standard and Advanced orders, and you are told exactly what needs uploading to the store using your own developer account.

What happens after you buy

Your order opens its own thread here the moment it is paid, and everything about that order - questions, changes and the final report - happens in it.

Questions people ask

My extension stopped working after a Chrome update. Is that this project?

Yes, this is the most common trigger for these requests. Send over the extension and describe what you are seeing now, and you will get the cause and the right tier confirmed before you commit to buying.

What is Manifest V3, and why is it a tier rather than a fix?

It is a genuine rebuild rather than a label change. The background page turns into a service worker that stops and restarts, blocking-style request handling is replaced by declarative rules, and code can no longer be pulled in from a remote server. Anything relying on those older mechanisms gets rewritten rather than patched.

I only have the store link, not the source. Can you still work?

In most cases yes, a published extension can be unpacked from its store build. If the result turns out minified or obfuscated, you are told before purchase, along with an honest view on whether repairing it makes more sense than rebuilding from scratch.

Will my extension stay published while you work?

Your live listing is untouched throughout. All work happens on a separate copy loaded in developer mode, and the finished build only goes live once you upload it yourself through your own developer account.

People also buy

Software and apps

Backend development services

Backend development covering secure REST APIs, database integration, authentication and testing, built with Express.js and MongoDB, delivered in 5 days for $25.99.

$25.99PER ORDER 5 days
Software and apps

Chrome extension development in JavaScript or TypeScript

Custom Chrome extension built in JavaScript or TypeScript on Manifest V3, with tiers covering 1 to 5 screens, optional Firefox and Edge support, and source code delivered to your own repository.

$62.99 - $375.99PACKAGES FROM 4-14 days
Software and apps

Custom e-commerce automation, AI chatbots, and software

We build custom Shopify apps, AI-powered chatbots, workflow automation and analytics tools that bring your scattered business systems into one place, drawing on more than 10 years of full-stack eCommerce engineering.

$36.99 - $748.99PACKAGES FROM 3-14 days