Publishing extension to Chrome Web Store

Publishing an Extension to Chrome Web Store

Chrome Web Store is the only official channel for distributing Chrome extensions. The publishing process includes registering a developer account, preparing a package, and passing review.

Registering a Developer Account

Visit chrome.google.com/webstore/devconsole. You need a Google account and a one-time $5 payment for verification. After payment, you get permanent access with no limit on the number of extensions.

Preparing a ZIP Package

The archive contains only extension files, without hidden files and development folders:

# Build before publishing
npm run build

# Create archive — exclude unnecessary files
cd dist/
zip -r ../extension-v1.2.0.zip . \
  --exclude "*.map" \
  --exclude ".DS_Store" \
  --exclude "node_modules/*" \
  --exclude "*.test.js"

Package structure:

manifest.json        ← required in root
icons/
  icon-16.png
  icon-32.png
  icon-48.png
  icon-128.png       ← used in Web Store
background/
  sw.js
content/
  injected.js
popup/
  popup.html
  popup.js

Requirements for manifest.json

{
  "manifest_version": 3,
  "name": "Extension Name",
  "version": "1.0.0",
  "description": "Short description up to 132 characters — appears in store listing",
  "icons": {
    "16": "icons/icon-16.png",
    "32": "icons/icon-32.png",
    "48": "icons/icon-48.png",
    "128": "icons/icon-128.png"
  }
}

version must match 1.2.3 or 1.2.3.4 format. With each update, the version must be strictly greater than the previous one.

Screenshots and Graphics for Listing

Store requirements:

• Store Icon: 128×128 px, PNG, no transparency in corners (Store will crop)
• Screenshots: minimum 1, maximum 5, size 1280×800 or 640×400 px
• Small Promo Image: 440×280 px (optional, but increases CTR)
• Large Promo Image: 920×680 px (for promo block on homepage)
• Video: YouTube link (optional)

Make screenshots with real content, show key use cases.

Filling the Listing

In Developer Dashboard:

• Name: up to 45 characters. Unique, accurately describes the function.
• Short Description: up to 132 characters. First 45 are most important for search.
• Detailed Description: HTML partially supported. Use lists, clearly describe capabilities.
• Category: choose from list (Productivity, Developer Tools, etc.)
• Language: primary listing language. Can add localized versions via _locales/.

Privacy Disclosure

As of 2024, filling Data Privacy Policy is required:

• Specify what data the extension collects
• If the extension doesn't collect data — explicitly mark this
• Link to Privacy Policy (required if you collect anything)

Without correct filling, review will be rejected.

Publishing and Review

After uploading ZIP and filling the listing — click "Submit for review". Review usually takes from a few hours to several days. First publication of a new extension takes longer (up to 2-3 weeks in complex cases).

Rejection reasons and how to avoid them:

• Requesting excessive permissions — ask only for what you actually use. Each permission requires justification.
• External code without security policy — all JS must be in the package or have explicit declaration in content_security_policy.
• Violating minimum permissions policy — <all_urls> instead of specific hosts will be grounds for additional review.
• Missing or incorrect Privacy Policy — when collecting any data.

Updating an Extension

Upload a new ZIP with increased version through Developer Dashboard → "Upload new package" button. Update goes through the same review. Users get updates automatically within a few hours after publication.

Automation via Chrome Web Store API

For CI/CD, you can upload updates automatically:

# Install chrome-webstore-upload-cli
npm install -g chrome-webstore-upload-cli

# Publish
webstore upload \
  --source extension.zip \
  --extension-id your-extension-id \
  --client-id $CWS_CLIENT_ID \
  --client-secret $CWS_CLIENT_SECRET \
  --refresh-token $CWS_REFRESH_TOKEN \
  --auto-publish

Tokens are obtained through Google Cloud Console → OAuth 2.0 with scope https://www.googleapis.com/auth/chromewebstore.

Group Policies for Corporate Distribution

For internal extensions (employees only), you can use forced installation through Google Workspace Admin or Windows Group Policy, without publishing to Store. This bypasses review for closed tools.