Steam Next Fest: what actually happens before, during and after

You get one shot at this. Not one per year, not one per game per stage of development — one Next Fest per game, ever. That's Valve's rule, and it's the single most important thing to know before you register.

The second most important thing: registration for the October 2026 edition closes on 31 August. If you're reading this in late August and your store page isn't public yet, that decision is being made for you.

This is written for developers deciding whether to register, not for players hunting free demos. I'll go through the dates, the eligibility rules, how visibility inside the Fest actually works, and what the data says about what you can realistically expect. Some of that last part is less exciting than the guides suggest.

The dates for October 2026

Steam Next Fest is a week-long event for upcoming PC games, and it runs three times a year — February, June and October. The October 2026 edition runs 19 October to 26 October, both at 10:00 AM PDT.

Every demo in the festival is free to download. That's the mechanic the whole thing rests on: players browse participating games and try them with no friction, which is why the Steam store surfaces the event so heavily during that week.

After October, the next editions are February 2027 and June 2027.

If you're reading this after those dates have passed, check Valve's Next Fest documentation for the current edition — the mechanics below don't change, only the calendar does.

The one-Fest rule, and why it's a real decision

Valve's eligibility list includes a line that's easy to skim past: a title may only participate in one Next Fest. Not one per year. One, full stop.

So the question isn't "should I do Next Fest." It's "which Next Fest," and that's a genuine strategic call with no obvious answer. Valve knows this, and says so directly in their own documentation: some developers join early to learn what players enjoy, others pick the edition closest to launch to build interest right before release. Their verdict on which is better? "There's no right answer."

That's unusually honest for platform documentation, and I think it's correct. The two options do different jobs:

Early in development gets you feedback while you can still act on it. You'll find out that your tutorial is confusing, that people quit at the third level, that the mechanic you're proudest of goes unnoticed. That's worth a lot. What you won't get is a wishlist spike that's still warm at launch.

Close to launch converts attention into wishlists at the moment those wishlists matter most. But you're locked in — whatever the demo shows is what people judge you on, and there's no second Fest to fix it in.

There's no formula here. What I'd say is: if you genuinely don't know whether your game is fun yet, that's a design question, and burning your one Fest to answer it might be the right trade. If you already know it's fun and you're eighteen months out, waiting is probably cheaper than it feels.

What the numbers actually say

This is the part most Next Fest guides skip, and it's the part that should shape your expectations.

Simon Carless at GameDiscoverCo has analysed every Next Fest since February 2023. For the February 2026 edition, with 3,500+ participating demos, his finding was blunt: the median game gained 11 Steam followers.

Eleven. For a week of being in the largest demo showcase on the platform.

Carless estimates that translates to roughly 200 wishlists, and I want to flag how that number is built, because it matters. He measures followers, which are publicly visible, and converts to wishlists using a rough multiplier. He hedges it himself — "perhaps 200 wishlists." So treat it as an order of magnitude, not a measurement. Anyone quoting you a precise Next Fest wishlist median is quoting an estimate of an estimate.

The trend underneath is clearer than the absolute number, and it's not encouraging. The field grows and the per-game return shrinks. Carless calls it "continued % degradation as the # of demos goes up," which is a dry way of describing a pie being cut into more slices.

His summary of the dynamic is the sentence I'd tattoo on the inside of your eyelids before you register:

games that already had interest are continuing to scale it, but you're seeing less of the 'Next Fest demo hit out of nowhere'

Next Fest amplifies existing interest. It doesn't create it. If you arrive with no audience, a randomised slot in a list of 3,500 games is not going to build you one. If you arrive with a few thousand wishlists and a demo that's genuinely good, the Fest can meaningfully compound that.

Which means the work that decides your Next Fest outcome mostly happens before Next Fest. Your store page, your capsule art, your tags — those are the things that convert the traffic Valve sends you. The Fest is a traffic event, not a conversion event.

Are you even eligible?

The full criteria, from Valve:

• Your game hasn't been in a previous Next Fest
• Your Steamworks account is in good standing
• Your base game's store page is published and public
• You'll have a publicly playable demo by the time the Fest begins
• Your game won't release before the Fest ends
• It's not a prologue, preview, or short-form version of a game you've already released

A few things that surprise people:

There's no requirement about your release date, as long as it's after the Fest. You can be two years out. That's fine.

There's no requirement about demo length or newness. Valve doesn't specify a minimum. An old demo you've already had live is acceptable.

Early Access and free-to-play games are eligible, as long as the game hasn't released yet. Entering Early Access counts as releasing.

Steam Playtest doesn't affect eligibility, but Valve recommends against running one during the Fest — it splits your players across two builds instead of concentrating them in one place. Sensible advice.

One wording trap: Steam distinguishes the demo app from the full game app, and registration happens from the base game, not the demo. That trips people up. For most titles it'll show up automatically on your App Landing Page, and you should see a green checkmark once it's saved.

How visibility inside the Fest actually works

This is the most useful mechanical detail in the whole documentation, and it's buried.

The first few days are completely randomised. Valve says so explicitly — every location except explicitly named lists and personalised segments is randomised at the start. Only after a few days does the algorithm kick in and start personalising carousels based on what people have been playing during the Fest.

Two consequences.

First, the opening days are a lottery you can't influence, which is by design — Valve's stated intent is giving visibility to all participants. Don't read your day-one numbers as a verdict.

Second, once personalisation starts, it runs on behaviour during the Fest. Which means the thing that determines your back-half performance is whether people who tried your demo kept playing it. Not your marketing. The demo.

Your tags decide where you appear

When you register you pick one or two primary categories. Valve combines those with your base game's Steam tags to sort you into sections.

This is where your tag hygiene stops being an SEO nicety and starts being the difference between showing up and not. If you haven't audited your tags, do that first — the same tag choices that feed the discovery queue feed your Next Fest placement.

Valve gives you a Developer Preview Page about five weeks before the event, showing exactly where your game has landed. Check it. If you're in a section that doesn't fit, you still have time to adjust your tags.

The workback timeline

Valve publishes their own countdown, and it's worth internalising because the deadlines stack up faster than they look:

Two pieces of Valve's own advice I'd underline.

Valve also runs live Q&A sessions with the Steam Business Team before each edition, and past recordings are on YouTube. If you're registering for the first time, an hour there is cheaper than learning these deadlines the hard way.

Submit 3–5 business days before your actual deadline. If you fail build review the first time, you need room to fix and resubmit. People miss Fests over this.

Build review is not QA. Valve is explicit: it validates that the game has the promised features and that it runs. It will not catch your bugs. Do your own testing, and don't treat passing review as a quality signal.

Also worth knowing: you can update your demo build after passing review, and Valve won't re-review it. Convenient, and a good way to ship a game-breaking bug on day one if you're careless.

Press Preview, honestly

Press Preview is Valve's sneak peek for press. It starts 11 days before the Fest and gives selected outlets an early look at the full list of registered games. Some notes on what it is and isn't:

• All registered games are included, regardless of demo status. If you're cancelling, do it before Press Preview starts.
• Press get no special access. They see what the public sees. If your demo isn't live, they can't play it.
• Releasing your demo early for press releases it for everyone. There's no press-only build.

If you provided contact details on the registration form, Valve shares those with press.

Now the reality check. Journalist Pierre-Hugues Meyer, writing about the February 2026 Fest, reported receiving emails about 157 different Next Fest games — the first on 28 January, the last on 25 February. One journalist. 157 pitches.

So Press Preview is a real opportunity and also a very crowded room. Being in it is not the same as being covered.

During the Fest

The short version: your demo does the work now. Valve's own tips are practical, and a couple are genuinely underused:

Put a feedback link on your demo's main menu. A button, right there, going to a Steam sub-forum, your Discord, a bug tracker, wherever. You're paying a week of visibility for feedback — make it trivially easy to give.

Say whether you'll deactivate the demo, and when. Plenty of people download demos meaning to play them later. If yours is going away after the Fest, tell them so they prioritise it.

Make sure the demo button is on your store page. Under Edit Store Page → Special Settings, and tick "display above purchase options" so it's prominent.

Set the demo live at least 30 minutes before the Fest starts. Valve's minimum recommendation, and it gives you time to notice something's broken while you can still fix it.

Livestreaming is entirely optional. You can stream gameplay and talk to players in the chat while they watch, and there's a dedicated section where people browse live streams from participating games. Since the October 2024 edition there's no official Valve livestream any more, and developer streams sit in their own tab. If you don't have the time or the temperament for it, skip it and put the energy into the demo. If you do stream, test the setup well in advance — broadcasting a demo works differently from broadcasting a regular game, and it takes a few attempts to get right.

One note if you're reading older guides: the Fest was reorganised in October 2024, away from the old genre tabs. Advice written before then describes an event that no longer looks the way it's described.

After the Fest

Shortly after it ends, Valve publishes a Wrap-Up page featuring the games with the most-played demos. If you land on it, you'll get an email — worth watching for.

Beyond that: you now have data you didn't have before. How many people installed the demo, how long they played, where they stopped, what they said in your feedback channel. In my experience that's the part people underuse. The wishlist number is the headline, but the playtime distribution is the thing that tells you whether your game is working.

And if the numbers were small — which, given a median of 11 followers, they statistically will be for most participants — that's information too, not a verdict on the game. It usually means the audience-building work hadn't happened yet. That work is still available to you. The Fest isn't.

Should you do it at all?

Yes, if you're going to release on Steam anyway. It costs you nothing but preparation time, and even a randomised week in front of Steam's browsing audience is more exposure than most indie games get on any given week.

But go in with the right expectation. Next Fest is not a launch strategy. It's an amplifier, and amplifiers need a signal. Spend the months before it building something to amplify — a store page that converts, tags that put you in the right sections, a demo that people finish — and pick the edition where those are actually ready.

The worst outcome isn't a quiet Next Fest. It's burning your one and only Fest on a week where nothing was ready. :)

FAQ