What is a review bomb on Steam?
It is a large number of reviews in a short time, aimed at your score. Valve defines a review bomb as players who post a large number of reviews in a short period of time, aimed at lowering the Review Score of a game. The Steamworks documentation adds that players use it to voice their unhappiness and to provoke a response.
Valve splits bombs into two kinds. An off-topic bomb is about something that Valve considers unrelated to whether a future buyer will enjoy the game. Valve counts DRM and EULA changes as off-topic. A negative wave about the game itself, such as a broken feature or a new bug, is normal feedback.
Firewatch is a well known case. In September 2017, after a public dispute between its developer and a YouTuber, Steam Spy counted 510 negative reviews in a short time, as Polygon reported. Valve added a review history chart to every store page in the same month.
| Kind | Example cause | What Steam does |
|---|---|---|
| Off-topic review bomb | Something outside the game, such as a DRM or EULA change | Valve can leave the whole period out of the review score; the reviews stay readable |
| Negative wave about the game | A broken feature, a new bug or a bad update | The reviews count as normal; the fix is in the game |
Sources: Steam News, User Reviews Revisited (Valve, 15 March 2019); Steamworks User Reviews documentation; Polygon (19 September 2017).
What does Steam do about an off-topic review bomb?
Valve removes the period from the score, not the reviews. A tool flags unusual review activity on every game in close to real time, and a team at Valve then checks the cause. If it is an off-topic bomb, Valve marks the time period, tells the developer, and leaves the reviews in that period out of the Review Score.
Every review in the period is left out, positive ones too, because Valve says it cannot read every review. The reviews stay on the page. The store page says that some reviews are not in the score, and players can choose in their store preferences to count them again. Valve did not apply the rule to bombs before March 2019.
The Steamworks documentation says the surge calms down after a few days. It also says that Valve has not seen a correlation between review bombs and purchasing behavior.
Sources: Steam News, User Reviews Revisited (Valve, 15 March 2019); Steamworks User Reviews documentation.
Does flagging a review remove it from my score?
Only when the review breaks the rules. You can flag a review as Abusive, Off-Topic or Violates Community Guidelines from the moderator controls on the review. You cannot delete reviews yourself. The result depends on what the moderators decide, as the table shows.
Reviews about price, value or business practices are allowed. Valve says reviews reflect the game, its value, the business practices and the community, and that all of this is valid feedback.
| Result | Effect on the review | Effect on the score |
|---|---|---|
| Confirmed as abusive or against the guidelines | Banned and removed from Steam | Removed from the score |
| Marked Off-Topic by a moderator | Lower visibility | Still counts in the score |
| Inside an off-topic review bomb period found by Valve | Stays readable; the period is marked | Left out of the score |
Sources: Steamworks User Reviews documentation.
What should I do in the first days of a review bomb?
Contact Valve, find the cause, stay out of arguments and protect your team. That is the core of Valve's advice.
- Contact Valve by email or through Partner Support. Valve can give you more information and add moderators to watch your discussion hub.
- Find the cause. Read a sample of the new reviews and match the start time with your last build, price change, announcement or public post.
- If a build caused it, fix the build first and post patch notes.
- Flag reviews that are abusive or break the guidelines. Do not flag a review only because it is negative.
- Do not censor or argue with reviewers in public. Valve says it has never seen that stop negative reviews.
- If you post, use an anonymous developer account, so that no one on the team becomes a target.
- Protect the team. Set a time limit for reading reviews, and share the reading among people.
Sources: Steamworks User Reviews documentation.
What if the negative reviews are about a real problem?
Then it is feedback, and the fix is in the game. In its 2017 post, Valve wrote that a score usually recovers after a review bomb. When it did not fully recover, Valve read that as a real issue that also made later buyers less happy.
Fix the problem, ship it as an update, and say so in an announcement. Steam may prompt a player who left a negative review and keeps playing to update the review. Reply to a review only when the reviewer lacks information or hit a bug that you fixed. Valve warns that a developer response often draws more attention than the review itself.
Sources: Steam blog, User Reviews (Valve, 19 September 2017); Steamworks User Reviews documentation.
How do I measure the damage?
Compare daily reviews and daily sales with a baseline from the weeks before. Valve's data says bombs are a temporary distortion on average, but check your own game.
Valve's GetAppReviews Web API returns reviews for a date range. It filters out off-topic review bomb periods by default, and you pass filter_offtopic_activity as false to include them. Each review has voted_up, the author's playtime when the review was written, and a refunded field.
- Pick a baseline: the 28 days before the first day of the bomb, without a sale or a festival. The 28 days is our suggestion.
- Count positive and negative reviews per day for the baseline and the bomb, once with the off-topic filter and once without it.
- Read units sold and returns per day in Steamworks for the same days.
- Check the playtime at review of the new negative reviews. In our reading, many reviews with almost no playtime point to a cause outside the game.
- Compare the 30 day score each week until it is back near the baseline level.
- Steam review score calculator →
- How to analyze your Steam reviews →
- Steam review score tiers: every label and what it takes →
Sources: Steamworks IUserReviewsService documentation; Steam blog, User Reviews (Valve, 19 September 2017); Steamworks User Reviews documentation.
How do I tell a review bomb from a bad build?
Manalens is the analytics and growth engine built for games. Send the build with every event, and read crash-free sessions and errors per session by build on the Game health board. If the latest build is stable and players keep playing, the cause is probably outside the game.
Sources: Manalens product documentation.
Frequently asked questions
Does Steam remove review bombs from the score?
Only off-topic ones. Since March 2019, a Valve tool flags unusual review activity, and a team checks the cause. If the bomb is about something outside the game, Valve leaves that whole period out of the review score. The reviews stay on the page, and players can choose to count them again.
Is a DRM or price complaint an off-topic review bomb?
Valve counts a review bomb about DRM or EULA changes as off-topic. Single reviews about price, value or business practices are still allowed, and Valve calls them valid feedback. The difference is the burst: Valve acts on an unusual change in review volume and sentiment, not on one review.
Should I reply to review bombers?
No. Valve says not to censor or argue with reviewers in public, because it has never seen that stop negative reviews. A developer response often draws more attention than the review itself. If you must post, use an anonymous developer account and keep the post short and factual.
Do review bombs hurt sales?
Valve says it has not seen a correlation between review bombs and purchasing behavior, and its 2017 data showed that scores generally recover. That is an average across Steam. Check your own game: compare daily units and returns during the bomb with a quiet baseline from the weeks before it.
Sources and implementation
- Steam News: User Reviews Revisited (Valve, 15 March 2019) ↗
- Steamworks documentation: User Reviews (Valve, read 18 November 2026) ↗
- Steamworks documentation: IUserReviewsService (Valve, read 18 November 2026) ↗
- Steam blog: User Reviews (Valve, 19 September 2017) ↗
- Polygon: Steam implements histogram to identify review bombings following Firewatch incident (Julia Alexander, 19 September 2017) ↗