Skip to main content
Publishing your extension involves four sequential stages — from setting up your developer account to managing the listing after it goes live. Extensy generates CWS-ready code for you; your job is to supply the promotional assets and work through the store’s submission process.
Extensy produces a store-ready ZIP. You are responsible for the promotional assets — icons, screenshots, and descriptions — that make your listing stand out.

The publishing journey

1

Set up a developer account

Register with Google to become a verified Chrome extension publisher. There is a one-time $5 USD fee.
2

Prepare your assets

Gather your extension ZIP, a 128×128 px icon, at least one screenshot, short and detailed descriptions, and a privacy policy if your extension collects user data.
3

Submit for review

Upload your ZIP and assets to the Chrome Web Store Developer Console, declare your permissions, configure visibility, and submit.
4

Manage after launch

Monitor install counts and active users, respond to reviews, and push updates whenever your extension changes.
Most reviews complete in 1–3 business days. Extensions that request broad permissions (such as <all_urls>) may take up to a week.

Detailed guides

Work through each guide in order to complete your submission.

Developer Account

Create and verify your Google developer profile.

Prepare Assets

Checklist for icons, screenshots, and descriptions.

Submit to Store

Step-by-step submission walkthrough.

After Publishing

Manage reviews and push updates after launch.