---
title: "I Will fix your Chrome extension or move it to Manifest V3"
url: https://zinnhub.com/zinns/i-will-fix-your-chrome-extension-or-move-it-to-manifest-v3/
description: "Your extension worked last month and it doesn't now. Chrome shipped an update, the site underneath changed its markup, or it still runs on Manifest V2 and the store won't take it any more. I repair those, in JavaScript and TypeScript."
published: 2026-09-29T11:47:27+00:00
modified: 2026-09-30T08:14:01+00:00
language: en-GB
---

# I Will fix your Chrome extension or move it to Manifest V3

Aimed at companies and solo developers whose extension already has users counting on it. You get the same extension back, changed only where the fix or Manifest V3 requires it, so those users notice as little change as possible.

Send me the source or the store link and what goes wrong. You get back a build you load in developer mode and click through yourself, the cause written out in plain words, and the source in your own repository.

Starter is one reproducible problem: a popup that opens empty, a permission error, a content script that no longer matches the page. Standard takes up to 3 of those, or moves a single-screen extension to Manifest V3. Advanced migrates an extension of up to 5 screens and lists the other problems I found on the way. A second broken thing is a second item: the add-on, or a new order.

Building a new extension is my other project. This one starts from code that already exists.

What I turn down, and I say it before the project rather than after: anything that needs someone else’s login, harvests personal data, or works a service against its own rules.

No calls. Everything in writing, including what was actually broken.

Steps for completing your project
1. Reproduce it, or unpack it – I load your extension in developer mode and reproduce the problem from your steps, or unpack the store build if the source is gone. If it does not reproduce, you hear it the same day.
2. The cause, in writing – What actually broke: a Chrome API that changed, a page whose markup moved, a Manifest V2 feature the store no longer accepts. Plain words, before the fix.
3. Fix, or migrate – The fix, or the Manifest V3 move: background page to service worker, request blocking to declarative rules, remote code brought inside. Each change with its reason.
4. Clean-profile test and a build for you – The fixed build tested on a clean profile, then handed to you to load in developer mode and click through on your own machine before you approve.
5. Handover in your repository – Source in your repository, the written summary on Standard and Advanced, and a note on what to upload to the store from your own account.