Browser extensions

Manifest V3

The current architecture standard every new Chrome extension is built on — and the specific things it changed from the previous version.

What it is

Manifest V3 is the current extension platform specification for Google Chrome (and, by extension, other Chromium-based browsers like Edge and Brave). Every Chrome extension declares a manifest.json file describing what it does and what permissions it needs; "V3" refers to the third major version of the rules governing what that file — and the extension's code — is allowed to do.

What changed from Manifest V2

  • Service worker instead of a persistent background page — V2 extensions could keep a background page running continuously, consuming memory even when idle. V3 extensions use an event-driven service worker that Chrome can start and stop as needed, which is significantly lighter on system resources.
  • No remote code execution — V3 extensions must ship all their JavaScript inside the extension package itself. Fetching and executing code from a remote server at runtime, allowed under V2, is no longer permitted — a meaningful security improvement, since it closes off a path malicious extensions previously used to inject harmful code after review.
  • Declarative content-blocking — extensions that block or modify network requests (like ad blockers) now largely use a declarative rules API instead of intercepting every request in real time, which is faster but somewhat less flexible than the old approach.
  • Narrower, more specific permissions — V3 pushes extensions toward requesting the minimum permissions needed for what they actually do, rather than broad access requested up front.

Why it matters as a user

In practice, Manifest V3 extensions tend to use less memory, have less impact on browser performance, and carry a smaller attack surface for malicious code than their V2 predecessors — the trade-off is that some categories of extension (particularly complex ad and content blockers) lost some of the flexibility the old blocking APIs gave them.

How Transform Case uses it

The Transform Case browser extension is built on Manifest V3 from the ground up — a lightweight background service worker handles the right-click menu and keyboard shortcuts, and the conversion engine itself ships entirely inside the extension package, with no remote code fetched at runtime. See the extension FAQ for the specific permissions it requests and why.

Source

Chrome for Developers — What is Manifest V3? — the official Chrome extensions documentation.

Related

Chrome Extension Context Menu Permissions

Back to the full glossary — 200 terms covering case conversion, style guides, and text tools.