Launch & distribution
Chrome Web Store listing checklist
What to prepare before submitting a Chrome extension: assets, permissions justification, privacy disclosures and what to expect from review.
- By
- LaunchFaro editorial
- Published
- Review
- Not yet reviewed by a named editor
- Next review
- 1 min read
Checklist
Step 1
Prepare the store assets first: a 128px icon, at least one 1280×800 screenshot, and a short description under 132 characters that states what the extension does, not how great it is.
Step 2
Justify every permission. Reviewers check that each permission is necessary, and broad host permissions can lengthen review. Request the narrowest access that works, and use activeTab where it is enough.
Step 3
Write the privacy disclosure honestly. If you collect anything, say so in the dashboard's privacy practices section and link a privacy policy on a domain you control.
Step 4
Chrome's documentation says most extensions are reviewed within a few days but some take up to a few weeks; contact support if a submission is still pending after three weeks. Keep a changelog in the listing so updates are easier to review.
Step 5
After publishing, claim the listing on discovery platforms like this one and keep the store identifier stable; renaming the extension does not change it, and that identifier is what users and directories link to.
