Steam Next Fest demo QA checklist (February 2027)

52 checks for a Steam Next Fest demo: first launch, the first 30 minutes, controls, the wishlist screen, saves, hardware and Steam Deck, performance, localization and store hygiene. 52 checks, free, with the February 2027 timeline.

For PC studios taking a demo to Steam Next Fest in February 2027. Tick items here (they stay saved in this browser), print the list, or hand the link to whoever plays the demo last before you submit.

From Jumbo Jelly, a PC game QA studio led by JJ (Jean Jarques), with 25+ releases shipped.

Your timeline, counted back from the fest

DateMilestoneWhat should be true by then
Now to 27 December 2026Content lockDemo scope is final. From here you fix, you do not add.
28 December to 10 January 2027Registration (deadline 10 Jan, 23:59 PST)Registered on Steamworks, demo app created and linked to the main game.
Early to mid January 2027Outside QA passFresh eyes on hardware you do not own, with time left to fix what they find.
18 January 2027Build and store page for Press PreviewRelease candidate uploaded and store page submitted; Valve pulls trailers from this date.
1 February 2027All required elementsLast call for the demo build, store assets and event details.
11 February 2027Press and creator previewTreat it as launch day: the build they play is the build they write about.
22 February to 1 March 2027Steam Next FestWatch reviews, Discord and crash reports daily. Hotfix owner on call.

Dates from the Steamworks page for the February 2027 edition (partner.steamgames.com, accessed 27 October 2026). Check it before you rely on them; the June 2027 edition runs 14 to 21 June with registration by 25 April. The week-by-week plan is in the article “Steam Next Fest February 2027: 8-week demo QA plan”. Week by week: Steam Next Fest February 2027: 8-week demo QA plan.

0 of 52 done

Ticks are saved in this browser only (localStorage), nothing is sent anywhere.

1. First launch and settings

Why it matters: If the demo crashes or looks wrong in the first 10 seconds, most players will not give it a second try.

2. First 30 minutes

Why it matters: Next Fest players try many demos in a short time. The opening decides whether you get a wishlist.

3. Controls and input

Why it matters: Players feel bad controls within seconds; the team stopped noticing them months ago.

4. End of demo and wishlist screen

Why it matters: The end of the demo is your best moment to ask for a wishlist. A freeze or a bare main menu wastes it.

5. Saves

Why it matters: Lost progress turns a curious player into an annoyed one, and a broken save can follow them into the full game.

6. Hardware and Steam Deck

Why it matters: Your players do not have your dev machine. The Steam Hardware Survey shows a wide spread of GPUs, CPUs and screens.

7. Performance

Why it matters: Stutters and long loads show up in reviews and creator videos, where everyone can see them.

8. Localization

Why it matters: Next Fest brings players from many countries. Broken text in their language reads as a broken game.

9. Store page and build hygiene

Why it matters: A solid demo still loses players to a wrong branch, a stale build or an empty store page.

Want a second pair of eyes before you submit?

Getting through all of this on several PCs, with fresh eyes, takes real hours your team is spending on the game. A Smoke Test (€290, one tester, 8 hours, report in 2 business days) covers the first 30 minutes, settings and controls on hardware you do not own. The Launch Health Check (€590) adds a second tester, a Team Lead and around 30 hours. Best booked in early January, so fixes land before the review deadline.

See the Smoke Test, €290 Book a 30-min call

Shipping updates after the fest? See the free Patch day QA checklist.

Last updated 2026-10-27 · Written by , founder of Jumbo Jelly.