Chrome Web Store: Extension Metadata Snapshot

Snapshot Chrome Web Store extension metadata (rating, user count, version, developer, and screenshots) by extension ID. One row per extension. Public HTML, no authentication required.

How to use

Provide a list of Chrome extension IDs (the 32-character hash from the Web Store URL) as extensionIds.

Input schema:

{
  "extensionIds": [
    "bfbmjmiodbnnpllbbbfblcplfjjepjdn",
    "cfhdojbkjhnklbpkdaibdccddilifddb"
  ]
}

Field	Type	Default	Description
extensionIds	string[]	["bfbmjmiodbnnpllbbbfblcplfjjepjdn"]	Extension IDs from the Web Store URL path

Extension IDs can be found in the Chrome Web Store URL: https://chromewebstore.google.com/detail/<extension-name>/<extensionId>

Example output row

{
  "extensionId": "bfbmjmiodbnnpllbbbfblcplfjjepjdn",
  "snapshotAt": "2026-06-04T05:00:00+00:00",
  "name": "AdBlock, best ad blocker",
  "description": "Block ads, pop-ups and annoying banners...",
  "ratingValue": 4.6,
  "ratingCount": 489231,
  "developerName": "AdBlock",
  "imageUrl": "https://lh3.googleusercontent.com/...",
  "userCount": "65,000,000+",
  "version": "6.8.0",
  "updatedAt": "June 3, 2026",
  "storeUrl": "https://chromewebstore.google.com/detail/bfbmjmiodbnnpllbbbfblcplfjjepjdn"
}

Pricing

Pay per event. Price per 1,000 events:

Event	Base price	Bronze	Silver	Gold
Chrome Web Store extension snapshot	$0.50	$0.45	$0.40	$0.35

Bronze, Silver and Gold are the discounts Apify gives users of its paid plans. The Pricing tab always shows the current prices.

Buyer

• Market intelligence: track competitor extensions: monitor rating drift, user growth, version cadence.
• Chrome extension directories: bulk-populate a database of extension metadata for catalogues or comparison sites.
• Developer research: find the most popular extensions in a niche before building your own.
• Review aggregation: combine with rating/review scrapers to benchmark extension quality at scale.
• App store analytics: monitor your own extension's public metrics over time for reporting.

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/chrome-webstore-extensions").call(run_input={"extensionIds": ["bfbmjmiodbnnpllbbbfblcplfjjepjdn"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/chrome-webstore-extensions').call({"extensionIds": ["bfbmjmiodbnnpllbbbfblcplfjjepjdn"]});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~chrome-webstore-extensions/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"extensionIds": ["bfbmjmiodbnnpllbbbfblcplfjjepjdn"]}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/chrome-webstore-extensions",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

FAQ

Do I need an account, cookies or an API key?

No. The actor reads public data without logging in. You only need an Apify account to start it.

How am I charged?

Pay per event, at the prices on the Pricing tab for your Apify plan (the Pricing section of this page lists them). The platform usage of the run is included in those prices, and your spending limit for a run is always respected.

Why did my run return no results?

The status message and the log of the run say why: usually nothing matched the input, or the source did not answer for a moment. Check the input against the example above and run it again.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects data that the source publishes openly, without a login. Public data can still be personal data under laws such as the GDPR, and sources have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when the source changes?

An automated test runs the actor every day on the example input and checks the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.

Related actors

• VS Code Extension Scraper: Open VSX Registry Metadata
• JetBrains Marketplace Plugin Scraper
• npm Package Stats Scraper: Metadata and Downloads
• App Store Scraper: App Details, Ratings, Prices
• App Store Search Scraper: Apps by Keyword
• App Store Top Charts Scraper: Ranks by Country and Genre

Source

Data is scraped from the public Chrome Web Store listing pages at:

https://chromewebstore.google.com/detail/{extensionId}

Metadata is extracted from the application/ld+json structured data block (JSON-LD, SoftwareApplication schema) embedded by Google for SEO purposes, supplemented by targeted regex probes for userCount, version, and updatedAt fields not present in the structured data. No authentication is required. Extensions that have been removed from the store return HTTP 404 and are skipped gracefully.