SteamStats vs SteamDB: public Steam data or your own Steamworks reports

SteamDB is an independent site that tracks public data on Steam apps: player counts, price history, app changes, sales and patch notes. SteamStats reads one studio's own Steamworks reports with its key, so it shows that studio's wishlists, sales, refunds and payouts, refreshing sales every 4 h on Indie and every 60 min on Studio and Publisher.

Last reviewed · SteamStats team

What each one does

SteamDB and SteamStats, checked 1 November 2026
QuestionSteamDBSteamStats
Where the data comes fromThe Steam network through SteamKit and Steam's update system, store pages, and some outside sources for historyThe studio's own Steamworks reports through Valve's partner API, plus public Steam pages, on Indie, Studio, and Publisher
Which gamesApps and packages across SteamThe studio's own games, plus comparable games' public figures in Market
Concurrent playersFrom Steam's API, with chartsFor the studio's games every 15 min on Indie and every 5 min on Studio and Publisher, against the usual range for that weekday and hour
Prices and salesA price table and price graph on every app page, sale pages and upcoming sale datesThe game's own discounts next to Steam's seasonal sales and the cooldown before the next discount
ReviewsThe SteamDB rating, which pulls games with few reviews toward the middleStore label, buffer before the label drops and the SteamDB rating, every 45 min on Indie and every 10 min on Studio and Publisher
Wishlists, units sold, refunds, payoutsNot in Steam's public dataFrom the studio's Steamworks reports: wishlists every 60 min on Indie, Studio, and Publisher, sales and refunds, net to studio and payout dates
AffiliationNot affiliated with Valve or SteamNot affiliated with Valve or Steam
PriceNot listed in the pages checkedRadar is free for one game; Indie is $29.00 per game a month; Studio is $79.00 per game a month

The SteamDB column comes from SteamDB's own FAQ and rating article. Steamworks sales and wishlist reports belong to the partner account, which is why a public tracker does not show them.

When SteamDB is the better choice

  • Looking at any game on Steam, including competitors, without connecting an account.
  • Price history and past discounts of other games, which helps set a price or a discount depth.
  • App and package change history, patch notes and the release calendar.
  • Player count charts for games a studio does not own.

When SteamStats is the better fit

  • Questions only a studio's own reports answer: wishlists today, units and refunds, what reaches the studio after Steam's share and withholding, and when the next payout lands.
  • A forecast of the game's net revenue to year end and over its first year, checked against actual sales every day.
  • Alerts for the studio's own games: wishlist spikes, sales outside the expected range, review labels close to changing.
  • A team view of several games, with every day counted in the organization's own time zone.

Using both

The two answer different questions. SteamDB shows what anyone can see about any game; SteamStats shows what only the studio can see about its own. SteamStats also shows the SteamDB rating next to the store score, using SteamDB's published formula, so the two review numbers can be compared on one screen.

Sources