Steam Next Fest: you get exactly one, so spend it well
Steam Next Fest is a week-long event, held roughly three times a year, where unreleased games with playable demos get their own event pages, category listings and front-page real estate. For a game with no audience, it is the one moment Steam hands you the same visibility as a game with 50,000 wishlists.
You get one per game, ever. That is the whole strategic problem.
What it actually does
During the fest your demo sits on event pages that a lot of people browse specifically to find new things. You get category pages, a spot in the fest's own discovery surfaces, and the ordinary Steam machinery of "people who played this also played" working on traffic it would never otherwise see.
The wishlist bump concentrates in the first two or three days and then decays. Games that do well typically report their largest single wishlist week of the entire pre-launch period.
Picking the wrong one is the common mistake
The temptation is to enter the next fest on the calendar because it is soon and momentum feels good. The reasons that backfires:
- A demo that is not fun yet burns the slot. The traffic is real and it is once. If your opening fifteen minutes are rough, you have spent your best visibility showing people a rough opening.
- Too close to launch is also wrong. Valve has rules about how close to release you can participate, and beyond the rules, the point of the fest is to collect wishlists that convert at launch. Collecting them the week before launch leaves no room to act on what you learn.
- Too far from launch and the wishlists cool. People who wishlisted eighteen months ago convert worse than people who wishlisted last month.
The usual advice that holds up: enter when the demo is genuinely good, ideally a few months before you intend to release, and let the release date follow the fest rather than the other way round.
Have these ready before the demo goes live
- A demo that reaches something satisfying inside fifteen minutes. Most people give you far less than that. The drop-off point in your first 48 hours of data tells you exactly where the opening drags.
- A wishlist prompt at the end of a run, not only in the main menu. Ask when they have just enjoyed something.
- Capsule art that reads at thumbnail size. Fest pages are grids of small capsules. See capsule sizes.
- A store page that answers "what is this" in one sentence above the fold, because fest traffic is skim traffic.
- Working crash reporting in the demo build. You are about to get more concurrent players than you have ever had, on hardware you have never seen.
- Somewhere to put feedback so it does not vanish into a Discord scroll. A structured log beats a chat channel.
During the week
Watch two numbers, not one. Wishlists tell you whether the page is converting. Median playtime and where players stop tell you whether the game is. A fest with a big wishlist bump and a five-minute median playtime is a warning, not a win: those wishlists will convert badly at launch because the demo did not actually land.
Reply to every demo review and forum post that week. Fest visitors are unusually willing to talk to developers, and the fixes they hand you are the cheapest playtesting you will ever get.
After
Write down, while it is fresh: wishlists before and after, median playtime, the three places people stopped, and the three things you would change. That note is worth more than the wishlist number itself, because the wishlist number is a result and the note is a cause.
Plan the beats and measure them
Game Marketing Beats Planner - every public moment on one calendar with a wishlist goal before and wishlists gained after, so within a few months the table tells you which beats move the number. Notion. $7.
See it on Etsy