PPlatformAppStores

Chrome Web Store

Browser

Google LLC · Browser & OS extension stores

Best for: Developers wanting maximum reach for a browser extension.

Overview

Chrome Web Store distributes browser extensions built on the Manifest V3 extension platform, covering content scripts, background service workers, and browser-action UI. Google's Developer Program Policies govern permissions, user data handling, and prohibited behaviors.

How to build & ship

  1. 1Register a Chrome Web Store developer account and pay the one-time $5 registration fee
  2. 2Build the extension against Manifest V3 with HTML/CSS/JS and the Chrome extension APIs
  3. 3Package the source into a ZIP and upload it via the Developer Dashboard
  4. 4Complete the store listing, privacy disclosures, and permission justifications
  5. 5Submit for review and publish once approved

Key APIs & SDKs

Manifest V3
chrome.* extension APIs (tabs, storage, scripting)
Service workers
declarativeNetRequest
Chrome Web Store Publish API

Integration types

Extension

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: None
  • Security review: Required
  • Automated and manual review against the Chrome Web Store Developer Program Policies.
  • Automated plus human policy review, usually within a few days but occasionally up to a few weeks for broad permissions or obfuscated code.
  • No platform-wide API rate limit; governed by whichever web APIs the extension calls.
Auth docs Store policies

Monetization

Free
Paid app
Listing fee
Onboarding
$5 one-time developer registration fee
Commission
0% (Chrome Web Store payments API deprecated; developers self-manage billing)
Merchant of Record
Developer is MoR

Pros & cons for builders

Pros

  • Largest browser-extension user base by far
  • Low one-time fee, no recurring cost
  • Well-documented APIs and tooling
  • MV3 shared across Chromium browsers

Cons

  • Strict, sometimes opaque policy enforcement and takedowns
  • Broad permissions slow review
  • MV3 limits some background/networking patterns

Frequently asked questions

How do I get my app approved on Chrome Web Store?

Automated plus human policy review, usually within a few days but occasionally up to a few weeks for broad permissions or obfuscated code.

What authentication does Chrome Web Store use?

Chrome Web Store apps primarily authenticate with OAuth 2.0, also supporting None.

How is Chrome Web Store monetized?

Chrome Web Store supports Free, Paid app, Listing fee. Typical commission: 0% (Chrome Web Store payments API deprecated; developers self-manage billing). Onboarding fee: $5 one-time developer registration fee.

Is a security review required to list on Chrome Web Store?

Yes, Chrome Web Store requires a formal security or listing review before apps go live. Automated and manual review against the Chrome Web Store Developer Program Policies.