Submission Readiness Checker
Validate the most common Chrome Web Store submission problems before you hit publish. Paste a manifest or upload your extension ZIP, then check icons, screenshots, privacy policy readiness, and permission review notes in one pass.
Input
ZIP upload unlocks file existence and icon dimension checks. Manifest-only mode still validates the submission checklist.
Submission status
Passes, warnings, and blockers update live as you edit.
Pass
4
Warn
2
Fail
5
Ready to submit?
You still have 5 blocking issues to fix before publishing.
What this checks
- Required manifest fields like name, version, description, and MV3 setup.
- Declared icon sizes and, in ZIP mode, whether the files actually exist.
- Icon dimension mismatches between the manifest and packaged images.
- At least one screenshot, privacy policy readiness, and permission notes.
- Permission-warning risk using the same logic as the Permission Preview tool.
Checklist results
Failures are likely blockers. Warnings are the things that often trigger slower review, rejection churn, or lower conversion after approval.
Manifest version
Manifest V3 detected.
Extension name
Name found: "Page Notes".
Extension version
Version found: 1.0.0.
Description present
Chrome rejects listings with a blank description field.
Fix: Add a user-facing description in the manifest and matching store listing copy.
Required icon sizes declared
Missing declared icon sizes: 16, 48, 128.
Fix: Declare at least 16x16, 48x48, and 128x128 icons under the `icons` key.
Packaged icon files
Upload the extension ZIP to confirm icon files exist and match the declared dimensions.
Fix: Use ZIP mode if you want file-level checks instead of manifest-only validation.
Store screenshots
1 screenshot recorded. Chrome requires at least 1 and allows up to 5.
Fix: Consider filling all 5 screenshot slots to improve conversion.
Privacy policy URL
This manifest requests permissions that often require a privacy policy in the Chrome Web Store.
Fix: Add a public privacy policy URL before submission.
Permission justifications prepared
Requested permissions should have specific justifications ready for the review form and listing.
Fix: Write one sentence per permission explaining exactly why the extension needs it.
Permission risk level
3 install warnings detected.
Fix: Reduce broad access where possible, or move non-essential access into optional permissions.
MV3 background setup
No MV3 background service worker found. This may be fine if the extension does not need one.
Fix: If your extension needs background logic, declare it under `background.service_worker`.
Limits of this checker
It cannot inspect your Chrome Web Store dashboard fields directly, so it uses the screenshot count, privacy policy URL, and permission notes you provide here as readiness signals.
Next step
Once the checklist is green, verify how scary your install warnings look and audit your listing copy before submission.