Steam Next Fest February 2027 runs from February 22 to March 1. Your demo build is due for review on January 18 if you want it in Press Preview. That gives a studio reading this on October 27 about 83 days to a QA-ready build, and the year-end holidays eat into them. The plan below works backwards in weeks, from content lock to the 48 hours after the fest closes.
What are the Steam Next Fest February 2027 dates?
Valve has published every February 2027 deadline on the edition’s Steamworks page (Steamworks docs, accessed 27 Oct 2026). The June 2027 dates come from its June 2027 page (Steamworks docs, accessed 27 Oct 2026). The “days before” column is simple arithmetic from each fest’s start.
| Milestone | February 2027 | Days before fest | June 2027 | Days before fest |
|---|---|---|---|---|
| Valve Q&A on Zoom | Dec 8, 2026 | 76 | date TBD (March) | n/a |
| Registration deadline | Jan 10, 11:59pm PST | 43 | Apr 25, 11:59pm PDT | 50 |
| Trailers pulled for official trailer | Jan 18 | 35 | May 3 | 42 |
| Demo + store page submitted for Press Preview | Jan 18 | 35 | May 10 | 35 |
| All required items submitted for review | Feb 1 | 21 | May 24 | 21 |
| Press Preview opens | Feb 11, 10am PST | 11 | Jun 3, 10am PDT | 11 |
| Fest opens | Feb 22, 10am PST | 0 | Jun 14, 10am PDT | 0 |
| Fest closes, Wrap-Up goes live | Mar 1 | +7 | Jun 21 | +7 |
Some third-party calendars show different submission dates for February. Treat the Steamworks page as the only source, and check it again in December. For the tasks behind each row, the Next Fest demo QA checklist gives you 52 checkable items with these deadlines. Progress is saved in your browser.
Why does the QA plan start from January 18 and not February 22?
January 18 is the first date where a broken build costs you something you cannot buy back. Miss it and journalists get no playable demo when Press Preview starts on February 11. Valve’s general Next Fest documentation (Steamworks docs, accessed 27 Oct 2026) also warns about build review. It only checks that the game runs and has the promised features. In Valve’s words, it “will not catch or even look for most bugs.” For a full release the same reviews take 3 to 5 business days per round, and our Steam review timeline shows how far ahead to submit.
So a passed review tells you very little about the build players will download. The stakes are real. In 2021 Valve reported a 1,364% jump in median daily wishlist additions during Next Fest, compared with the two weeks before. The figure was summarised by Game Developer (Game Developer, accessed 27 Oct 2026). A June 2026 survey of developer data on How To Market A Game (accessed 27 Oct 2026) put the median play-to-wishlist conversion at 19.3%. A crash in the first minute removes a player from that 19.3% before they see your best scene.
The calendar adds pressure. December 24 to January 1 falls inside weeks 9 and 8 before the fest, when most small teams are offline. In practice content lock has to happen before Christmas, so release candidate 1 can be tested in the first week of January.
If the team has no QA of its own, an 8-hour smoke test on that release candidate returns a prioritised bug report in 2 working days. That still leaves a week to fix before January 18.
What should you test each week before Next Fest?
The table counts weeks back from February 22, 2027. Dates are Mondays. The “build” column says which version of the demo should be under test that week.
| Week | Dates | Steam milestone | Build under test | What to test, and why |
|---|---|---|---|---|
| T-8 | Dec 28 | holidays | content-locked demo | Full playthrough of the demo slice; lock scope so later weeks fix bugs instead of adding features |
| T-7 | Jan 4 | registration Jan 10 | release candidate 1 | Clean-machine install, first launch, settings persistence, store page facts vs build |
| T-6 | Jan 11 | trailers pulled, review Jan 18 | release candidate 2 | External test on hardware you do not own; Steam Deck pass; fix only blockers |
| T-5 | Jan 18 | demo submitted for Press Preview | submitted build | Install the exact build from Steam on a fresh account; log the build ID |
| T-4 to T-3 | Jan 25, Feb 1 | all items due Feb 1 | patch candidates | Regression pass on every fix; re-check the store page review |
| T-2 | Feb 8 | Press Preview Feb 11 | live demo | Monitor press and early players; keep a hotfix branch ready |
| T-1 | Feb 15 | trailer launches about 4 days prior | live demo | Final regression, server or backend load if the demo is online |
| Fest | Feb 22 to Mar 1 | demo live 30+ min early | live demo | Crash reports, demo reviews, one person on call for hotfixes |
| After | Mar 1 to Mar 3 | Wrap-Up goes live | live demo | Triage everything players reported; decide what carries into the full game |
Weeks T-8 and T-7: lock content, then test the first ten minutes
If you are still choosing between a demo and a closed test, our Steam Playtest vs demo vs beta branch table shows why only the demo counts for Next Fest. Content lock at T-8 means the demo slice stops growing. Every new feature after this point is a new source of bugs with less time to find them. Test the first ten minutes hardest, because that is where most demo players decide whether to keep going.
Week T-6: put the build on someone else’s hardware
This is the week for a fresh pair of eyes on release candidate 2. Your team knows the controls, the save path and the one menu that needs a double click. A tester who does not will hit those problems in the first hour. Use different GPUs, a laptop and a gamepad, and fix only what blocks play.
Weeks T-5 to T-3: test what Valve will actually ship
Once the build is submitted, test the version Steam delivers. Install it from Steam on an account that has never run the game. Note the build ID in every bug report, so nobody fixes a problem that only existed in an older upload. Each fix then gets a regression pass before it goes back to review. Hotfixes in this window tend to break the thing next to them.
Weeks T-2 and T-1: the demo is public, treat it like a launch
Press Preview opens on February 11. Valve notes that press can play any demo that is already live. From here, every build change is a patch to a public product. Keep a hotfix branch, a named owner for crash reports and a rule for what is worth patching mid-fest.
What breaks first in a Next Fest demo?
The list below comes from Valve’s published requirements for demos and Steam Deck, plus failure types that developers discuss publicly. Read it as a list of risks to test. It carries no frequency data.
- Crash on first launch. A missing runtime, an antivirus false positive or a shader compile that hangs on older GPUs. Developer machines already have everything installed, so test on a clean Windows install.
- Settings not saved. Resolution, volume or key bindings reset on the next launch. Check where the demo writes config and saves, and whether it collides with the full game’s folder.
- Wrong controller prompts. Steam Deck’s compatibility checklist (Steamworks docs, accessed 27 Oct 2026) requires on-screen glyphs to match the active input. Keyboard icons on a gamepad session read as unfinished.
- Steam Deck basics. The same checklist asks for a playable default at 30fps at 800p and text readable at 30 cm. A demo does not need the Deck Verified badge, but Deck players will try it during the fest.
- Text input without a keyboard. Naming a character or a save file on a handheld needs the on-screen keyboard to appear.
- A dead end at the demo’s last screen. Valve’s demo documentation (Steamworks docs, accessed 27 Oct 2026) suggests linking the full game from the demo menu. Check that the link opens the right store page. Then check that the end screen does not soft-lock.
- Store page promises the build does not keep. Languages, controller support and Deck claims on the page must match the demo. If they do not, the first reviews will say so.
What do you do in the 48 hours after the fest opens?
The first two days decide what your demo reviews say, since players can review a demo separately from the full game. Steamworks recommends setting the demo live at least 30 minutes before the fest starts, so you can catch a broken depot before the traffic arrives.
- Read crash reports and new demo reviews every few hours on February 22 and 23.
- Patch only blockers: crashes, soft-locks, lost saves and broken input.
- Run a short regression pass before every upload, then confirm the new build ID is the live one.
- Post a short changelog on the store page so players see the fix.
- On March 1, export every report and tag what also affects the full game.
Steamworks also notes that the demo release notification email to wishlisters can be sent only within 14 days of the demo’s launch, and only once. If the demo went live for Press Preview on February 11, that window closes around February 25, during the fest. Send it after your first hotfix has landed.
For the post-fest patch itself, the patch-day QA checklist covers the 34 checks that keep a fix from breaking something else.
Should you move to June 2027 instead?
Move if the demo cannot reach release candidate 1 by the first week of January. A game can enter Next Fest only once, so a rushed February entry uses up the slot. June 2027 runs June 14 to 21, with registration closing on April 25 and the Press Preview build due May 10. The structure is identical, with the same 35 days between Press Preview submission and fest start and the same 21-day final deadline. June costs you four months of wishlists. In exchange, the demo gets a full external test before players download it.