Chrome Web Store Scraper — Extensions, Reviews & Extension Ideas

Extract Chrome Web Store extensions with their full profile — users, rating, number of ratings, version, last update, first publication date, size, languages, permissions, data the developer declares it collects, in-app purchases, Featured and established-publisher badges, the developer and their EU trader status — plus reviews with the developer's reply, developers with all their extensions found, and a category snapshot with an opportunity score to spot extension ideas worth building.

No login, no account, no API key, no browser. Duplicate rows, removed extensions and error rows are never charged.

This actor is not affiliated with, endorsed by, or connected to Google or the Chrome Web Store. It reads public data only.

What you get

Output type	One row per	Highlights
extensions (default)	extension in the categories or searches you choose	Users, rating, ratings count, version, last update, first published, days since update, abandoned flag (2+ years), size, languages, minimum Chrome version, manifest version, API and host permissions, all-sites access, declared data collection, in-app purchases, Featured / established publisher, developer, trader status, website, support and privacy links, screenshots, related extensions
extension-details	link or id you paste	The same full profile for specific extensions
reviews	review	Stars, text, date, edited flag, helpful and unhelpful votes, extension version used, language, developer reply and its date. Filter by stars and language, most recent or most helpful first
category-snapshot	category or search	Total and median users, median rating, share rated under 4 stars, share not updated in 2 years, launches in the last 12 months, Manifest V2 share, in-app-purchase share, top 10 extensions, opportunity gaps and the opportunity score
developers	developer	Extensions found in the run, total users, weighted rating, categories, Featured and abandoned counts, website, public business contact (EU-declared traders only)

Find extension ideas

• Popular but disliked: maxRating: 3.5, minUsers: 50000 — an opening for a better product.
• Abandoned with real users: abandonedOnly: true, minUsers: 10000 — users stuck with an unmaintained tool.
• Still on Manifest V2: filter the manifestVersion column — extensions that need a rebuild.
• What users complain about: outputType: reviews, reviewsStars: ["1", "2"] on the leaders of a category.
• Which categories are open: outputType: category-snapshot on several categories and compare opportunityScore.

Opportunity score

Each category-snapshot row carries opportunityScore (0–100), computed only from the extensions in that snapshot, with a published, deterministic formula (same input → same score):

• 40% demand = log10(1 + total users) / 9, capped at 1 (a category with a billion users scores 1)
• 25% dissatisfaction = share of rated extensions under 4 stars
• 20% staleness = share not updated in more than 730 days
• 15% openness = 1 / (1 + N / 50), where N is the real size of the category or search when the store tells it (populationCount, with opennessBasis: "category"): the number of results the store reports for a search, or every extension when the listing ran out. The store gives no total for a category, so for categories larger than the sample (and for filtered snapshots) N is the sample size (opennessBasis: "sample")

opportunityComponents gives the four parts. Compare category scores at the same snapshotSampleSize: demand is summed over the sample, and for categories openness is too (0.333 with the default 100), so it only separates small categories and searches. Measured on 17 Oct 2026: the store's result count for a search was within 1–4% of the distinct results it actually returns (pdf 462 vs 446, notion 477 vs 472, crm 629 vs 623). Over the 18 categories with the default sample of 100 (store order): scores from 36.1 (Household) to 57.2 (Workflow & Planning). opportunityGaps lists up to 10 extensions with 10,000+ users that are rated under 4 stars (with 20+ ratings) or abandoned. It is arithmetic on public data, not a prediction.

Filters

• Categories (the 18 extension categories) and search texts (the store returns up to about 400–780 results per search: pdf 427, email 751, ai 773)
• Category order: recommended (store default), popular, highest rated
• Users, rating and number of ratings ranges, Featured only, established publishers only — checked on the listing, so skipped extensions cost nothing
• Updated after / before, abandoned only, EU traders only — checked on each profile (also when picking extensions for reviews); a run checks up to 25 profiles per requested row (at least 300) and the status message says when it stops
• Reviews: stars, language, written since, most recent or most helpful, max per extension

Pasting extension links with the default output type runs extension-details for exactly those; filters are not applied to pasted links (the log and the run summary say so, as for any option that has no effect).

Data quality, measured

Measured on 17 Oct 2026 over 50,000 extensions of all 18 categories in one run on the Apify platform (about 3,400 per category, all of the smaller ones; "filled" = not null and not empty):

Extension field	Filled
Version, last update, first published, size, languages, manifest version, minimum Chrome version, badges	99–100%
Users	96.5%
Rating · ratings count (extensions nobody rated have none)	65.2%
Screenshots · privacy policy · support site · website	99.1% · 60% · 37.4% · 31.2%
API permissions · content-script sites · host permissions	81.7% · 61.6% · 55.8%
Declared data categories (empty = declares none)	27.9%
Developer name · legal name	88.4% · 20.2%
Public business email / phone (EU traders, 11.2% of extensions)	11.1% / 11.1%

Extension rows had 44.1 filled fields on average (of 58). Popular extensions are filled better than the long tail: on the top of each category, ratings reach about 98%.

Reviews (1,876 in 50 test runs): text, stars, dates, votes and language 100%; reviewer name 99.8%; extension version 96.4%; developer reply 5.4%.

Default input {}: 20 extensions in 2–4 seconds (measured on 17 Oct 2026, 4 runs on the Apify platform, 512 MB).

Speed, read live: the 50,000-extension run took 1 h 54 min (about 7 profiles per second, 7% from the cache, peak memory 266 MB). Reviews are faster: 1,000 in about 7 seconds.

In 50 test runs on the Apify platform (17 Oct 2026, all output types, filters, links, edge cases and a spending cap) 50 of 50 succeeded, with charges equal to rows delivered in every run and 0 duplicates.

How it compares

Compared with the other Chrome Web Store actors in the Apify Store, as declared in their own dataset schemas (17 Oct 2026):

	This actor	Typical alternatives
Fields per extension	59	9–31
Extension + reviews + developers + category summary in one actor	Yes	Usually one of them
First published date, abandoned flag, declared data collection, in-app purchases	Yes	Not in their schemas
Reviews filtered by stars and language, with developer reply	Yes	Some
Opportunity score per category	Yes	No
Price per extension profile	$1.00 per 1,000	free to $5.00 per 1,000; those with 20+ fields: $3.00–$5.00
Error rows and removed extensions charged	Never	Varies

Pricing

Pay per event:

• Extension profile: $0.001 ($1.00 per 1,000)
• Review: $0.0001 ($0.10 per 1,000)
• Category snapshot: $0.005 per category or search
• Developer: $0.001
• Actor start: $0.00001

Error rows, duplicates within a run and removed extensions are never charged. Set a maximum cost per run and the actor stops cleanly when it is reached.

Input example

{
  "outputType": "extensions",
  "categories": ["productivity/workflow"],
  "sortBy": "popular",
  "minUsers": 10000,
  "maxRating": 3.8,
  "maxItems": 100
}

FAQ

How fresh is the data? By default a profile that any run of this actor fetched in the last 24 hours is reused from a shared cache (maxCacheAgeHours); those rows carry cachedAt and cost the same. In our 50 test runs, which repeated many inputs, 66% of extension rows came from the cache; in the 50,000-extension run, 7%. Set maxCacheAgeHours to 0 to read every profile live. The store itself refreshes users and ratings about once a day.

Is "users" the number of installs? It is the number the store shows (weekly active users as counted by Google), rounded by the store for large extensions.

Why do developer emails appear only for some extensions? By default you get the business contact (email, phone, address, D-U-N-S) that the store shows for developers who declared themselves traders under EU law. The store also shows an email for many other developers, some of whom are private individuals: their email and phone are returned only if you turn on includeNonTraderContacts (off by default), and their postal address never is.

Do you return reviewer photos or emails? No. Only the public display name, the review and the developer's reply; contact details inside texts are removed.

What happens with a removed extension? You get one extension-not-found row explaining it, not charged.

Can I get the whole catalog? Run every category with a high maxItems; the largest category returned 7,284 different extensions. Duplicates across categories are removed within a run.

Support: open an issue on the actor page.