Blog

Steam Next Fest: the mistakes that waste your only shot

Steam Next Fest happens three times a year. Each edition runs for about a week, featuring hundreds of free demos. For an unreleased indie game, it's the single best opportunity to build wishlists fast.

And you only get to do it once per game.

That's the part most devs don't internalize until it's too late. You register, you put up your demo, the week happens, and then it's over. No retries. No "next time." If you waste it, you wasted it.

Mistake #1: registering too late

Valve opens registration roughly 5-6 weeks before each Next Fest. The deadline is hard. Miss it and you're out until the next edition, which might be 4 months away.

I've seen devs on Reddit who had their demo almost ready, forgot to check the registration dates, and missed the window by three days. Four months of waiting because they didn't set a calendar reminder.

5-6 weeks

Typical registration window before each Next Fest

Valve publishes the schedule twice a year. The dates for H1 come out around December. H2 around June. There's no excuse for not knowing when registration opens. Set the reminder the day the dates are announced.

Mistake #2: the demo isn't ready

"Ready" doesn't mean "the full game but you can only play level 1." Ready means: it launches without crashing, runs at acceptable framerates on average hardware, has a clear beginning and ending, and represents your game well.

The bar isn't perfection. The bar is "a player can pick this up, understand what the game is, have a good time for 15-30 minutes, and leave wanting more." That's it.

What kills demos: crashes on launch (test on multiple machines), confusing first 2 minutes (playtest with someone who hasn't seen the game), no clear ending (players quit at random and feel unfinished), and performance issues (optimize before the fest, not during).

Mistake #3: no livestream

During Next Fest, Steam gives you the ability to livestream directly on your store page. Many devs skip this because they're introverted, or they think nobody will watch, or they don't have a good setup.

The data from multiple postmortems says the same thing: devs who livestream during Next Fest get 2-3x more page visits than those who don't. Steam's algorithm surfaces games with active streams. You're literally getting free visibility that you're leaving on the table.

You don't need a face cam. You don't need a professional setup. Play your own game, talk about what you're building, answer questions from chat. That's enough. An awkward dev playing their own game is more authentic and interesting than a polished trailer loop.

Mistake #4: treating it as a test

Next Fest is not a beta test. It's a marketing event. The primary goal is wishlists, not bug reports.

Yes, you'll get useful feedback. Yes, some players will report bugs. That's a nice bonus. But if your demo is so buggy that the conversation is about crashes instead of gameplay, you shipped too early.

The demo should be the best possible slice of your game. Polish it like it's the final product. First impressions don't get a second chance, and during Next Fest, players are trying 10-20 demos. If yours crashes or confuses them in the first minute, they move on.

Mistake #5: going silent before and after

Some devs treat Next Fest as a one-week event. Show up, put up the demo, wait for results, go back to development.

The devs who get the most out of Next Fest start building momentum 2-3 weeks before. They post about the upcoming demo on their channels. They share short clips. They build anticipation. By the time the fest starts, their audience is already primed.

After the fest, they follow up immediately. A devlog about what they learned. Thanking the players who gave feedback. Showing how the game is evolving based on that feedback. This turns one-time demo players into long-term followers.

The fest is one week. The marketing around it should be at least four.

The devs who did well

I've read through dozens of Next Fest postmortems. The ones that report strong results (3,000+ wishlists in a week) tend to share these traits:

They registered on time. Their demo was polished and short (20-40 minutes). They livestreamed at least 2-3 times during the week. They had a trailer that showed gameplay immediately. Their Steam page was strong before the fest started. And they were active on social media the entire time.

None of that is complicated. It's just preparation. The devs who struggle with Next Fest almost always say the same thing afterward: "I wish I had started preparing earlier."

The timeline that works

Eight weeks before: check that your Coming Soon page is live and your trailer shows gameplay. Start posting about the upcoming demo.

Six weeks before: register for Next Fest the day registration opens.

Four weeks before: have a playable demo build. Start internal testing.

Two weeks before: demo should be feature-complete. External playtesting with 3-5 people who haven't seen the game.

One week before: upload the demo to Steamworks. Test the store page. Prepare your livestream setup. Schedule social media posts.

During the fest: livestream, respond to feedback, post daily updates.

After the fest: publish a devlog, share results, keep the momentum going.

SteamLaunch organizes all of this for you.

Roadmap, deadlines, content calendar, guides, wishlist tracker.

Start