About Chrome Extension Tools

What Chrome Extension Tools is, who it is for, and what it deliberately does not do. An independent project for people who work with Chrome extension packages.

What this is

Chrome Extension Tools is a set of small, single-purpose web pages for working with Chrome extension packages: downloading them, unpacking them, reading their manifests, checking them against Manifest V3 rules, and understanding what their permissions actually allow.

Each tool does one thing and does it in the browser. There is no account to create, nothing to install, and no backend to trust with your files.

Who it is for

Two groups, for different reasons.

If you use extensions, you sometimes want to know what one declares before you trust it with your browsing. TheManifest Viewer andPermission Checker answer that in plain language, and the CRX to ZIP converter gets the package open so you can look for yourself.

If you build extensions, theManifest V3 Validator catches the configuration mistakes that produce confusing load failures, and the downloader is useful when you need a specific published version of another extension to test against.

What it deliberately does not do

  • No accounts, no database, no CMS. Every page is a static file. There is nothing to sign in to because there is no user data model.
  • No file uploads. The tools that accept files process them with the browser File API. There is no upload endpoint to send them to.
  • No analytics and no advertising yet. Nothing you type is measured, recorded, or profiled.
  • No reputation claims. This site will not tell you an extension is safe or unsafe, because a manifest cannot tell you that. It explains what is declared and lets you decide.
  • No affiliation with Google. This is an independent project. It is not affiliated with, sponsored by, or endorsed by Google, and nothing here is "Google-approved" or "Chrome-certified".

How it is built

Astro, with static HTML output and TypeScript for the parts that run in your browser. The site is deployed to Cloudflare Pages as static files. There is no server-side rendering, no Cloudflare Worker, and no API — which is what makes the privacy claims simple to keep honest.

Tool logic is only loaded on the page that uses it. The homepage ships almost no JavaScript at all.

Corrections

If something here is wrong, out of date, or describes Chrome behaviour that has since changed, say so through the contact page. Chrome's extension platform moves, and a tool that quietly gives outdated advice is worse than no tool.