Your Steam review score affects everything -- visibility, trust, whether someone actually clicks "Add to Cart." A bad score is hard to recover from, and a good one compounds over time. I've watched games with identical quality levels sell wildly different numbers of copies, and the difference often came down to how well they managed their reviews.
This guide covers how to manage reviews without doing anything shady -- and what to do when things go sideways.
Why reviews matter more than you'd expect
Reviews hit your game in several ways, and most of them aren't obvious until you're staring at a sales graph wondering what happened.
Steam's algorithm uses review scores as a quality signal. Higher scores mean more impressions in discovery queues, search results, and recommendations. Drop below 70% positive and your visibility takes a real hit. For a full breakdown of how these signals interact, see our guide on how Steam's algorithm works. The short version: the algorithm treats your review score as a proxy for "should we show this game to more people?" A score that dips below certain thresholds can quietly cut your traffic in half without any notification from Valve.
Players also check reviews before buying. Research on app stores suggests that a single star improvement can lift conversion by 25-30%. Steam reviews work the same way -- the gap between "Mixed" and "Mostly Positive" is enormous for whether someone actually buys. If you're already working on your store page optimization, review management is the other half of that equation.
And then there's the trust factor. Players trust other players more than they trust your trailer or your store page description. Positive reviews lower the "is this worth my money?" anxiety. Negative reviews amplify it. A strong capsule image might get someone to click, but reviews are what get them to buy.
Understanding review metrics
Steam has two review scores, and they don't carry equal weight.
Recent Reviews covers the last 30 days. The algorithm weights it more heavily, and it's shown more prominently to shoppers. This is the number that matters most for your day-to-day sales. If you shipped a bad patch three weeks ago and your recent score tanked, that's what players see when they land on your page -- not your lifetime average.
All Reviews is the lifetime score. It matters for overall credibility, but it's slower to move in either direction. Think of it as your game's permanent record. A strong lifetime score gives you a buffer when things go wrong; a weak one means every bad patch hits harder.
The score badge changes based on how many reviews you have. With 0-9 reviews, there's no visible score at all -- you're basically invisible in terms of social proof. At 10-49 reviews, your score becomes visible and starts influencing purchase decisions. Once you hit 50+, Steam displays "Recent Reviews" separately if it differs from the overall score.
Getting past 10 reviews fast matters a lot for early credibility. This is one reason why building a wishlist audience before launch is so valuable -- those early buyers are your most likely reviewers. If you're planning a Steam Next Fest demo, that's a prime opportunity to build relationships with players who'll be ready to review on day one.
The thresholds that actually matter
Not all review percentages are created equal. Steam uses specific thresholds to assign rating labels, and crossing one of these boundaries changes how your game looks to shoppers.
Below 20% positive, you're tagged as "Overwhelmingly Negative." Between 20-39% is "Very Negative," and 40-69% is "Mixed." That "Mixed" label is where a lot of indie games end up, and it's a painful spot -- it's not bad enough to be a meme, but it's bad enough that cautious buyers skip you entirely.
At 70% you hit "Mostly Positive," and this is the threshold I think about most. Going from 69% to 70% doesn't sound like much, but it changes your visible label and signals to the algorithm that your game is worth recommending. It's the difference between "risky purchase" and "probably fine."
80% gets you "Very Positive," and 95%+ earns "Overwhelmingly Positive." Each jump makes a meaningful difference in wishlist conversion rates, but the 70% and 80% thresholds are where I've seen the biggest impacts on actual sales.
Responding to negative reviews
You will get negative reviews. Every game does. How you handle them matters more than the reviews themselves.
The first thing to figure out is whether a response is even worth it. Respond when the review contains a legitimate bug report, when the player has a misconception you can clarify, when the feedback could help future players make informed decisions, or when you've already fixed the issue they mentioned. That last one is underrated -- going back to old negative reviews after a patch and saying "hey, we fixed this" sometimes gets the reviewer to update their rating.
Don't respond when the review is abusive or in bad faith, when you'd be arguing or getting defensive, when there's nothing constructive to add, or when you're emotional. Especially that last one. I've seen developers tank their reputation with a single angry response written at 2 AM. If you're frustrated, close the tab and come back tomorrow.
When you do respond, acknowledge the issue first: "Thanks for flagging the difficulty spike in Chapter 3." Then give them something useful: "We've added difficulty options in the latest patch that might help." If you're working on a fix, say so: "We're tracking this and working on improvements for the next update."
The main rule: never argue, insult, or dismiss. Even if the review is unfair, your response is public. Every future player who reads that thread will judge you by how you handled it.
Here's what a good response looks like in practice. Say someone writes: "Game keeps crashing on my hardware. Can't even play for 10 minutes." A solid response would be: "Sorry you're experiencing crashes. We've identified some AMD driver issues -- could you try updating to the latest drivers? If that doesn't help, please report your specs in our support forum and we'll investigate directly." That works because it acknowledges the problem, offers a concrete solution, gives a clear next step, and shows you're actually paying attention.
Responding to positive reviews
Positive reviews deserve attention too, but the approach is different. You don't want to come across as a bot that replies "Thanks for the kind words!" to every single review.
Keep responses brief. A short thank you is enough most of the time -- long responses to positive reviews can feel performative, like you're performing gratitude for an audience rather than actually engaging. "Thanks for playing! Glad you enjoyed the boss fights" beats a three-paragraph essay about your development journey.
Where positive review responses get interesting is when you can highlight something specific. If a player mentions a feature you're proud of, lean into it: "Happy you discovered the secret ending -- took us ages to design that sequence!" This does double duty: it rewards the reviewer and signals to anyone reading that there's more content to discover.
One thing I'd avoid: don't reply to every positive review. If someone scrolls your review page and sees identical "Thanks!" responses on twenty reviews in a row, it looks automated. Pick the ones that say something interesting and engage with those.
And never -- seriously, never -- ask players to update their review or add more detail. It looks desperate and it violates Steam's guidelines.
Encouraging positive reviews (without being sketchy)
You can't buy, incentivize, or manipulate reviews. Valve bans games for this. But you can make it easy for happy players to leave reviews on their own, and there's nothing wrong with that.
The best time to remind players about reviews is at natural emotional peaks. After completing the game, after achieving something significant, in your credits or end screen -- these are all moments where a player is feeling good about their experience. A gentle prompt works well here: "If you enjoyed the game, a review helps other players discover it." That's it. No begging, no pressure.
Fixing bugs quickly is one of the best review strategies nobody talks about. Every unresolved bug is a potential negative review. Quick patches show players you care and give them less reason to leave a bad review in the first place. I've seen games flip from "Mixed" to "Mostly Positive" after a single well-communicated patch that addressed the top complaints.
Community building matters here too. Players who feel connected to your development process are more likely to leave positive reviews. Regular updates, honest communication, and actual engagement with your community all help. This doesn't mean you need to be on Discord 24/7 -- it means when you post an update, it should sound like a human being wrote it, not a PR department.
When you ask for feedback, keep the wording neutral: "If you have thoughts on the game, we'd appreciate a review." That encourages reviews without specifically asking for positive ones. The distinction matters to Valve.
Timing is everything with review prompts. Don't ask during frustrating gameplay moments, right after a bug, or before the player has meaningfully experienced the game. Ask after satisfying moments, after you've fixed a reported issue, or when the player just had a great experience. A well-timed ask at the right emotional moment is worth ten poorly-timed ones.
Dealing with review bombing
Review bombing is when a large number of negative reviews hit your game in a short period, usually driven by something other than the game itself. Maybe you said something controversial on social media. Maybe a popular streamer had a bad experience and their audience piled on. Maybe a platform decision (like adding DRM or removing a feature) triggered backlash.
It's one of the most stressful things that can happen to a game developer, and your first instinct -- to fight back, to argue, to explain -- is almost always wrong.
Steam introduced a review bombing detection system in 2019 that can identify and filter "off-topic review activity." When Valve detects a review bomb, they mark those reviews as off-topic and exclude them from your review score. This doesn't happen instantly, though. It can take days for Valve to investigate and apply the filter, which means your score might crater in the short term before it recovers.
Here's what to do if it happens to you. First, don't panic when you see the graph crater. Seriously. The worst thing you can do is make an emotional public statement while the bombing is happening. Take a breath.
Second, contact Steam support. Let them know what's happening and why you believe it's a review bomb rather than legitimate feedback. Provide context -- links to social media threads, streamer videos, whatever triggered it. The more evidence you give them, the faster they can act.
Third, if the bombing is tied to a legitimate grievance (you removed a popular feature, added aggressive monetization, etc.), you need to honestly evaluate whether the criticism has merit. Review bombs driven by actual product decisions aren't always "unfair" -- sometimes players are telling you something important in the loudest way they can. In that case, the right move might be to address the underlying issue rather than waiting for Valve to filter the reviews.
While you wait for the situation to resolve, keep communicating with your community through Steam announcements. Be transparent about what's happening without being combative. Something like: "We're aware of the recent review activity and we're working with Steam to ensure our review score accurately reflects player experience." Stay calm, stay professional, and let the system work.
The good news is that review bombs are usually temporary. Even without Valve's intervention, the wave typically passes within a week. Your Recent Reviews score will recover as new legitimate reviews come in. The players who actually love your game haven't gone anywhere.
Review recovery strategies
If your score has dropped, you can recover. It takes work, but it's doable -- and I've seen games make the climb from "Mixed" to "Very Positive" over a few months.
Start by actually reading your recent negative reviews and looking for patterns. Complaints usually cluster around a few themes: technical issues (bugs, performance), expectation mismatches (your store page description promised something different from what the game delivered), content problems (too short, too hard, missing features), or specific design decisions that aren't landing with players. Once you know what's actually wrong, you can fix the right things instead of guessing.
Fix the root cause. Don't just try to drown out negative reviews with positive ones. One solid patch that addresses the top three complaints is worth more than any amount of review prompting. Players can tell the difference between a developer who listens and one who's just trying to game the score.
Then tell people you fixed it. When you ship a fix, announce it through Steam announcements and update logs. Respond directly to relevant reviews: "Update 1.2 addressed the performance issues several of you mentioned. Give it a try and let us know if it helps!" This serves two purposes -- it might get some reviewers to update their ratings, and it shows anyone reading old reviews that you're actively supporting the game.
Focus on your recent score. Since recent reviews are shown prominently, fixing current issues improves your visible score faster than your overall average would suggest. This is actually good news if you've had a rough stretch -- it means you can turn things around relatively quickly. A focused two-week push on the biggest complaints can meaningfully shift your Recent Reviews label.
If your problems were partly caused by mismatched expectations -- players expecting a different kind of game than what you made -- revisit your store page. Your description, screenshots, and capsule art should set accurate expectations. It's better to have fewer sales with higher satisfaction than lots of sales followed by refunds and negative reviews. Speaking of which, your pricing plays into this too -- price too low and players assume the game is low quality; price at the right point and you attract players who are more likely to appreciate what you've built.
What not to do
These will backfire or get you banned. I've seen developers try all of them.
Incentivizing reviews -- offering in-game items, discounts, or other rewards for reviews -- violates Steam's guidelines. Valve will remove the reviews and may ban your game entirely. It doesn't matter if you're only asking for "honest" reviews; the incentive itself is the problem.
Review brigading is just as bad. Coordinating groups to leave positive reviews or downvote negative ones is obvious and punishable. Valve has seen it all before, and their detection systems are better than you think.
Creating fake accounts to review your own game is detectable. Valve's systems catch this, and the punishment is severe. Don't do it. Don't let your friends do it from their accounts either -- patterns of behavior from connected accounts get flagged.
Public arguments with reviewers make you look bad no matter who's right. If you need to resolve something, take it to support channels. The audience watching a developer argue with a reviewer is never rooting for the developer.
Mass-flagging negative reviews is for abusive content, not reviews you disagree with. Abusing the report system gets you flagged as a bad actor with Valve, which is the opposite of what you want.
Long-term review strategy
There's no clever hack here. The best long-term review strategy is making a good game and supporting it after launch. I know that's not the magic answer anyone wants, but it's the truth.
Ship something polished. Every bug you fix before launch is a negative review you never have to deal with. Use your store page checklist to make sure everything is tight before you go live -- mismatched expectations between your store page and your actual game are one of the biggest drivers of negative reviews.
Keep supporting the game after release. Developers who stick with their games build up positive review momentum over time. Each update is a chance to turn a critic into a fan, and each patch note is a reminder to satisfied players that the game is still alive. There's a reason that review count correlates strongly with revenue -- engaged developers build engaged communities, and engaged communities leave reviews.
Build relationships, not just a product. Players who feel involved in the development process will go to bat for you naturally. They'll argue with negative reviewers in the comments (so you don't have to), recommend the game to friends, and leave detailed positive reviews that convince other buyers. That kind of organic advocacy is worth more than any marketing spend.
And when things go wrong -- they will -- be honest about it. Players forgive a lot when they feel like you're being straight with them. A developer who says "we messed this up, here's how we're fixing it" earns more goodwill than one who pretends everything is fine while the review score slides.
Frequently asked questions
How many reviews do I need before my score matters?
You need at least 10 reviews before Steam displays a score at all. But realistically, you want 50+ before your score stabilizes and "Recent Reviews" appears as a separate metric. Below 50, a single negative review can swing your percentage by several points. Focus on getting those early reviews by building a wishlist audience before launch through events like Steam Next Fest.
Can I get a negative review removed?
Only if it violates Steam's terms of service -- things like hate speech, spam, or content that's clearly not about the game. You can't get a review removed just because it's unfair or inaccurate. If you believe a review violates the rules, flag it through Steam's reporting system and let Valve make the call. Don't abuse the system by flagging every negative review, though.
My game has a "Mixed" rating. How long does it take to recover?
It depends on how many total reviews you have and how quickly you're getting new ones. Since Recent Reviews only covers the last 30 days, you can shift that label in a few weeks with a good patch and some communication. The All Reviews score takes longer -- if you have 500 reviews at 65% positive, you'll need a sustained run of positive reviews to push past 70%. Fixing the root issues players are complaining about is the fastest path.
Do review scores affect how Steam promotes my game during sales?
Yes. Steam's algorithm considers review scores when deciding which games to feature in discovery queues, sale pages, and recommendations. A higher score means more visibility, which means more sales, which means more reviews -- it's a virtuous cycle. Conversely, a low score limits your reach. This is why reviews aren't just a vanity metric; they directly impact your revenue.
Your review score isn't just a number -- it's the single biggest factor in whether a browsing player becomes a paying one. Start by auditing your current reviews for patterns, then make a plan to address the top complaints.
Check your store page with our Capsule Validator and Screenshot Checker to make sure your visuals are setting the right expectations. Curious how reviews translate to actual revenue? Try our free Revenue Calculator to see how any game's review count maps to estimated sales. Then read up on Steam store page optimization, writing a strong description, and pricing strategy to tighten the full experience.
Browse our genre-specific optimization guides for strategies tailored to your game type, and check the Steam Page Leaderboard to see how top games optimize their store pages.