There are exactly two ways to get more Steam reviews: sell more copies, and raise the fraction of buyers who bother to write one. The typical rate is about 1 review per 30 sales (the working range is 20-60), and the tactic most developers reach for first — an in-game popup asking players to review — is explicitly against the written Steamworks rules.
That second part surprises people, so I checked the Steamworks review documentation directly on July 2, 2026, and the line is still there: “Don’t ask customers to review your product from within your application.” The rest of this post covers the asks that are still allowed, plus the review-rate math that tells you whether your numbers are normal and how many sales each label gate really costs.
What Valve’s review policy actually says
The developer rules in the Steamworks docs are short. The relevant lines, quoted:
- “Don’t solicit reviews in exchange for any games, DLC, money, or other rewards.” The one exception Valve names is sending copies to press or internet personalities for previews or coverage.
- “Don’t ask customers to review your product from within your application.”
Valve’s stated reasoning is that they “don’t see customer benefit from individual developers or games soliciting reviews from customers.” Steam handles the asking itself: the client prompts players to review games they have spent time in. That built-in prompt matters more than it sounds. Gamalytic’s sales-to-review analysis found that when Steam started prompting players in 2019, the sales-per-review ratio roughly halved. Players already get asked. Your job is to make sure the answer is a thumbs up, and to put your own asks in the places the rules leave open.
One honest caveat: enforcement of the in-app rule is inconsistent. You can find shipped games with “leave a review” buttons on their main menus that have never been penalized. But the rule is written down, Valve has removed a developer’s entire catalog from Steam over review manipulation, and the upside of an in-app popup over an announcement-post ask is small. I would not spend my store page’s credibility on it.
The forbidden list
Everything on this list is either quoted from the Steamworks docs or falls under their catch-all ban on attempting to “artificially manipulate” the review system:
| Tactic | Status | Why |
|---|---|---|
| Paying for reviews | Banned | Direct manipulation; this is the case Valve built detection for |
| Reviews in exchange for games, DLC, or rewards | Banned | Quoted prohibition in the docs |
| In-game prompt asking for a review | Banned | “Don’t ask customers to review your product from within your application” |
| Asking specifically for a positive review | Banned | Solicitation plus sentiment steering; treated as manipulation |
| Key giveaways to farm reviews | Pointless since 2016 | Key-activated reviews are visible but excluded from the score |
| Review-for-review swaps with other devs | Banned | Coordinated inflation, same category as paid reviews |
| Neutral ask in patch notes, update posts, Discord, socials | Not prohibited | Outside the application, no incentive, no sentiment steering |
| Responding to reviews as the developer | Allowed | Official feature; the docs just warn against arguing with customers |
The logic behind the table is simple. Incentives are out, and so is anything that steers sentiment or happens inside the game itself. An uncompensated, neutral ask made outside your application is not on the forbidden list, and it is how nearly every indie studio does this in practice.
“Enjoyed the game? A positive review helps us a lot!” fails two rules at once if it appears in-game, and one rule anywhere else. Drop the word “positive” from every ask you write. Ask for honest reviews or just “a review,” nothing more specific.
Why keys and giveaways cannot buy you a score
This one has been settled for a decade. In a September 12, 2016 announcement, Valve found “at least 160 titles” with suspiciously better scores among key activators and changed the system: reviews from Steam key activations remain visible on the page but no longer count toward the review score. The change moved the score category of about 14% of games overnight, and roughly 200 titles lost their label entirely until real purchasers reviewed them.
The practical consequence for you: only direct Steam purchases feed your percentage. Press keys, Kickstarter backer keys, giveaway keys, curator copies — all of those players can write reviews, and shoppers can read them, but none of them move the number that prints your label. If your launch plan involves thousands of keys, your review score still depends entirely on the people who paid. Our review score thresholds guide covers the full nine-label grid and which reviews get counted or excluded.
Your baseline: the Steam review rate per sale
Before optimizing anything, know what normal looks like. The commonly used exchange rate between reviews and sales, the Boxleiter multiplier, runs 20-60 sales per review, with ~30x the common middle for 2023+ releases. The genre-by-genre breakdown lives in our review to sales multiplier post; use it in reverse and you get your expected review rate: roughly 1.5-5% of buyers review, ~3.3% typical.
Gamalytic’s 2023 deep dive put numbers on what moves that rate. The strangest finding is that review rate is not linear with quality:
Games people love get reviewed (players advocate). Games people hate get reviewed (players warn). Games in the middle get silence. A ~70% positive game needs about twice the sales per review of a 90% game. If your game lands at “pretty good,” your review count grows at half speed, which delays every label gate below.
The same analysis found a few other levers worth knowing:
- Playtime predicts reviews. The longer someone plays, the more likely they review. Games that hold players for long sessions accumulate reviews faster per sale.
- Free games earn about half the review rate of paid games per unit — roughly twice as many “sales” per review. Free demo downloads follow similar logic: huge numbers, thin review conversion.
- Deep discounts depress the rate. Bargain buyers review less; one heavily discounted game in the dataset managed 1 review per 1,000 players.
None of these are things you can game after launch. They are reasons to plan review expectations by genre and price before launch, which is exactly what the multiplier table is for.
Legal ways to raise your review rate
Given the constraints, here is what actually works, ranked roughly by effect for effort:
Make the game end on a high note, and update it. The Steam client prompts active players. Every patch that pulls lapsed players back in re-exposes them to that prompt with more playtime on the clock. This is the boring compounding engine behind games whose review counts keep climbing years after launch.
Ask in your update posts. A patch announcement is read by your most engaged players at the exact moment you have given them something. One neutral line at the end (“if you’re enjoying the update, a Steam review genuinely helps small teams”) is outside the application, uncompensated, and sentiment-neutral. Steam events and announcements also trigger visibility rounds, so the same post that asks for reviews brings back the players who can write them.
Ask in your community hub, Discord, and socials. A pinned community hub post explaining what reviews do for a small studio converts a slow trickle of your warmest audience. Same rules apply: no incentives, and keep the word “positive” out of the ask.
Respond to reviews, sparingly. Developer responses are an official feature. Use them on the most-helpful negative reviews to say “fixed in 1.2,” never to argue. The docs specifically warn against using responses to refute customer opinions. A visible pattern of fixes changes what future reviewers write. The full playbook, including crisis response, is in our review management guide.
Fix what the negative reviews name. Sort negative reviews by helpfulness and count complaint categories. The top two usually cause most of the damage. Patching them is the only tactic on this list that changes sentiment rather than volume.
Chris Zukowski lists “giving up before your first ten reviews” among his 60 game marketing mistakes. Below 10 reviews you have no label at all, just “Need more user reviews to generate a score.” If you are past launch and stuck at 6 reviews, the highest-value marketing task you have is getting four more.
Timing the ask: when players actually review
You cannot put a prompt in the game, but you control when your out-of-game asks land, and timing is most of the battle:
| Moment | Why it converts |
|---|---|
| Launch week | Highest emotional engagement your game will ever have; the first 10 reviews decide whether you get a label at all |
| Right after a content update | Players just received value; announcement reaches owners directly |
| After a player finishes the game | Completion posts, achievement-linked community threads; these players have the most playtime and the most to say |
| During a festival or sale spike | New buyer cohort arrives; your announcement feed is being read by strangers |
| Never: months of silence, then an ask | An ask with no accompanying value reads as begging and converts terribly |
The common thread is reciprocity. Every effective ask rides on something you just gave the player. A standalone “please review us” post with nothing attached gets ignored.
The sales math behind each label gate
Review count gates are really sales targets wearing a disguise. Steam’s label thresholds are community-documented rather than official, but they have held stable for years: a first label at 10 reviews, Very Positive eligibility at 50, Overwhelmingly Positive eligibility at 500. Run those through the ~30x multiplier:
Three planning consequences fall out of that chart:
- Your first ~300 sales are worth disproportionate marketing effort, because sale number 300 is the one that typically prints a label on your page and unlocks every review-score filter on Steam.
- Very Positive is a realistic first-year target for a modestly successful indie (~1,500 units), and it is the label shoppers treat as “safe purchase.”
- Overwhelmingly Positive is a volume gate. At ~15,000 units required, most Steam games are mathematically locked out regardless of quality. Do not plan around it.
These are estimates built on a multiplier with a wide range: a chatty community can hit 50 reviews on 1,000 sales, a quiet one might need 3,000. To model your own gates with your actual review count and percentage, run the numbers through our free review score calculator; it tells you how many positive reviews you need to reach or defend each label.
Your review plan, start to finish
The whole post as a checklist you can execute:
- Before launch: set expectations with the multiplier table for your genre and price. Know your sales target for 10 and 50 reviews before day one.
- Launch week: one goal — 10 counted reviews from real purchasers. Ask once in your launch announcement and once in your Discord. Neutral wording, no incentives.
- Weeks 2-8: patch fast, and end every patch note with one quiet ask. Respond to the top negative reviews with fixes, not arguments.
- Ongoing: check your recent score monthly, watch which complaints repeat, and treat each label boundary (70%, 80%) as a milestone with real conversion money attached. The thresholds post has the math for climbing out of a band.
- Never: pay, incentivize, swap, prompt in-game, or use the word “positive” in an ask. Every path Valve has closed was closed because it worked briefly for someone else.
If you want to know how your current label, review velocity, and store page work together, run your page through the free Steam Page Analyzer. It reads the review signals shoppers see and ranks the fixes by impact.