Does this upload my manifest anywhere?

No. The check runs in the page itself, so the manifest never leaves the browser.

Does a clean result mean my extension will be approved?

No. The tool reads the manifest only. It cannot see what the code does, and approval is Google's decision. A clean result means the manifest gives a reviewer fewer things to question.

No. Broad host access is allowed when the feature genuinely needs any site, but it needs a justification naming that feature. If only a few domains matter, list them, or use activeTab when the extension acts after a click.

Why does it flag a path in a host permission?

Chrome ignores the path portion of a host permission, so a pattern like https://example.com/only/this/page* grants the whole domain. Narrowing happens at the domain level.

Free Chrome Extension Manifest Pre-Check

What this checks

The rules behind the check

Each finding below maps to something a reviewer can act on. The tool reads only the manifest, so it cannot see what your code actually does — a clean result means the manifest gives a reviewer fewer questions, not that the extension will be approved.

Manifest version — MV2 submissions are no longer accepted for new extensions.
Host access breadth — <all_urls> and wildcard patterns are permitted when the feature needs them, but they need a justification that names the feature.
Wording for each permission — see How to write permission justifications for what to put in the justification field.
Sensitive permissions — history, cookies, downloads, debugger, webRequest, management, proxy and privacy all need an obvious matching feature.
Permissions with no visible surface — a permission with no content script, action or background usage behind it reads as over-collection.
Remote code signals — external script origins in the CSP, and remote URLs in web_accessible_resources.
Listing assets — a 128×128 icon and a description that reads as a sentence rather than a keyword list.

Deeper reading: the rejection reasons in full · privacy policy and Data Use · why reviews stall.

Want the fill-in version?

The Chrome Web Store Submission Kit turns each finding into text you can paste: permission justification lines, a Data Use worksheet, a privacy policy template, and a rejection decoder. 6-page PDF, one-time $19. It is ours — we wrote it and we are paid when you buy it. Everything on this site stays free either way.

Get the kit — $19

Not sure what to change?

Paste your manifest.json or the rejection email and we will tell you which parts are likely drawing scrutiny and what we would change. Free, no signup. It is our reading, not a ruling from Google.

Send it for a free triage The triage form is different from the tool above: what you paste there is sent to us.

Prefer to work through it yourself? The Chrome Web Store Submission Kit collects the permission justification lines, the Data Use worksheet, a privacy policy template and a rejection decoder into one document — one-time $19. It is ours; we are paid when you buy it. Everything on this site stays free either way.

Get the kit — $19