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

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.

Monetization

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