79.65% of this 2024 cohort
stayed below 50 reviews.
14,084 paid Steam games released in 2024, analysed one by one. 200 cases scored in detail, 100 read in depth. What the public data reveals about low review activity, page features and the questions a studio can investigate next.
14,084 games.
11,218 invisible.
Of the 14,084 paid games released on Steam in 2024 (English supported, excluding demos/soundtracks/tools), 79.7% finished with fewer than 50 reviews after at least twelve months. 56.6% of the entire cohort didn't even pass nine reviews.
Only 1,411 games — one in ten — reached 200+ reviews, the threshold this study uses as a viable comparison group.
SOURCE: SHYPIARD STUDY, N=14,084, Z02Z/FRONKON DATASET (STEAM/STEAMSPY)
In 84 of 100 cases,
reach or activity led the diagnosis.
Of the 100 cases read in depth (10 to 49 reviews), 84% were classified primarily around distribution/reach or post-launch velocity. The reading identifies a question to investigate; it does not prove why the game received few reviews.
Distribution and reach
46/100 cases
Post-launch velocity
38/100 cases
Positioning and promise
8/100 cases
Reception and expectation fit
7/100 cases
Steam page conversion
1/100 cases
Three numbers. Three concrete levers.
This study isn't a report to read — it's the diagnostic Shypiard applies to every studio. Here's exactly what we do about each of these three findings.
Full launch strategy → · METHOD: 14,084 GAMES (COHORT) · 200 SCORED CASES · 100 CASES READ IN DEPTH — ASSOCIATIONS, NOT PROVEN CAUSES
A separate 2026 corpus — 100 low-review vs 100 high-review, plus 100 survival games — lives in Shypiard Research →
WHAT THE DATA HELPS YOU DO
The problem to check. The next action. The budget to scope.
Recommendations below are a first investigation, not a claim that every gap needs fixing. Game examples describe the dated evidence; their intervention costs remain unknown unless disclosed.
Language coverage: choose a reachable audience before adding languages
What could be wrong
A language barrier may keep suitable players from understanding the promise or playing comfortably. A low language count alone does not show that your game has this problem.
How to investigate and improve it
- Export the page text and game strings separately. Count source words and identify interface, subtitles and audio needs.
- Choose one priority language from player requests and the audience you can reach. Translate a small playable slice and the page consistently.
- Have a fluent tester check the build, fonts and UI. Scope the remaining game text and future updates before commissioning more languages.
What other games tend to show
Five or more languages appear on 87/100 high-review pages versus 20/100 low-review pages. Broader support is common in that selected group; the single-language exceptions keep it from becoming a requirement.
15 supported languages in the 17 August 2026 row.
Spending on this specific intervention is not disclosed in the corpus.
One supported language and 31,400 recorded reviews: a boundary case for mandatory localization.
Spending on this specific intervention is not disclosed in the corpus.
Budget · Translation scenario: $0.10 per source word / language
A published Loten Labs rate provides a planning reference. At that assumed per-language rate, 1,000 words in one language = $100; 10,000 words in four = $4,000. Confirm the language pair and service scope with a quote.
Initial internal labour: €300–€6001–2 person-days × your chosen rate. Editorial first-pass estimate: String inventory and a pilot review, excluding full implementation. External purchases are separate.
Translation-only planning calculator
$100 translation scenario
Rate is editable. No currency conversion or addition to the EUR labour line; integration, QA, voice and tax are excluded.
How to check whether it helped
Record the localized build/date, language-specific feedback and qualified visits. Compare equivalent campaign periods; a before/after change is not automatically a translation effect.
These are supplier-based scenarios, not the budgets of the example games. Integration, linguistic QA, audio, tax and future text changes require their own scope.
Screenshots: make the gallery explain the experience
What could be wrong
A short or repetitive gallery may leave progression, interface or the main activity unclear. Eight images are a comparison threshold, not evidence that a visitor understands them.
How to investigate and improve it
- List the distinct things a player should understand: core loop, progression, environments and supported social play.
- Capture representative moments from the current build. Replace repeated scenes before adding filler to reach a number.
- Ask unfamiliar target players to describe the game from the gallery. Revise the scenes they misread.
What other games tend to show
At least eight screenshots appear on 82/100 high-review pages, 59/100 low-review pages and 89/100 survival pages. Their quality and effect on conversion were not measured.
Seven screenshots in the snapshot despite 264,694 recorded reviews.
Spending on this specific intervention is not disclosed in the corpus.
Twelve screenshots coexist with 32 reviews. Asset count did not establish reach.
Spending on this specific intervention is not disclosed in the corpus.
Budget · Internal first pass
No new vendor purchase is required for an internal recapture. The team's time is still a cost. New environments or gameplay features are outside this first pass.
Initial internal labour: €150–€3000.5–1 person-days × your chosen rate. Editorial first-pass estimate: Capture and gallery review using an existing playable build. External purchases are separate.
How to check whether it helped
Use a comprehension test first, then review qualified store visits and wishlist activity over comparable periods. Log which images changed.
Do not build new game content just to fill the gallery. A count cannot explain sales.
Achievements: support the loop when the implementation earns its cost
What could be wrong
An absent feature is a completeness question, not proof of a launch weakness. Generic achievements can consume development and QA time without clarifying the appeal.
How to investigate and improve it
- Decide whether milestones fit the game's progression and the audience's expectations.
- Scope a small implementation spike: unlock rules, API integration, save migration and regression checks.
- Ship only milestones that can be tested reliably. Keep this behind missing gameplay clarity or measured reach issues.
What other games tend to show
Achievements appear on 93/100 high-review pages and 68/100 low-review pages. They are frequent, but several highly visible games omit them.
No achievements recorded, with 31,400 reviews.
Spending on this specific intervention is not disclosed in the corpus.
No achievements recorded in the August snapshot, with 540,159 reviews.
Spending on this specific intervention is not disclosed in the corpus.
Budget · Internal first pass
Start with internal discovery. Budget the actual unlock systems, platform integration and QA from the game's architecture instead of borrowing an industry flat price.
Initial internal labour: €150–€3000.5–1 person-days × your chosen rate. Editorial first-pass estimate: Design and integration spike; shipping scope still needs an engineering estimate. External purchases are separate.
How to check whether it helped
Check unlock correctness and player feedback after release. Do not infer extra purchases from the feature's presence.
The first-pass labour estimate excludes full engineering and regression work. Absence can be a deliberate product choice.
External website: give players and creators a useful next destination
What could be wrong
A site can support a press kit or player information, but its presence is not proof of distribution. A separate site may be unnecessary if the existing destinations serve the need.
How to investigate and improve it
- Identify the missing job: press assets, build access, support, or a clear campaign destination.
- Use the simplest maintainable page with approved assets and working links.
- Tag campaign links and keep the information consistent with the Steam page.
What other games tend to show
Website presence differs in the older 2024 observatory. That association does not measure what the sites contain or whether visitors use them.
Budget · Internal first pass
Reuse existing hosting if suitable. New hosting, a domain and external design require current quotes and renewals; the corpus does not record those costs.
Initial internal labour: €150–€3000.5–1 person-days × your chosen rate. Editorial first-pass estimate: Press-kit or simple landing-page scope. External purchases are separate.
How to check whether it helped
Track useful visits and asset downloads with consent where required. Judge the site by the job it serves.
Do not commission a new site solely to match a feature-frequency gap.
Multiplayer: a product choice, not a checkbox to buy
What could be wrong
The prevalence of multiplayer among one group can tempt a team to expand the product without evidence that its players need it.
How to investigate and improve it
- Validate whether social play is central to the intended experience.
- Prototype the actual session and list networking, authority, matchmaking, QA and support requirements.
- Estimate that architecture before committing. Keep the single-player promise if it already fits the audience.
What other games tend to show
The older observatory records multiplayer presence as a feature association. It does not compare the same game with and without multiplayer.
Budget · Internal first pass
Shipping multiplayer needs a game-specific engineering and operating-cost estimate. This small first pass is not a multiplayer implementation budget.
Initial internal labour: €300–€6001–2 person-days × your chosen rate. Editorial first-pass estimate: Feasibility and audience discovery only. External purchases are separate.
How to check whether it helped
Use prototype playtests, session reliability and intended-player demand. Model ongoing support and service costs explicitly.
There is no defensible flat multiplayer budget or guaranteed reach gain in these data.
Low visibility: test qualified exposure before buying a large campaign
What could be wrong
A polished, well-liked game can still have little recorded activity. Public reviews cannot separate too few visits, the wrong visitors or poor conversion.
How to investigate and improve it
- Collect the Steam traffic and campaign evidence you can access; write the audience hypothesis first.
- Build a small creator shortlist around actual gameplay and a playable build. Use dated UTM links for the experiment.
- Compare qualified visits and wishlists before scaling spend. Negotiate sponsorships by deliverables, audience fit and usage rights.
What other games tend to show
Favorable reception occurs in both outcome groups, and creator history is missing on 95/100 rows on each side. The corpus cannot give a creator-campaign success rate or a standard sponsorship price.
A highly positive low-volume row shows why reception does not establish reach.
Spending on this specific intervention is not disclosed in the corpus.
A complete page coexists with a low review count; the detailed case supplies context missing from the aggregate.
Spending on this specific intervention is not disclosed in the corpus.
Budget · Internal first pass
Start with research and direct outreach time. Paid placements need channel-specific quotes; spend is not disclosed consistently enough to publish a market average here. Do not treat free outreach as free labour.
Initial internal labour: €300–€6001–2 person-days × your chosen rate. Editorial first-pass estimate: Audience hypothesis, a small shortlist and measurement setup. External purchases are separate.
Valve: UTM analyticsHow to check whether it helped
Compare the same campaign's qualified visits, attributable wishlists and subsequent activity. Steam UTM only attributes eligible tracked visits and can miss cross-device behavior.
No reach diagnosis or expected return is inferred solely from review count. Set any paid test cap from your own budget.
Early Access and updates: make the current build and next commitment clear
What could be wrong
Players may be asked to buy a future promise without a clear view of what works now. An update checkbox cannot tell you whether a roadmap is credible or a project is maintained regularly.
How to investigate and improve it
- Describe the playable scope, known limitations and next deliverable in concrete terms.
- Review a timeline of announcements against actual builds and feedback. Separate current Early Access status from the game's release history.
- Estimate one achievable milestone and support workload. Announce a cadence the team can maintain.
What other games tend to show
In the survival snapshot, 31 games are currently in Early Access and 37 have an observed Early Access date. Updates appear on 29/31 current-EA pages and 69/69 released pages; presence does not measure cadence.
Its official update 25 notes describe new onboarding options and accessibility-related changes, an example of naming concrete player-facing work.
The cost of that update is not published in this source.
Current Early Access in the August row; read it as a historical status, not today's live badge.
Spending on this specific intervention is not disclosed in the corpus.
Budget · Internal first pass
Cost the milestone as people × working days × your loaded day rate, then add testing and support. The page/roadmap review is a small first pass, not the cost of finishing a survival game.
Initial internal labour: €300–€6001–2 person-days × your chosen rate. Editorial first-pass estimate: Build-state audit and one milestone scope; development cost remains to estimate. External purchases are separate.
Valve: Early Access expectationsHow to check whether it helped
Measure whether promised work shipped, recurring player issues and response after each dated update. Do not equate more announcements with more traffic.
Released games may have used Early Access. Current status medians do not estimate the effect of choosing Early Access.
Positioning: make a specific player promise testable
What could be wrong
A broad genre label can attract expectations the game does not meet. Survival, for example, includes very different activities and social modes.
How to investigate and improve it
- Write one sentence naming the activity, the intended player and the distinctive payoff.
- Choose comparisons around mechanics, session structure and supported modes, then review their opening promise.
- Test the pitch with unfamiliar target players and change the page where expectations diverge.
What other games tend to show
The survival corpus mixes 86 Survival, 12 Open World Survival Craft and two Extraction primary-family entries. This coarse coding does not make the games interchangeable audiences.
An Open World Survival Craft comparison needs a specific activity and mode check.
Spending on this specific intervention is not disclosed in the corpus.
A survival comparison should be inspected for actual loop and audience, rather than matched only by label.
Spending on this specific intervention is not disclosed in the corpus.
Budget · Internal first pass
Begin with a copy and audience audit. Copywriter fees, player recruitment and new product features need separate scopes.
Initial internal labour: €300–€6001–2 person-days × your chosen rate. Editorial first-pass estimate: Promise, comparisons and comprehension test. External purchases are separate.
How to check whether it helped
Ask what players expect to do and compare that with the playable build. Track expectation mismatches in feedback.
Two Extraction entries are too few for a genre-wide price, demand or conversion estimate.
Review score: separate happy reviewers from a large audience
What could be wrong
An attractive percentage can conceal very little evidence. Negative themes can also reveal unmet expectations, but a score alone cannot identify the defect or the audience mismatch.
How to investigate and improve it
- Read the count alongside the percentage and inspect the actual review themes.
- Compare the page promise with what players say they received. Reproduce reported issues before deciding whether to change the build or the pitch.
- Test with additional relevant players. Keep positive reception and qualified audience growth as separate measures.
What other games tend to show
Thirty low-review games have ≥90% positive reviews. Their median is 30 reviews, versus 74,188 within the 82 highly positive high-review games. Current-EA survival reception has a 66% median versus 85% for released games; these groups are not matched.
49 recorded reviews at 94% positive: encouraging reception with low observed volume.
Spending on this specific intervention is not disclosed in the corpus.
Budget · Internal first pass
First budget analysis time. Participant compensation and the engineering work needed for any reproduced issue are separate lines; request a specific quote or use your team's rates.
Initial internal labour: €300–€6001–2 person-days × your chosen rate. Editorial first-pass estimate: Review-theme audit and a small test plan. External purchases are separate.
How to check whether it helped
Track issue frequency, reproducibility and feedback from the intended audience. Avoid treating a small percentage change as proof of a fix.
Reviewers are selected players, not a representative survey of everyone who could buy the game.
Missing data: instrument the next decision instead of inventing a diagnosis
What could be wrong
Unknown traffic, wishlists or campaign history cannot be treated as zero. Raw event counts also cannot explain a visitor's motive.
How to investigate and improve it
- Name the decision and the observations that would separate competing explanations.
- Collect permitted aggregate metrics and a dated intervention log. Keep source, denominator and missing values visible.
- Compare like-for-like windows and audience segments. Inspect the last observed errors and transitions before proposing a fix.
What other games tend to show
Only three wishlist declarations appear across the 200 launch rows. The snapshot cannot fill Valve's private counter or reconstruct most creator histories.
A documented public wishlist declaration exists; it is a sourced exception, not an estimate for other games.
Spending on this specific intervention is not disclosed in the corpus.
Budget · Internal first pass
Use available Steamworks reporting rather than buying a guessed counter. Tool subscription, engineering and consent implementation costs depend on the chosen setup.
Initial internal labour: €150–€3000.5–1 person-days × your chosen rate. Editorial first-pass estimate: Campaign links and a minimal measurement plan. External purchases are separate.
Valve: UTM analyticsHow to check whether it helped
Check the report's actual denominator, privacy limitations and data freshness. A missing value should remain unknown.
Shypiard's PostHog reports describe usage of Shypiard. They are not access to a studio's private Steam traffic or wishlist totals.
Release timing: remove practical conflicts before chasing a weekday
What could be wrong
A date may clash with competing releases, campaigns or support capacity. A weekday association cannot establish that your announced date is wrong.
How to investigate and improve it
- Check direct audience competition and announced events in the proposed window.
- Confirm build-review deadlines, team availability, creator access and launch support.
- If the date is flexible, compare realistic windows. Preserve commitments unless there is a game-specific reason to move.
What other games tend to show
Tuesday–Thursday accounts for 73/100 high-review games versus 48/100 low-review games. Friday is 15 versus 29. The comparison is not adjusted for audience, release age or publisher support.
A Friday release in the high-review cohort.
Spending on this specific intervention is not disclosed in the corpus.
A Friday release in the low-review cohort. Matching the weekday does not explain either outcome.
Spending on this specific intervention is not disclosed in the corpus.
Budget · Internal first pass
Changing a planning document can be internal work. A delayed launch can create substantial payroll and opportunity costs; calculate those from your actual team and delay length.
Initial internal labour: €150–€3000.5–1 person-days × your chosen rate. Editorial first-pass estimate: Calendar and readiness review. External purchases are separate.
How to check whether it helped
Track readiness, available support and campaign delivery. Compare launch activity without attributing the result solely to the weekday.
No cohort-based expected return is available for moving a date.
Price: compare a similar offer, then cost the decision
What could be wrong
A missing public price can be normal before release. A low or high observed price is not a measured cause of low review volume, and may reflect a sale rather than launch pricing.
How to investigate and improve it
- Compare the same currency and discount state for mechanically relevant games of similar scope.
- Consider the current playable value, support commitment and actual studio costs.
- Review the Steamworks pricing schedule and announced offer before changing a public commitment.
What other games tend to show
The older observatory uses observed prices, potentially discounted. Its price-band frequencies are not a price experiment or a forecast of profit.
Budget · Internal first pass
A price review is internal work; changing the price affects future revenue and needs a studio-specific model. Do not count a price cut as a free marketing fix.
Initial internal labour: €150–€3000.5–1 person-days × your chosen rate. Editorial first-pass estimate: Comparable-price and offer review. External purchases are separate.
How to check whether it helped
Track units, net revenue, discounts and refund context with studio data. Public reviews alone cannot establish profitability.
The corpus cannot supply the game's development budget or break-even price.
Know where you stand
before you release.
The free launch diagnostic applies this reading grid to your game. The automated launch check scans your Steam page in seconds.