Launch guideBrowser and IDE extensions

How to launch a Chrome extension

A Chrome extension launch starts with a review queue you don't control. Google says most reviews finish within a few days but can take weeks, and new developers or broad permissions take longer. So submit well before your public launch date, keep permissions narrow, and use the wait to build a landing page, because the Web Store listing alone rarely ranks for anything beyond your name.

Updated September 23, 2026 · platform facts checked against the official docs linked below

At a glance

Review time: Most within a few days; can take up to a few weeks[1]
Summary limit: 132 characters[2]
Screenshots: 1–5 at 1280×800 (or 640×400)[3]
Registration: One-time fee, shown in the dashboard[4]

Where people find Chrome extensions

Chrome Web Store search and collections: Search ranks on listing metadata; editors pick collections and you can't pay to be featured.
Microsoft Edge Add-ons: Chrome extensions can often be ported with few changes (Microsoft publishes a porting guide), so it's a second store listing for little work.
Product Hunt: Extensions do well when the demo shows the before and after on a real site.
Extension directories: Niche lists of browser extensions and tools for the job your extension does.
Communities for the site you extend: An extension for GitHub, Gmail or LinkedIn users launches best where those users talk about the pain.

Assets to prepare

Assets to prepare before launch
Asset	Spec or guidance
Store icon	128×128 PNG with 96×96 artwork and 16 px transparent padding; must read on light and dark.[3]
Screenshots	At least 1, up to 5; 1280×800 preferred, 640×400 accepted; full bleed, square corners.[3]
Small promo tile	440×280. Required.[3]
Marquee promo tile	1400×560. Optional, used if you're featured.[3]
Summary	132 characters or fewer; no superlatives or competitor names.[2]
Permission justifications	One plain sentence per permission for the privacy tab.
Privacy policy URL	Required if you handle user data.

Store and listing rules

What the platform itself says, with a link to the page we checked.

Single purpose: an extension must have one narrow, easy-to-understand purpose; don't bundle unrelated features.[5]
Reviews take longer for new developers, dangerous permissions, big code changes, broad host permissions and hard-to-review or obfuscated code.[1]
Keyword stuffing in the title or description can get the item suspended; don't claim badges like "Editor's Choice".[2]
The Featured badge is by nomination through One Stop Support for public, English-supporting items without policy violations.[6]
Edge Add-ons certification can take up to seven business days; its description must be 250–10,000 characters.[7]

A 4-week launch timeline

Week 1 · four weeks out
- Cut permissions to the minimum and replace broad host permissions with specific ones where you can.
- Register the developer account with an email you'll keep; it can't be changed later.
- Write the single-purpose statement.
Week 2 · three weeks out
- Make the icon, screenshots and small promo tile at the exact sizes.
- Write the 132-character summary and description.
- Submit to the Chrome Web Store at least two weeks before your announcement date.
Week 3 · two weeks out
- Port and submit to Edge Add-ons.
- Build the landing page with an install button and a GIF of the extension working.
- Prepare the Product Hunt listing and maker comment.
Week 4 · launch week
- Test the published build on a clean Chrome profile.
- Line up users of the site you extend to try it on launch day.
- Plan your first update so you have something to say in week two.

Launch-day checklist

Confirm the listing is live in every region you want before announcing.
Launch on Product Hunt with the before/after GIF first in the gallery.
Post in the community of the site you extend, following its rules.
Submit to LaunchRanked so the landing page gets a permanent, followed link after review.
Watch reviews and uninstall feedback; reply to every early review.

After launch: SEO steps

Launch boards reset; search pages don't. These steps keep people finding you after launch week.

Give the landing page its own content: what it does on which sites, a GIF, FAQs. Don't just redirect to the store.
Target "{job} Chrome extension" and "{site} extension for {job}" searches with specific pages.
Nominate the extension for the Featured badge once you meet the criteria.
Localize the store listing for your biggest non-English markets.

Common mistakes

Requesting <all_urls> when you only need two sites; it slows review and scares users.
Announcing a launch date before the review is approved.
Screenshots with padding, rounded corners or tiny text.
Only having a Web Store listing; it rarely ranks on Google for non-brand searches.

Templates for this launch

FAQ

How long does Chrome Web Store review take?

Google says most extensions are reviewed within a few days, but it can take up to a few weeks. New developers, sensitive permissions and large or obfuscated code take longer.

What image sizes does the Chrome Web Store need?

A 128×128 icon, a 440×280 small promo tile, and 1–5 screenshots at 1280×800 or 640×400. The 1400×560 marquee is optional.

Should I publish to Edge Add-ons too?

Usually yes. Chrome extensions can often be ported with few changes, and Microsoft says certification can take up to seven business days.

How do I get featured in the Chrome Web Store?

Editors choose home page collections and you can't pay for placement. You can nominate eligible extensions for the Featured badge through One Stop Support.

Sources

Checked September 23, 2026. Platforms change their rules; open the source before you rely on a number.

← All 35 launch guides