Publish to the Chrome Web Store

This page covers publishing to the Chrome Web Store—not the same step as publishing to the Awetheme marketplace.

Google’s dashboard details may change, but the flow is roughly:

1. Prepare the theme package

Make sure it includes:

• Config files and any images you use
• A 128×128 store icon (the creator always writes one on export; customize it under Chrome Web Store listing if you want)

Exporting a ZIP from the creator usually covers this.

2. Zip it

After exporting and extracting the ZIP, enter the outermost theme folder. You should see manifest.json directly there, without another same-named folder nested inside it. A typical structure looks like:

my-theme/
|-- manifest.json      ← Theme configuration (name, colors, image paths, icons, etc.)
|-- images/            ← Background, frame, and other images
`-- icons/
    `-- icon-128.png   ← Store / extension-management icon (always included)

The important part is that extraction creates only this one theme folder: inside my-theme/, manifest.json sits alongside images/ and icons/. You should not end up with a double-nested path such as my-theme/my-theme/manifest.json.

3. Register a developer account

Complete registration in the Chrome Web Store developer dashboard (there is usually a one-time registration fee—follow the current dashboard prompt).

4. Create a listing and upload

You will typically provide:

• Name, description, and category
• Screenshots / preview images
• Privacy disclosures (themes usually collect no data—answer accurately)

For promotional image sizes and optional multilingual theme files, see Store languages and image sizes.

5. Save the draft and submit for review

When you finish the listing, click Save draft first. After it saves and all required fields pass validation, click Submit for review. Once approved, you can publish. For updates, upload a new ZIP, save the draft, and submit it again.

Estimated review time: Most submissions are reviewed within a few days, but submission volume, a first submission, or manual review can extend this to several weeks. If review takes longer than three weeks, contact developer support. See the official Chrome Web Store review documentation for current guidance.

Tips

• Ship a small stable version first and confirm preview and install work
• Then add more colors and image details gradually