A Steam Next Fest demo is often the first time thousands of strangers play your game in a single week. For a small team, that week can shape wishlists, press interest and publisher conversations for months. It is also easy to burn by shipping a demo that crashes on launch, runs badly on mid-range hardware or ends before players see what makes the game special.
This is the checklist we walk through with teams in the four to six weeks before a festival demo goes live. It assumes a PC build on Steam, but most of it applies to any public demo.
1. Lock the date math first
Next Fest runs a few times a year, and Valve publishes the registration deadlines and press preview window well ahead on the Steamworks site. Work backward from those dates, not from the festival start:
- the demo needs its own store presence and review before the festival, so build in time for Valve's review and at least one fix-and-resubmit cycle,
- the press and creator preview period starts before the public week, so "feature complete" really means a week or more earlier than the festival,
- if your team is spread across US time zones, agree on one clock for the deadline (Pacific time is a sensible default for Steam dates).
2. Decide what the demo is for
A demo that tries to show everything usually shows nothing well. Pick one goal and cut the slice to fit it:
- Wishlists: the first 10 to 15 minutes should hit the core loop and one memorable moment.
- Publisher or investor interest: stability and a clear sense of scope matter more than length.
- Feedback on a mechanic: instrument it and ask for feedback in game, not only on the Discord.
End the demo on a high point with a clear wishlist prompt, not at an arbitrary level boundary.
3. Test on hardware that looks like your players', not your dev machines
Developer PCs are usually far above the median. Before submission, run the demo on:
- an older mid-range GPU and a CPU with fewer cores,
- a laptop with integrated graphics,
- a machine with a non-US keyboard layout and a non-English Windows locale, if you can borrow one,
- a Steam Deck, if you plan to claim Deck support anywhere.
Check that the default graphics preset picks something playable on first launch. Many festival players will quit before they ever open a settings menu.
4. Make the first two minutes bulletproof
Most players decide whether to keep going within the first few minutes. Walk the first launch as a brand new player, with no config files and no save data:
- no black screen longer than a few seconds without a loading indicator,
- the game launches in a sensible window mode on multi-monitor setups,
- controller and keyboard prompts match the device actually in use,
- audio does not blast at full volume on the first menu,
- skipping the intro does not soft-lock anything.
5. Run a regression pass on every build you upload
Festival weeks tend to produce hotfixes, and hotfixes are where regressions sneak in. Keep a short, written pass you run on every uploaded build, even a one-line fix: boot, new game, the full demo path, save and reload, quit and relaunch. We keep a free patch-day regression checklist for exactly this, and it works just as well for demo builds as for live patches.
6. Set up crash reporting and basic telemetry before launch day
You will not be able to reproduce most of the crashes players hit. Make sure the demo build:
- ships with a crash reporter that captures the build number, GPU and driver version,
- logs a few anonymous funnel events (launched, finished tutorial, reached the end of the demo, clicked wishlist) so you can see where players drop off,
- discloses any data collection in line with your privacy policy.
7. Prepare the store page and the build together
The demo, the store page and the trailer should tell the same story. Before submitting, check that:
- capsule art is legible at small sizes, since festival lists show tiny thumbnails,
- the first screenshots show real gameplay, not menus or concept art,
- system requirements match what you actually tested in step 3,
- supported languages listed on the page are fully localized in the demo, or not listed.
8. Plan the festival week itself
Decide in advance who is on call for crashes, who answers Steam discussions and who handles creator requests, and in which time zones. If you plan a livestream, test the streaming setup in a private session first. Agree on a rule for hotfixes, for example "crash and progression fixes only, everything else waits until after the festival".
When to bring in extra hands
Small teams often have the design and content in good shape but lack the hours for hardware testing, performance work and store-page polish in the final month. That is a reasonable point to bring in an outside PC game development team for optimization, QA passes or porting work, so the core team can keep building the game itself.
Juego Studios is a game development studio. This checklist reflects the prep we do with our own teams; adapt it to your engine, team size and festival timing.
Top comments (0)