Chrome Web Store Listing Requirements

Everything Google requires for your Chrome extension listing — text limits, image specs, privacy, and policies. Last updated 2026.

Last updated April 2026

Text Requirements

Extension NameMax 75 charactersNo keyword stuffing
Short DescriptionMax 132 charactersShows in search results
Detailed DescriptionMax 16,384 characters
Category1 requiredChoose the most relevant
Language1 primary requiredLocalize for more reach

Tip: The short description is the most important SEO field. Include your primary keyword naturally. Avoid ALL CAPS, excessive punctuation, or unsubstantiated claims.

Image Requirements

AssetSizeFormatStatus
Store Icon128×128PNGRequired
Management Icon48×48PNGRequired
Toolbar Icon16×16PNGRequired
Screenshot1280×800 or 640×400PNG/JPEGAt least 1
Small Promo440×280PNG/JPEGOptional
Large Promo920×680PNG/JPEGOptional
Marquee Promo1400×560PNG/JPEGOptional

See the complete image size guide for detailed specifications and best practices for each asset type.

Privacy & Data Disclosures

Privacy Policy URL

Required if your extension collects any user data. Must be a publicly accessible URL.

Data Use Disclosures

Declare what data you collect, why, and whether you sell or share it. Found in the Privacy tab of the developer dashboard.

Permission Justifications

Explain why each requested permission is necessary. Vague or missing justifications are the #1 cause of review rejections.

Single Purpose

Your extension must have one clearly stated purpose. Multi-purpose extensions are rejected.

Common Rejection Reasons

Excessive permissions

Fix: Only request what you need. Remove unused permissions from manifest.json.

Missing or vague permission justifications

Fix: Write a specific sentence for each permission explaining how your extension uses it.

Remotely hosted code

Fix: Bundle all JavaScript in the extension package. No eval(), no CDN scripts.

Misleading metadata

Fix: Your name, description, and screenshots must accurately represent functionality.

Missing privacy policy

Fix: Add a privacy policy URL if you request host permissions or collect any data.

Not single purpose

Fix: Each extension should do one thing well. Split multi-purpose tools into separate extensions.

Use our interactive publish checklist to verify everything before you submit.

Create Store Assets with CWS Kit