How to Launch a Chrome Extension: Store Listing, Review and Launch

A Chrome extension is one of the fastest products to build and one of the hardest to get noticed. The Chrome Web Store is crowded, its search favors extensions that already have users and ratings, and a new listing starts with neither. A good launch gives you that first group of users, reviews and links, and the store does more of the work after that.

This guide goes through it in order: preparing the extension so it passes review, building a listing that turns visitors into installs, the launch itself, and the first weeks after. It assumes the extension works and you are ready to put it in front of people.

Step 1: set up the developer account early

• Register as a Chrome Web Store developer with the Google account you want to own the extension long term. There is a one-time registration fee.
• Use a company or shared account if more than one person will manage the listing, rather than a personal Gmail you may lose access to.
• Verify the publisher details the dashboard asks for, including a contact email. Users see some of it on the listing.
• Decide who owns it now. Moving an extension between accounts later is harder than setting up the right owner once.

Step 2: prepare the extension to pass review

Every new extension and every update is reviewed before it goes live. Review usually takes from a few days to a few weeks, and extensions that ask for broad access take longer. Most rejections come from a handful of avoidable problems.

• Use Manifest V3. New extensions must use it. If you started from an old tutorial, check the manifest version first.
• Ask for the fewest permissions possible. Each permission you request needs a justification in the dashboard, and broad host permissions such as access to all sites get more scrutiny. Use activeTab or optional permissions where they do the job.
• Keep to a single purpose. Chrome Web Store policy requires an extension to have one narrow, easy-to-understand purpose. A tab manager that also blocks ads and changes your new tab page will struggle.
• No remote code. All the logic must ship in the package. Loading and running scripts from your server is not allowed under Manifest V3.
• Fill in the privacy practices honestly. Declare what user data you collect and why, and link a privacy policy if you handle any user data. The privacy policy generator gives you a starting point to adapt.
• Make the listing match the extension. Screenshots and descriptions that promise features the extension does not have are a common reason for rejection.

Plan around review time. Submit at least a week before any launch date you have announced, and do not change the package between approval and launch. In the dashboard you can choose not to publish automatically once approved, so you can release on the day you choose.

Step 3: write the listing

The listing is your landing page inside the store. Most people decide to install from the name, the summary, the first screenshot and the rating, in that order.

Name

Short, memorable, and ideally with the main thing it does: "Tabby: Tab Manager" works better than "Tabby" alone, because people search the store for the job, not your brand. Do not use another company's trademark in the name, and do not stuff it with keywords.

Summary (up to 132 characters)

The summary comes from the description field in your manifest and shows under the name in search results and on the listing. It has 132 characters to win the click. Describe the one job the extension does and where it works: "Save and restore groups of tabs in one click, so your research survives a browser restart." Check it with the Chrome Web Store description checker.

Detailed description

The longer description is set in the developer dashboard. Use it to:

• Restate the problem and the result in the first two lines, because many people read no further.
• List the main features as short lines, each one a result.
• Explain why each permission is needed, in plain words. Users read the permission warning on install, and an honest explanation reduces drop-off.
• Say what data you collect, or that you collect none.
• Give a support link or email.

Use the words people search for, naturally. Repeating a keyword list breaks store policy and reads badly.

Category and language

Pick the category a user would browse for your extension, not the one with the fewest competitors. Add translated listings if you have users in other languages: they are cheap to add and help store search in those languages.

Step 4: make the images at the right sizes

Asset	Size	Check with
Store icon	128 x 128 pixels, PNG	View it at small size before you upload
Screenshots	1280 x 800 (preferred) or 640 x 400. JPEG or 24-bit PNG, no transparency. At least one, up to five.	Chrome Web Store screenshot size checker
Small promo tile	440 x 280 pixels. JPEG or 24-bit PNG, no transparency.	Chrome Web Store promo tile size checker
Marquee promo tile (optional)	1400 x 560 pixels	Same checker
Promo video (optional)	A YouTube link	Watch it with the sound off

• Screenshots show the extension working on a real page, with a short caption on each. A screenshot of a popup floating on a blank background tells people little.
• The first screenshot does the most work. Make it the main job, done, with a caption stating the result.
• The small promo tile is shown small. Use your logo and a few words on a solid background. Avoid screenshots and small text in it.
• Keep one visual style across the icon, tiles and screenshots, so the listing reads as one product.
• Use 1280 x 800 for screenshots so they stay sharp on large screens. The screenshot checker resizes an image that is close but not exact.

Step 5: build the first-run experience

An install is not a user. Many people install an extension, see nothing happen, and forget it is there. Two small pieces of code help a lot.

• A welcome page on install. Open a short page when the extension is first installed, using the runtime.onInstalled event. Show the one thing to do first, and how to pin the extension to the toolbar so people can find it.
• An uninstall feedback page. Set an uninstall URL with runtime.setUninstallURL pointing to a one-question form: "What made you remove it?" These answers are the most honest feedback you will get.
• A visible first result. If the extension works in the background, show something the first time it acts, such as a small badge or notification, so users know it is doing its job.

Step 6: a landing page outside the store

Launch posts should usually link to your own page, not straight to the store. A page on your domain can explain the problem, show a demo, collect emails from people on other browsers, and earn links that help your site in search. Put a clear "Add to Chrome" button on it that goes to the store listing.

• Check the page's preview card with the social preview checker, because it will be shared on X and Reddit.
• Tag the store link with UTM parameters from the UTM builder. Then your analytics can tell which post sent the visitors who clicked through to install.
• Mention other browsers. Microsoft Edge and other Chromium browsers can install from the Chrome Web Store, and Edge has its own add-ons store you can list in too. Firefox uses the same WebExtensions approach with some differences, so a port is often small work.

Step 7: launch it

Extensions launch well in places where people try things immediately. Pick two or three and spread them over a couple of weeks.

• Product Hunt suits extensions for productivity, writing, design and browsing, especially ones with a strong visual demo. Use the Product Hunt launch checklist to prepare.
• Show HN suits developer extensions and anything technical or privacy-focused. Explain how it works and what data it touches; that crowd will ask. See how to write a Show HN post.
• Reddit communities where your users already discuss the problem, written for each community. Read the rules first; many ban direct promotion.
• Directories and launch sites that fit. The developer tool launch sites and AI tool directories cover the main categories. Many list extensions.
• Your own audience: a waitlist, newsletter or followers. The first installs and reviews from them matter most.

On each platform, lead with a short GIF or video of the extension doing its job on a real page. For an extension, seeing it work is the whole pitch.

Step 8: the first weeks after

• Ask for reviews at the right moment. After a user has had a clear success, not on day one. A small, dismissible prompt is enough. Never offer anything in exchange for a rating: it breaks store policy.
• Reply to every review, especially the bad ones. Future users read the replies.
• Read the uninstall answers weekly and fix the top reason first.
• Ship small updates. An actively maintained listing looks safer to install. Each update goes through review, so batch changes sensibly.
• Watch the store dashboard for impressions, installs and uninstalls by week. A rising number of store impressions with flat installs means the listing needs work; flat impressions mean you need more outside traffic.

Where Aback Launch fits

Aback Launch is a weekly launch platform where extensions launch alongside other new products. Launches go live every Friday at 00:00 UTC and stay up all week, and every product keeps a permanent page that links to your site. The link becomes dofollow once you add our badge.

FAQ

How long does Chrome Web Store review take?

Usually from a few days to a few weeks. Extensions that request broad permissions, such as access to all websites, often take longer. Submit at least a week before any launch date you have announced.

What size are Chrome Web Store screenshots?

1280 x 800 pixels (preferred) or 640 x 400, as JPEG or 24-bit PNG without transparency. You need at least one and can upload up to five.

How long can a Chrome extension description be?

The summary, which comes from the manifest's description field, can be up to 132 characters. The detailed description in the developer dashboard has a much larger limit.

Where should I launch a Chrome extension?

Product Hunt for consumer and productivity extensions, Show HN for developer and privacy-focused ones, the Reddit communities where your users discuss the problem, and directories that fit your category.

How do I get more Chrome extension installs?

Improve the summary and first screenshot, bring outside traffic from launches and your own page, ask happy users for reviews, and fix the main reason people uninstall.