Chrome Web Store & Firefox Add-ons Scraper - Extension Users, Ratings & Versions

Get Chrome extension and Firefox add-on data in bulk: user counts, star rating, number of ratings, current version, last-updated date, size, languages, developer, website, category and the "Featured" badge, plus Firefox permissions and reviews. Paste extension URLs or IDs, discover extensions from the official Chrome Web Store sitemap or category pages, or search Firefox add-ons by keyword. Schedule it and it tracks changes between runs (users delta, rating delta, new version).

No browser, no proxy, no login. $1 per 1,000 extensions.

What data do you get?

Field	Chrome Web Store	Firefox Add-ons
users	"7,000,000 users" as a number	average daily users
rating, ratingCount	4.3, 13,300 (ratingCountText keeps "13.3K")	4.48, 6,979 (exact)
version, updatedAt	yes	yes
size, sizeBytes	yes	yes
languages	full list	-
developerName, developerWebsite	yes	authors, homepage
category, itemType, featured	category, extension/theme, Featured badge	categories, Recommended / Line badges
establishedPublisher, isTrader	CWS badges	-
permissions, hostPermissions	- (not shown by Chrome)	yes
weeklyDownloads, license, tags, createdAt	-	yes
reviews[]	- (see FAQ)	optional, newest first
summary, description, iconUrl	yes	yes
changeType, usersDelta, ratingDelta, ratingCountDelta, previousVersion	yes	yes

Developer e-mail addresses and phone numbers are never output (they are personal data on many listings).

Use cases

• Extension developers: track competitors' users, ratings and release cadence every day.
• Security & IT teams: audit the extensions your company allows - version, last update, publisher, Firefox permissions; spot abandoned extensions (old updatedAt).
• Investors and extension buyers: screen extensions by users, rating and update history before making an offer.
• Agencies & lead generation: build lists of extension publishers with their website and category.
• Researchers: sample the Chrome Web Store catalogue through the sitemap.

How to use

1. Paste extension URLs or IDs into Extension URLs or IDs - Chrome and Firefox can be mixed.
2. Optionally add Chrome categories (e.g. productivity/workflow), turn on Discover from sitemap, or enter a Firefox search query.
3. Click Start. Results appear in the Dataset; the run summary (failed inputs, next sitemap shard) is in the OUTPUT record.
4. For monitoring, schedule the Actor daily or weekly with Only changed on.

Input example

{
  "extensionUrls": [
    "https://chromewebstore.google.com/detail/dark-reader/eimadpbcbfnmbkopoojfekhnkhdbieeh",
    "kbfnbcaeplbcioakkpcpgfkobkghlhen",
    "https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/"
  ],
  "chromeCategories": ["productivity/workflow"],
  "firefoxQuery": "password manager",
  "includeFirefoxReviews": true,
  "maxReviewsPerAddon": 20,
  "onlyChanged": false,
  "maxItems": 100
}

Accepted identifiers: chromewebstore.google.com/detail/... URLs, old chrome.google.com/webstore/detail/... URLs, bare 32-letter Chrome IDs, addons.mozilla.org/.../addon/<slug>/ URLs, Firefox slugs, GUIDs ({...} or name@domain) and numeric AMO ids. Prefix with chrome: or firefox: to force a store.

Output example (Chrome)

{
  "store": "chrome",
  "id": "eimadpbcbfnmbkopoojfekhnkhdbieeh",
  "name": "Dark Reader",
  "url": "https://chromewebstore.google.com/detail/dark-reader/eimadpbcbfnmbkopoojfekhnkhdbieeh",
  "users": 7000000,
  "rating": 4.3,
  "ratingCount": 13300,
  "ratingCountText": "13.3K",
  "version": "4.9.134",
  "updatedAt": "2026-10-28",
  "size": "836KiB",
  "languages": ["Deutsch", "English", "..."],
  "developerName": "Dark Reader Ltd",
  "developerWebsite": "https://darkreader.org/",
  "category": "Accessibility",
  "itemType": "extension",
  "featured": true,
  "establishedPublisher": true,
  "isTrader": true,
  "summary": "Dark mode for every website. Take care of your eyes, use dark theme for night and daily browsing.",
  "changeType": "changed",
  "usersDelta": 50000,
  "ratingDelta": 0.1,
  "previousVersion": "4.9.130",
  "fetchedAt": "2026-11-02T09:48:41+00:00"
}

Output example (Firefox, with reviews)

{
  "store": "firefox",
  "id": "uBlock0@raymondhill.net",
  "name": "uBlock Origin",
  "users": 11444100,
  "rating": 4.8,
  "ratingCount": 22270,
  "version": "1.75.0",
  "updatedAt": "2026-11-01T20:16:14Z",
  "size": "4.43MiB",
  "developerName": "Raymond Hill",
  "category": "privacy-security",
  "featured": true,
  "badges": ["recommended"],
  "permissions": ["alarms", "dns", "menus", "privacy", "storage", "tabs", "..."],
  "weeklyDownloads": 241352,
  "license": "GNU General Public License v3.0 only",
  "reviews": [
    {"rating": 5, "text": "Works perfectly", "author": "AlwaysNur", "createdAt": "2026-11-02T01:34:32Z", "version": "1.75.0", "developerReply": null}
  ]
}

Change tracking (monitor mode)

Every run stores a small snapshot (users, rating, rating count, version) per extension under your State key. The next run with the same key adds changeType (new / changed / unchanged), usersDelta, ratingDelta, ratingCountDelta and previousVersion. With Only changed on, unchanged extensions are skipped and not charged, and changed ones cost half price. Use a different State key for each watch-list.

Pricing

Pay per result, no subscription:

Event	Price
Extension (Chrome or Firefox)	$0.001 ($1 per 1,000)
Changed extension (monitor mode)	$0.0005
Firefox review	$0.0002
Actor start	$0.00005

How it compares (Apify Store, November 2026, public prices):

Actor	Price per extension with details
This Actor	$0.001, Chrome + Firefox, change tracking
calm_builder/chrome-web-store-scraper	$0.0012 per item + $0.003 per detail
easyapi/chrome-extension-scraper	$0.00499
tugelbay/chrome-web-store-intelligence	$0.005 per profile
Firefox add-on scrapers	about $0.009

You can set a maximum charge per run; the Actor stops cleanly when it is reached.

FAQ

Why no Chrome keyword search or Chrome reviews? The Chrome Web Store's robots.txt disallows /search and /detail/*/reviews, and Google's terms forbid automated access that ignores robots.txt. This Actor only requests pages robots.txt allows: extension detail pages, category pages and the official sitemap. For discovery use categories or the sitemap; if you need Chrome reviews, this is not the right tool.

How does it respect the stores? Both robots.txt files are downloaded at the start of every run and every URL (including redirects) is checked against them. Requests are spaced about 1 second apart per store, query strings (tracking parameters) are dropped, and no proxies are used. Firefox data comes from the public addons.mozilla.org API.

Are Chrome rating counts exact? Chrome shows rounded counts such as "13.3K ratings"; we convert that to 13300 and keep the original text in ratingCountText. Chrome user counts are also rounded by Google. Firefox counts are exact.

Why does a Chrome ID come back as "not found"? The listing was removed, made private or is not available in the store's default region. It is listed in OUTPUT.failed and not charged.

How do I walk the whole Chrome catalogue? Turn on Discover from sitemap with a large Max extensions. Each sitemap shard holds about 8,000-9,000 listings (extensions and themes). The OUTPUT record shows nextSitemapShard; pass it as Sitemap start shard in the next run.

Why do Firefox rows almost always show as "changed"? Firefox reports average daily users, which moves a little every day. Chrome's rounded user count changes less often.

Who owns the data? Listing content belongs to the extension authors and is shown publicly by Google and Mozilla. Use it in line with the stores' terms and applicable law.

Use with AI agents (Apify MCP)

Add this Actor as a tool in the Apify MCP server (gazidev/browser-extension-store-data) and ask your assistant things like "Compare users, rating and last update of the top 5 password managers on Chrome and Firefox" or "Which of these 40 extension IDs have not been updated in a year?". The flat JSON output is easy for LLMs to reason about. You can also call it from the Apify API, Python/JS clients, Make, Zapier or n8n.