Chrome Manifest V2 Extensions Stopped Working: What Aug 31, 2026 Really Changes

If you have August 31, 2026 circled as the day your Amazon seller extensions die, move the circle. Manifest V2 extensions stopped running in Chrome in 2025: Chrome 138 (stable since June 24, 2025) had Manifest V2 disabled for every user on every channel by July 24, 2025, with no way to turn them back on, and Chrome 139, stable on August 5, 2025, removed Manifest V2 support from the browser entirely. What happens on August 31, 2026 is narrower and easier to miss: Google removes the remaining Manifest V2 extensions from the Chrome Web Store (data checked 2026-08-25, Chrome’s Manifest V2 support timeline ).

So the deadline is real, but it is not the deadline most sellers think it is. Nothing installed in your browser changes behaviour that day. What disappears is the evidence layer — the listing page, the reviews, the permissions disclosure, the last-updated date, and your ability to reinstall the thing at all. This guide separates the two events, then gives you a short audit that tells you exactly which state each tool in your stack is in.

Two Different Dates, Two Different Events

The confusion is understandable: “Manifest V2 is going away” has been a headline for four years running, and the phases blur together. Here is the separation that matters, quoted from Google’s own timeline page (data checked 2026-08-25).

Read the last column and the ordering does the work for you. Every row that changed how extensions behave sits in 2025. The 2026 row changes a catalogue.

One caveat worth stating plainly, because it is the only place the two events touch: the same 2026 entry adds that “Manifest V2 extensions installed on Chrome 138 or earlier will remain installed, but will be unable to receive any updates and cannot be reinstalled from the Chrome Web Store once removed from Chrome.” Remaining installed is not the same as remaining usable — on consumer Chrome 138 those entries are already switched off and cannot be switched back on. The row stays in your list. The tool does not come back.

Why Chrome Manifest V2 Extensions Stopped Working — in 2025, Not 2026

The mechanism is worth understanding, because it explains why no workaround exists.

Chrome did not delete Manifest V2 extensions from anyone’s browser. It stopped honouring them, in three steps. First a default-off state that users could override, from March 31, 2025. Then a default-off state with the override removed, at Chrome 138. Then the removal of the code path itself, in the Chrome 139 branch — Google’s timeline says support “will be removed from Chrome” starting with that branch, and Chrome 139 reached stable on August 5, 2025.

Enterprises got a short extension and it has also expired. The timeline states that “Chrome 138 is the final version of Chrome to support Manifest V2 extensions (when paired with the ExtensionManifestV2Availability key)” and that the policy itself was removed with Chrome 139. In practice that means a managed fleet could hold at Chrome 138 and keep an internal Manifest V2 tool alive; the moment those machines took the Chrome 139 update, the exception evaporated with the policy.

This is why “manifest v3 forced 2026” — a phrase you will see in a lot of forum threads — is a year off. The forcing happened in 2025. What is left for 2026 is bookkeeping.

If a seller tool in your stack quietly stopped appearing on Amazon product pages last summer and you filed it under “Amazon changed something again,” this is very likely what actually happened.

What Actually Disappears on August 31, 2026

Since nothing about your browser changes, it is worth being precise about what you lose. Four things, and three of them are records rather than software.

1. The reinstall path. This is the only operational loss. If a Manifest V2 tool is still sitting disabled in your extensions list and you remove it — or you set up a new laptop — there is no listing to install it from. The official wording is explicit: it “cannot be reinstalled from the Chrome Web Store once removed from Chrome.”

2. The update path. Already academic for a disabled extension, but it closes the door on a vendor shipping a last-minute Manifest V3 rewrite under the same listing after that date.

3. The permissions record. A store listing publishes what an extension was allowed to touch. For a tool that had access to your Seller Central session or your customer-facing listing pages, that disclosure is the document you would want if you ever needed to reconstruct what had access to what. After removal there is no canonical page to point at.

4. The review and update history. Ratings, review text and the last-updated date are how most sellers judged whether a free extension was maintained. A delisted tool leaves no trail — which also means that in twelve months you will have no way to check whether the abandoned downloader you used in 2024 was ever updated after its last known release.

None of this is dramatic. But if your process for vetting a browser tool is “check the store page,” that process gets a blind spot on September 1, 2026, and the blind spot is retroactive.

Your Amazon Extension Is Not Working in Chrome: A 15-Minute Audit

Here is the audit. It is short on purpose — you are classifying, not troubleshooting.

Step 1 — List what you actually have. Open chrome://extensions and read the full list, not the pinned toolbar icons. Most seller stacks accumulate five to fifteen extensions and the owner can name maybe six. Write down every item, including the ones you do not recognise.

Step 2 — Sort by enabled state, and note what you cannot re-enable. On current Chrome, a Manifest V2 extension appears switched off and stays switched off; the official timeline is unambiguous that from Chrome 138 “users can no longer turn them back on.” So the toggle is your primary signal. Anything you can flip on and off freely is running under Manifest V3.

Step 3 — Open each listing while listings still exist. For every extension you still care about, visit its Chrome Web Store page and check the last updated date. A tool actively maintained through 2025 was necessarily migrated — it could not have survived Chrome 138 otherwise. A tool whose last update predates mid-2024 and which is now disabled is a Manifest V2 casualty, and its listing has a shelf life measured in days.

Step 4 — Separate manifest deaths from page-structure deaths. This is the step that saves the most time. If an extension is enabled but does nothing on an Amazon product page, Manifest V2 is not your problem — Amazon changed its page markup and the extension’s selectors no longer match. Different diagnosis, different fix, and usually a vendor update rather than a replacement.

Step 5 — Screenshot before you clean up. For any Manifest V2 item you are about to remove, capture the listing’s permissions section and last-updated date first. That is thirty seconds of work for the only copy of that record you will ever have.

Step 6 — Then, and only then, uninstall. A disabled Manifest V2 extension is inert, so there is no urgency; but leaving eight dead entries in the list is how the next audit becomes confusing.

Reading the Result: Four States Your Stack Can Be In

The third row is the one that gets misdiagnosed most often, and it is worth repeating because the deadline noise pushes people toward the wrong conclusion: an enabled extension that fails on Amazon is not a manifest problem.

Replacing a Dead Extension Without Losing the Workflow

If the audit turns up a genuine Manifest V2 casualty, the replacement question is not “what does the same thing?” but “what does the same thing and is still being maintained?” Two filters do most of the work.

Filter one: recent updates. Any extension with a 2025 or 2026 update date has, by definition, cleared the Manifest V3 bar. That single fact tells you more about a vendor than the feature list does — migration was substantial work, and the tools that got abandoned instead were the ones nobody was paying to maintain.

Filter two: permission narrowness. Manifest V3 changed how extensions request host access, and a well-built one asks for the pages it needs rather than every site you visit. For an Amazon-specific tool, “runs on Amazon product pages” is the expected shape. Anything asking for broad access to all sites deserves a reason.

For the media side of a seller workflow — pulling competitor gallery images, A+ modules and product video for research — ASINCrate is one of the tools that ships on Manifest V3, and its published scope is limited to Amazon product detail pages rather than blanket site access. It is worth being accurate about what the free tiers include, because this is where marketing usually blurs: without an account you get single-image downloads, URL copying and variant browsing; a free account adds a small monthly allowance of video downloads and settings sync. Bulk ZIP export, CSV metadata export and batch URL copy are Pro features, not free ones (per the published pricing page, data checked 2026-08-25). If your dead Manifest V2 tool did bulk work, plan for that.

The broader point is workflow continuity rather than any single tool. A competitor image analysis routine that depended on an extension which no longer loads is worth rebuilding deliberately — same outputs, documented inputs — instead of replacing one fragile dependency with another. The audit in the previous section usually surfaces a second finding along the way: tools nobody remembered installing, still sitting in the list with whatever access they were granted years ago.

Frequently Asked Questions

Did my Chrome extension stop working because of the August 31, 2026 deadline?

No. Chrome disabled Manifest V2 extensions for every user on every channel with Chrome 138 (stable since June 24, 2025), with that shutdown fully in effect by July 24, 2025, and the official timeline states that from that point users can no longer turn them back on. Support was then removed from the browser in the Chrome 139 branch, stable on August 5, 2025. If an extension went dark, that happened in 2025. August 31, 2026 is a Chrome Web Store event, not a browser event.

What exactly happens on August 31, 2026?

Google’s Manifest V2 support timeline states verbatim: “All remaining Manifest V2 extensions are removed from the Chrome Web Store. Manifest V2 extensions installed on Chrome 138 or earlier will remain installed, but will be unable to receive any updates and cannot be reinstalled from the Chrome Web Store once removed from Chrome.” Nothing about your browser’s behaviour changes that day — the store listing, its update path and its reinstall button are what disappear (data checked 2026-08-25).

Is there any way to keep running a Manifest V2 extension?

Not on a normal Chrome install. The only exception was an enterprise policy, ExtensionManifestV2Availability, and Google’s timeline says Chrome 138 is the final version of Chrome to support Manifest V2 extensions when paired with that key, and that the policy is removed with Chrome 139. There is no consumer toggle left, and no flag that brings one back.

How do I tell whether my Amazon extension is Manifest V2 or Manifest V3?

The fastest practical test on a current Chrome: open chrome://extensions and see whether the extension is switched off with no way to switch it back on. That state is what Chrome 138 onwards produces for Manifest V2. A second check is the extension’s Chrome Web Store listing — an item last updated before mid-2024 and never touched since is almost certainly still on Manifest V2, and after August 31, 2026 a missing listing is itself the answer.

My Amazon extension is not working in Chrome. Is Manifest V2 always the reason?

No, and assuming so wastes an afternoon. Amazon changes its own page markup frequently, and a Manifest V3 extension that relied on a selector Amazon renamed will fail on the listing page while remaining perfectly enabled in chrome://extensions. Check the extension’s enabled state first: still enabled means the cause is the extension’s own code or Amazon’s page, not the manifest deadline.

Should I keep a copy of a Manifest V2 extension before its listing disappears?

A saved copy will not run — current Chrome does not load Manifest V2 regardless of where the files come from. What is worth saving before August 31, 2026 is the evidence around it: the listing’s permission disclosure, its last-updated date and its review history, which are the records you would need if you ever had to explain what a tool had access to.

The One-Line Summary

Your Manifest V2 extensions stopped working in 2025, at Chrome 138 and 139. On August 31, 2026 their store listings disappear, taking the reinstall button and the paper trail with them. Spend fifteen minutes in chrome://extensions this week, screenshot what you are about to lose, and make sure every tool you still depend on has an update date in the last twelve months.