Steam Reviews Scraper
Pricing
from $2.99 / 1,000 results
Steam Reviews Scraper
Steam Reviews Scraper is a Python tool designed to extract user reviews, playtimes, ratings, and reviewer details for any game on Steam. It exports structured review datasets into CSV or JSON formats for sentiment analysis, market research, and game analytics.
Pricing
from $2.99 / 1,000 results
Rating
0.0
(0)
Developer
real-estate-api
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
4 days ago
Last modified
Categories
Share
Steam Reviews Scraper: Export Game Reviews, Prices and Store Data
Steam reviews scraper for public Steam store data. It pulls game reviews (playtime, votes, language), review score summaries, store details and prices, search hits, top sellers, and live player counts. No Steam API key.
Store search stops around 10 hits per term. Review totals change with the language filter. Full app-list endpoints are not included here because one is retired and the other requires your own Steam Web API key.
Use cases
- Game developers and publishers: read review text, playtime, and votes when you want sentiment or bug reports from people who actually played
- Market research: collect top sellers, new releases, specials, and coming soon lists with prices for a store country
- AI and NLP datasets: export review text plus language, helpful votes, and hours played
- Community analysis: keep author ids, profile URLs, and whether the review was a Steam purchase, a free copy, or a refund
- Price tracking: store the pre-discount and current price in currency units, converted from Steam's cents
What data does this Steam reviews scraper extract?
| Mode | You provide | Rows |
|---|---|---|
reviews | App ids or store URLs, plus filters | Review rows, and one summary row per game when that option is on |
app_details | App ids or store URLs | One store record per app |
search | Search terms | Up to about 10 hits per term |
featured | Country code | Top sellers, new releases, specials, coming soon |
player_count | App ids | Current player count |
Playtime in the output is hours. Steam sends minutes. Prices in the output are currency units. Steam sends cents. Timestamps are UTC ISO-8601.
Input
| Parameter | Type | Default | Description |
|---|---|---|---|
mode | string | reviews | Reviews, store details, search, featured lists, or player count. |
apps | array | 730 | App ids or URLs such as https://store.steampowered.com/app/730/CounterStrike_2/. |
searchTerms | array | empty | Search mode only. About 10 results per term, no next page. |
reviewFilter | string | recent | recent, all (most helpful), or updated. |
reviewLanguage | string | all | Language code. Summary totals follow this value. |
reviewType | string | all | all, positive, or negative. |
purchaseType | string | all | all, steam, or non_steam_purchase. |
dayRange | integer | empty | Last N days. Sent only with reviewFilter=all. |
includeSummary | boolean | true | Add the score summary from the first review page. |
enrichWithDetails | boolean | false | Add store details onto search and featured rows. Slower. |
countryCode | string | us | Store country for prices. Some apps are absent in a region. |
maxItems | integer | 200 | Total rows this run, hard cap 10,000. |
maxReviewsPerApp | integer | 1000 | Review rows per game. Each request asks for 100. |
maxConcurrency | integer | 3 | Parallel apps, max 5. App details stay at 3 or fewer. |
timeoutSecs | integer | 300 | Stop starting new work after this many seconds. |
requestTimeoutSecs | integer | 30 | Per-request timeout. 429 and 5xx responses back off. |
proxyConfiguration | object | No proxy | Optional. Leave off unless Steam blocks the IP. |
Example input
{"mode": "reviews","apps": ["730", "https://store.steampowered.com/app/620/Portal_2/"],"reviewFilter": "recent","reviewLanguage": "all","reviewType": "all","purchaseType": "all","includeSummary": true,"maxItems": 200,"maxReviewsPerApp": 100,"maxConcurrency": 3,"timeoutSecs": 300,"requestTimeoutSecs": 30,"proxyConfiguration": { "useApifyProxy": false }}
Review rows, store rows, and exports
Results go to the default dataset. Open the Reviews, Review summaries, Apps, or Errors view. Download JSON, CSV, or Excel from the Apify dataset.
A review row looks like this (playtime already converted to hours):
{"recordKind": "review","appId": 730,"reviewId": "237492390","url": "https://steamcommunity.com/profiles/76561199826248400/recommended/730/","text": "отличная игра помогает справится со стрессом","language": "russian","votedUp": true,"votesUp": 0,"weightedVoteScore": 0.5,"createdAt": "2026-10-11T19:18:57Z","steamPurchase": true,"authorSteamId": "76561199826248400","authorName": "viski","playtimeForeverHours": 396.0,"playtimeAtReviewHours": 396.0}
Summary rows include reviewScore, reviewScoreDesc, totalPositive, totalNegative, totalReviews, positivePercent, and filterLanguage. Steam only sends the full summary on page 1, and the totals are for the language you asked for. language=all and language=english do not match.
Store rows include the name, item type (itemType, also copied to type), free flag, developers, publishers, release date, coming soon flag, prices, genres, platforms, required age, plain-text languages, DLC count, and the store URL. Free games have null prices because price_overview is null. Unreleased apps keep comingSoon: true.
Search hits include price, metascore, platforms, controller support, and image. Featured rows include section (top_sellers, new_releases, specials, coming_soon), rank, discount, and prices. Player rows are appId, playerCount, and checkedAt.
Failed lookups are rows, not a crashed run: NOT_FOUND when Steam says success is false, or HTTP_ plus the status after retries.
| Field | Type | Description |
|---|---|---|
recordKind | string | review, summary, app, search, featured, player_count, or error. |
appId | integer | Steam app id. |
reviewId | string | Recommendation id. Duplicates are dropped. |
text | string | Review text. |
playtimeForeverHours | number | Lifetime hours. |
itemType | string | game, dlc, app, bundle, summary. Alias type is also on the row. |
priceFinal | number | Current price in currency units, or null if free. |
playerCount | integer | Players online at checkedAt. |
errorCode | string | Set on error rows. |
Limits
- 10,000 dataset rows per run (
maxItems). - Review requests ask for 100 reviews. Steam caps the page there.
- Store search returns about 10 results and has no page parameter.
- App details are slow (about 1.5 to 2 seconds each in the check on 2026-10-12) and reject
appids=730,570. - The public GetAppList route is retired (HTTP 404). IStoreService GetAppList returns 403 without a Steam Web API key, so this actor does not call it.
FAQ
Do I need a Steam API key? No. Reviews, app details, store search, featured categories, and current players are public. A key is only required for the full app catalog, which this actor does not call.
Why do two runs show different review totals for the same game?
The summary is tied to reviewLanguage and reviewFilter. all languages and english are different populations. Later pages do not repeat the summary block.
Why does search only return about 10 games? That is the store search endpoint. It is not a full catalog. Run several terms, or pass known app ids into reviews or app details.
Can this export every Steam app? Not without your own Steam Web API key, and that endpoint is outside this actor. Pass the app ids or store URLs you care about.
What happens when an app id is wrong or missing in a country?
You get an error row with NOT_FOUND or HTTP_ and a status. The other apps still run.
Trademark Notice
Steam and Valve and related names, logos, and trademarks belong to their respective owners. Their use in this documentation is solely to identify the source of the data and does not imply affiliation, sponsorship, endorsement, or partnership.
Disclaimer
This Actor is an independent tool and is not affiliated with, endorsed by, sponsored by, or otherwise officially associated with Steam and Valve.
Is web scraping legal?
Collecting information that is already public is generally legal. Scraping is not the same thing as hacking, and there is no single law that bans it. The limits are the usual ones: do not break into accounts, do not take private or confidential data, and be careful with personal data and copyrighted works. A site's terms can also restrict how you access it. Facts such as a public name, price, or rating are not the same thing as republishing someone's article or photo.
This actor reads public pages or official public APIs. It does not log in and it does not bypass access controls.
This is not legal advice. For the longer explanation, see Apify's article Is web scraping legal?.