Skip to content
Overheard

How to get feedback on your Steam demo

Published · Numbers as of

15%of 906 problems we found in Twitch streams of indie games came up in more than one stream of the same game

Use more than one source, because each one hears from different players. Steam reviews, your Discord and a survey come from players who stayed long enough to have an opinion. Steam's playtime numbers tell you that people stop, not why. Streams of your demo show the moment a player gets stuck, in their own words, including the players who quit and never write a review.

Expect each source to show you a few players at a time. In 259 Twitch streams of 46 indie games, only 15% of the 906 problems we found in a game came up in more than one of its streams.

Five sources, and what each one misses

Where feedback on a Steam demo comes from. Steam features as described in Steamworks, checked 7 Oct 2026.
SourceYou hear fromIt tells youIt misses
Steam reviews of the demoplayers who chose to write onea verdict and a few reasonsplayers who quit early, and the exact moment something went wrong
Your Discord, a survey in the demoyour most engaged playersanswers to the questions you askeveryone who didn't care enough to join or reply
Steam Playtest or recruited testersplayers you let insessions you choose, and testers you can ask follow-up questionsplayers you didn't pick, and it takes your time to run
Playtime in Steamworkseveryone who launched the demothat players stop, and roughly whenwhy they stopped
Streams and videos of your demostreamers who picked your demo themselveswhere they got stuck or had fun, said aloud, with the minute in the videoa follow-up question. They play for their audience, and a Twitch VOD expires after 7 to 60 days

Steam reviews and your own channels

Players of a demo can leave Steam user reviews on it, separate from the full game (Steamworks: Demos). Read them in one sitting after the fest and write down the reasons, not the verdicts: “didn't know where to go” is something you can fix, “not for me” usually isn't.

A survey when the demo ends or a feedback channel on your Discord lets you ask exactly what you want to know. You hear from the players engaged enough to answer, so ask about the moment they almost stopped: the players who did stop are the ones you won't hear from.

Steam Playtest and recruited testers

Steam Playtest is free. Players sign up from your game's store page and you let them in, in batches or all at once. A playtest has no store page of its own, and a player who only took part in it can't review your game (Steamworks: Playtest). It suits a build you aren't ready to show everyone. With recruited testers, paid or from your community, you can watch a session and ask about it right after, so use them for the things the other sources raise but don't explain.

Playtime: that players stop, not why

Steamworks shows how long players spend in your demo. As a reference, Chris Zukowski collected median playtimes from developers of 130 demos in 2022, and the median across them was 14 minutes (How To Market A Game). A short median tells you to look for a reason. To find it, you need to see a player in the minutes before they stop, which is what the next source gives you.

Streams of your demo

A stream is a playtest you didn't have to organise: a player who picked your demo, thinking aloud, recorded. This is what the streams of one game look like once every moment is marked:

  • Stream 1, 1h analysed: 29 problems, 4 suggestions or comparisons, 5 highlights.
  • Stream 2, 1h analysed: 11 problems, 1 suggestion or comparison, 1 highlight.
  • Stream 3, 1h analysed: 16 problems, 2 suggestions or comparisons, 2 highlights.
  • Stream 4, 46 min analysed: 26 problems, 5 highlights.
  • Stream 5, 1h analysed: 23 problems, 1 suggestion or comparison, 5 highlights.
  • Stream 6, 1h analysed: 24 problems, 3 suggestions or comparisons, 3 highlights.
Show moments:
6 streams of ORMOD: Directive (game page)

From all the streams we analysed:

  • Streamers keep running into things late in a session. Only 16% of 615 moments of confusion came in the first quarter of the part we analysed, and 32% in the last. A review written after ten minutes can't tell you about those.
  • The largest group of problems, 23% of 906, was unclear rules, controls and item effects: things the game never explained (what streamers struggle with most).
  • 36% of the streams were not in English. Those players run into problems too, but you won't hear them unless someone translates (indie game streams that aren't in English).
  • Streams show what players enjoy too, at the minute it happens, which tells you what not to cut (what streamers praise in indie games).

The work is finding the streams and watching them before they expire: start with how to find Twitch streams of your game, then what to note while you watch.

How to put them together

  1. During the fest, keep a list of the streams of your demo, with the day and the channel.
  2. In the week after, watch them in the order their VODs expire and write one line per problem, with the minute (after Next Fest: from streams to a fix list).
  3. Read the reviews and your Discord, and mark which problems they confirm. Add the ones streams didn't show.
  4. Check playtime: if the median is short, look for a problem that comes up in the first minutes of the streams.
  5. Fix first what shows up in two or more places, and any crash or lost save even if only one player hit it.

How we counted

The stream numbers come from our game pages: 259 Twitch streams of 46 indie games, analysed in the week of 21 Sept 2026, up to 8 streams per game. A speech model transcribes the part where the game was on screen, and a language model marks moments of confusion, frustration, bugs and praise, each backed by a quote. A problem counts as repeated when the same problem came up in two or more streams of one game. The Steam features are described from the Steamworks documentation, checked 7 October 2026.

What this doesn't tell you

  • Our streams are of games streamed often enough for us to analyse at least 3 streams, mostly not of small demos. A demo with one or two streams gives you fewer chances to see a problem twice.
  • We don't have data on reviews, surveys or playtime. Those rows of the table describe what each source is, not how well it works.
  • The playtime figure is from 2022 and from developers who chose to share theirs.

The numbers come from our own data, counted by a script on the date above. Overheard is run by Mateusz Woskowicz, an independent developer in Poland.

Demo in the October Next Fest?

Overheard finds the Twitch streams of your Steam game or demo and tells you where streamers got stuck, what broke and what they liked, each with a link to the minute in the VOD. Send us the Steam page: we email you when enough streamers have played it, and you decide then whether the $49 report is worth it.