Steam Next Fest Demo Feedback: Before, During and After

Steam Next Fest October 2026 opens Monday, October 19 at 10am PDT, which means the next 72 hours decide how much useful Steam Next Fest demo feedback you walk away with. This guide is the plan I would follow if my demo were in the fest right now: a fast cold playtest this weekend, a feedback button that players actually press, a daily loop for reading and patching during fest week, and a way to turn it all into a better demo afterwards. If you missed October, the last section maps the same plan onto February 2027.

The dates and rules that matter this week

I checked these on Valve's Steamworks pages on October 17, 2026. Valve can adjust schedules, so glance at the event page again before you rely on them.

• Fest window: October 19 at 10am PDT to October 26 at 10am PDT. That is 17:00 UTC: noon US Central, 1pm US Eastern, 6pm in the UK.
• Your demo must be live before 10am PDT on October 19. Valve recommends setting it live at least 30 minutes early so you have time to catch problems.
• You can keep updating the demo during the fest. After your demo passes build review once, Valve does not review later updates. Great for hotfixes, but nobody at Valve will catch a broken patch for you.
• Build review is not QA. Valve's own docs say it only checks that the game runs and has the promised features. It will not look for most bugs.
• The wishlist email is one shot. You can trigger the demo release notification to wishlisters once, within 14 days of the demo's first release. If your demo went live recently and you have not pressed it, check your demo's app landing page today.
• Don't run a Steam Playtest at the same time. Valve recommends pushing everyone to the demo during the fest so players are not split across two builds. Our Steam Playtest vs demo guide covers when each one makes sense after the fest.
• One Next Fest per game, ever. Capture every bit of feedback this week.
• Wrap-up: Valve launches a wrap-up page with the most played demos on October 26.

Block out the first few hours after launch on Monday so you can watch for problems live.

This weekend: a 48-hour cold playtest

Chris Zukowski of How To Market A Game puts it bluntly: no demo survives first contact with players, and Next Fest should be your demo's grand finale, not its debut. If your demo has only been played by you, your team and a few friends, this weekend is your last cheap chance to see it through fresh eyes before thousands of strangers do.

You do not need a big study. You need a handful of people who have never seen the game.

1. Find three to six cold players. Not your teammates, not the friend who played every build. Friends of friends, genre communities or other developers all work. If you need channels, the how to find playtesters guide lists the ones that reliably produce testers.
2. Give them the exact build Steam players will get. Same build, same settings, clean install. Bugs hide in first-run code paths.
3. Watch the first 15 minutes, live or recorded. Ask them to talk out loud. Don't explain anything. Every time you want to say "oh, you need to press E", write it down instead. That is a fix.
4. Note where they stop or stall. The moment someone puts the controller down, opens a menu looking for help, or says "so what am I supposed to do?" is gold.
5. Ask three questions at the end. What would you tell a friend this game is? What was the most frustrating moment? Would you wishlist it, and why or why not?

You can also post the demo build on Get Playtests right now. It's free, with no credit card and no identity check. Players browse the open playtests, pick the games that interest them, and send written, video or livestream reviews. Video and livestream reviews are especially handy for a demo because you watch someone's real first session. Reviews that arrive during or after the fest feed straight into the post-fest round below. If you are brand new, your first posting may wait until a review you write for someone else's game is approved. That review-first rule is what keeps reviews coming for every game on the site, yours included.

What to fix before Monday, and what to leave alone

You have two days, so be ruthless. Fix things that stop people from playing or understanding the game. Leave everything else for after the fest.

Fix now:

• Crashes on launch, in the first minutes, or on common hardware
• Softlocks and places where players can get stuck with no way forward
• Missing or wrong control prompts, especially for controller players
• A first objective that two or more cold testers could not find
• A missing feedback button or wishlist link (see below)

Leave for later:

• Balance tuning that is "a bit off" rather than broken
• New content, new levels, new systems
• Refactors, engine upgrades, save format changes

Every change you make this weekend is a change nobody has tested. Small, targeted fixes only.

Put a feedback button where players can see it

Valve's own Next Fest tips tell developers to put a link to submit feedback on the demo's home screen, in the main menu, the pause menu, or both. One developer who shared their Next Fest learnings on r/gamedev said a two-click feedback form on the main menu and pause menu brought in a flood of comments that helped them catch bugs and improve the design. The pause menu catches players on the way out, right when they know why they are leaving.

Here is how to set it up quickly:

1. Pick one destination. A short Google Form, a Steam discussion sub-forum, a Discord channel or a bug tracker. One place is easier to read every day than four.
2. Add the build number automatically. If your engine lets you open a URL with parameters, pass the demo version into a hidden or prefilled form field. When you patch on Wednesday you will need to know which reports came from Monday's build.
3. Keep the form tiny. Three to five questions, most of them optional. Long forms get abandoned.

A short demo form that works well during a fest:

• What made you stop playing just now? (optional)
• Was anything confusing or broken? Where?
• How far did you get?
• Did you wishlist the game? Why or why not?
• Anything else you want to tell us?

If you want more question ideas for longer playtests, the playtest survey questions guide has a full bank organized by what you are trying to learn.

Two more things for your demo's home screen

• Say when the demo goes away, if it does. Valve notes that many players download demos during the fest to play later, so tell them on the home screen if you plan to deactivate it. Valve also encourages leaving demos up after the fest, which I would do. Late players are still feedback.
• Link to your store page. Valve's demo docs explain how to use the Steam overlay to open your full game's store page from inside the demo. Put that link on the end screen so players who just finished can wishlist in one click.

Set up the places where feedback will land

Even with a button, players will post feedback wherever they already are. Prepare those places before Monday so nothing gets lost.

• A demo feedback sub-forum on Steam. Valve's tips suggest creating a sub-forum in your base game's discussions for demo feedback. Pin a thread called something like "Demo bugs and feedback" with a short template: what happened, what you expected, your hardware, the build number from the main menu.
• Your Discord. Make one channel for demo feedback and one for bugs, and link both from the demo. Pin the same template.
• Demo user reviews. If you enabled a separate store page for your demo, Valve's docs note that players can leave user reviews on it. Read them every day. They are short, blunt and very honest.
• Videos and streams of your demo. Search Twitch and YouTube for your game's name each evening. A stranger playing with no help from you is one of the best playtests there is. Note the timestamp every time they hesitate, die unexpectedly or misread something.

During the fest: a daily feedback loop

Next Fest is a week long, which is enough time for two or three improvement cycles if you work in small loops. Bugnet's guide to Next Fest bug reports makes the same point: check daily, not weekly, because a problem you fix on day two improves the experience for everyone who plays on days three to seven.

Here is the loop I would run every morning:

1. Collect. Pull everything from the last 24 hours into one document: form responses, forum posts, Discord messages, demo reviews, notes from streams you watched.
2. Tag each item. Use a small, fixed set of tags: crash or bug, confusion, difficulty, wants more, performance, praise.
3. Count. How many separate people mentioned each issue? Repeats from different players matter far more than one passionate post.
4. Pick one or two fixes. Choose the issues that stop people from playing or understanding the game and that you can fix safely today.
5. Test the fix on a clean install. Remember that Valve will not review the update. Install the patched demo fresh, play the first 15 minutes and the area you changed.
6. Push and announce. Post a short Steam announcement: what you heard, what you fixed, thanks to the players who reported it.

That last step is underrated. In an r/IndieDev thread of Next Fest tips from the player side, one commenter said they had bounced off demos assuming the jank was permanent, and that a "we fixed that" announcement is what pulls them back.

Reading fest feedback without overreacting

Fest players are trying lots of demos, so their feedback is blunt and fast. Useful, but easy to overreact to.

• Watch behaviour over opinion. "I quit at the second boss" plus "I quit at the second boss" plus a stream where someone quits at the second boss tells you more than ten comments about art style.
• Use a threshold. If three or more separate players report the same thing, treat it as real. One report is a note to watch for.
• Separate demo scope from design. "Too short" and "I wanted more" are good problems. They mean the demo worked. Don't rush new content into a live demo because of them.
• Look for the first stall. Most demo feedback, positive or negative, traces back to the first five minutes.
• Respond, don't argue. Thank people, ask one follow-up question if needed, and move on.

What to patch mid-fest, and what not to

Safe to patch during the fest:

• Crash fixes and softlocks
• Clearer tutorial prompts, tooltips and objective text
• Number tweaks to an obvious difficulty spike
• Default settings, like a brighter default gamma or a different default sensitivity
• Performance quick wins you can verify yourself

Risky during the fest:

• New mechanics or content
• Changes to save files or progression
• Anything you can't fully test on a clean install in under an hour

Streaming your own demo

Livestreaming is optional. If you do stream, Valve suggests turning broadcast chat on by default. Keep a notes file open and write down every chat question that hints at confusion. Those are your next tutorial fixes.

After October 26: turn the week into a better demo

The fest ends, but the feedback doesn't. Players who downloaded your demo during the week will keep playing it, especially if you leave it up.

1. Collate everything into one list. Merge your daily tags and counts, sorted by how many players hit each issue.
2. Pick the top five issues. Not twenty. Five you can actually fix in the next build.
3. Ship an updated demo and say so. A Steam announcement with "here is what you told us and what we changed" gives returning players a reason to try again.
4. Run a fresh round with new players. The point of fixing things is checking that the fix worked. Get a new group of people who never played the fest build, ideally a similar size to your weekend round, and watch whether they still stall in the same spots. You can post the updated demo on Get Playtests for this round too.
5. Write down what you learned about your players. Which games did people compare yours to? Which moments did they clip? That is your launch marketing copy.

Missed October? Plan for February 2027

Valve lists the next editions as February 22 to March 1, 2027 and June 14 to 21, 2027. Each game only gets one Next Fest, so use the time to arrive with a demo that has already been tested hard.

Valve's general workback timeline says to submit your demo for build review about five weeks before the fest if you want it live for the Press Preview, and about three weeks before at the latest. For February 22 that means roughly mid January and the start of February. Check the February 2027 edition page for the exact dates.

Working back from that, a feedback plan could look like this:

• November and December: share a rough demo and run small cold playtests every week or two. Five to eight fresh players per round is plenty to find the big problems.
• Early January: freeze features and do a final cold round on the exact build you'll submit, feedback button included.
• Mid January: submit for build review and release the demo publicly so you can collect feedback and ship hotfixes before the fest.

That makes Next Fest the grand finale: the week you show off a demo players have already helped shape.

Your Next Fest feedback checklist

Before Monday, October 19:

• Demo live at least 30 minutes before 10am PDT
• Cold playtest with three to six fresh players on the exact Steam build
• Launch crashes, softlocks and first-objective confusion fixed
• Feedback button on the main menu and pause menu, capturing the build number
• Wishlist link on the end screen and a pinned feedback thread on Steam

Every day of the fest:

• Collect, tag, count, fix one or two things, test on a clean install, patch, announce
• Watch at least one stream or video of a stranger playing

After October 26:

• Pick the top five issues, ship an updated demo, announce what changed
• Run a fresh round on the new build with players who never saw the fest version