Steam festivals: choose the right event and prepare your game
Choose a Steam festival that fits your game. Check eligibility, discounts, store-page readiness and demo access, then plan what you want to measure.
For indie developers choosing between Steam festivals, start with the game's main mechanic, release state and readiness. Pick a themed event that genuinely fits, use a seasonal sale when a discount makes sense, or consider Next Fest for an unreleased game with a playable demo. Then confirm eligibility and registration before committing preparation time.
That is the decision this guide helps you make. There is a calendar below, followed by a preparation check you can work through with your team. The checklist and worked example are planning suggestions, not results from a measured festival campaign.
Themed sale events, seasonal sales or Next Fest?
Steam themed sale events, seasonal sales and Next Fest have different entry requirements. Start with the kind of participation you need.
| Your situation | Route to investigate | Check before committing |
|---|---|---|
| Your main gameplay fits a named theme | A themed sale event | Event criteria, app eligibility and registration |
| You have an unreleased game and a playable demo | Next Fest, or a relevant themed event | Demo readiness and the rules of the specific edition |
| You have a released game and want to offer a discount | A seasonal sale or a relevant themed event | Release, price-change and discount cooldowns |
| The theme is only a minor feature in your game | A different event | Whether the audience would still recognise the promised game |
For themed events, Valve considers tags and the gameplay represented on the store page. A small side activity is not enough to establish the main theme. Unreleased games and free demos can generally participate unless the event says otherwise; a discount is optional, although discounted games receive more prominent featuring. Valve's themed-event rules
Next Fest is for unreleased games with a public base-game page and a playable demo, and a title can participate once. Valve runs it three times a year, in February, June and October. Use the separate Next Fest guide for preparation and edition details.
Third-party events have their own organisers and application rules. Do not assume the Valve process below also applies to an independent showcase.
Upcoming Steam festivals and sales
Dates checked against Valve's public calendar on 5 November 2026. Event dates are not registration deadlines.
| Event | Dates | Type |
|---|---|---|
| Auto-Battler RPG Fest | 16–23 November 2026 | Themed event |
| Steam Winter Sale | 17 December 2026–4 January 2027 | Seasonal sale |
| Desktop Companion Fest | 14–18 January 2027 | Themed event |
| Shop Keeper Fest | 25 January–1 February 2027 | Themed event |
| Sheep Fest | 4–8 February 2027 | Themed event |
| Couch Co-Op Fest | 8–15 February 2027 | Themed event |
| Steam Next Fest | 22 February–1 March 2027 | Demo event |
Steam events scheduled for the rest of the first half of 2027
| Event | Dates | Type |
|---|---|---|
| Rhythm Fest | 8–15 March 2027 | Themed event |
| Steam Spring Sale | 18–25 March 2027 | Seasonal sale |
| Dinos vs. Robots Fest | 29 March–5 April 2027 | Themed event |
| Racing Fest | 12–19 April 2027 | Themed event |
| Witch Fest | 22–26 April 2027 | Themed event |
| Fighting Fest | 26 April–3 May 2027 | Themed event |
| Real-Time Strategy Fest | 10–17 May 2027 | Themed event |
| Mountaineering Fest | 31 May–3 June 2027 | Themed event |
| Steam Next Fest | 14–21 June 2027 | Demo event |
| Steam Summer Sale | 24 June–8 July 2027 | Seasonal sale |
These are the remaining dates listed here, rather than an application schedule: each event has its own registration requirements. Keep the current Valve calendar as the reference when a date changes.
The official Steam sales run across the seasons: Spring, Summer, Autumn and Winter. The Steam Autumn Sale is already past in this November planning view; use the Winter Sale row for the next seasonal opportunity.
The October events are over. An old calendar entry does not mean registration is still open.
The Auto-Battler RPG Fest runs from 10:00 a.m. PST on November 16 to 10:00 a.m. PST on November 23 (19:00 CET on both dates). Valve gives the opening time as the deadline to enter a discount or opt out. Check your game’s Steamworks registration page for eligibility and registration.
Register the right app, then check the discount
For a themed event, open its registration link through the event documentation or your invitation. If you believe your game qualifies but it is missing, use the appeal route on the registration page. Register before entering an event discount.
Keep a record of the app, event, registration confirmation and any separate marketing-material opt-in. Participation does not guarantee a particular position or inclusion in Valve's trailer. Those are different decisions. Registration and featuring
What can your game actually get from the event?
Valve promotes the event, typically through the Steam homepage and other marketing surfaces. Inside the event, placement can depend on player interest and popularity; some sections use more random ordering. Valve does not promise a position for an individual game.
That gives you access to a relevant browsing context, rather than a guaranteed audience. For a small development team, the useful question is whether this opportunity justifies the work your page, demo and support still need. Set your own goal before joining: learning from player feedback, building interest in an upcoming game, or selling a released one. Then judge the result against that goal. How themed-event visibility works
Winter Sale: which discount cooldowns still apply?
Valve distinguishes three restrictions:
A release cooldown of 30 days, including Early Access and full release.
A price-increase cooldown of 30 days after an increase in any currency.
A discount cooldown of 30 days between discounts.
Official seasonal-sale discounts are exempt from the third restriction. They do not bypass the release or price-increase restrictions, and a custom discount on the same dates does not automatically receive the seasonal-sale exemption. Valve's discount rules
For example, a normal discount ending on 23 November would ordinarily constrain another discount until around 23 December. The official Winter Sale has an exception to that discount cooldown; a recent release or price increase can still block participation. Check the exact app and discount dates in the dashboard.
That is the useful calculation: which later promotion would this decision prevent? It is more informative than treating every eligible event as a reason to cut the price.
Before the event: check the promise, page and demo
This is a working readiness check for indie developers preparing a small team's next event. It is deliberately about what you can show and verify before visitors arrive. It is not another full store-page audit.
Can a stranger see why this game belongs here?
Write a sentence explaining the connection between the event and the main thing the player does. Then point to the screenshot or gameplay moment that demonstrates it.
For a hypothetical auto-battler, that might be choosing units and upgrades before watching the resulting battle. If the page mainly shows dialogue scenes, a player cannot easily see that promise. The practical fix is to show a representative decision and its consequence.
Changing tags to chase an event without changing what the game actually offers would create a different problem: attracting people who expected something else. Use the Steam tags guide to check the metadata in detail.
Does the page make the next action clear?
Open your public page as a visitor. Check the main explanation and the route to play the demo, wishlist the full game or buy it, depending on its state.
Valve recommends using the short description to explain the game's distinctive appeal and suggests mentioning the genre. Keep temporary phrases such as “Now Available” out of that field. The store-page guide covers the individual elements; the page audit checklist is for a broader review.
For this preparation pass, note the one misunderstanding most likely to stop the right player. Fixing that is a manageable task. Rebuilding every asset immediately before an event may not be.
Free demos: test the public route before the event
Test installation, the opening, a representative piece of play and the route from the demo to the full game. Ask someone unfamiliar with the build where they become confused. Put a clear feedback route in the demo, such as a bug form or an existing community space, so a useful observation has somewhere to go.
Valve's demo documentation explains the release checklists and the link back to the base game. It also says the base-game page needs to be republished after releasing the demo for the download button to appear. Do not equate a reviewed build with a tested player journey. Demo setup and release
A demo is not mandatory for every themed event. If the game is unreleased, decide what useful action visitors can take with the material you can honestly offer.
Who can handle a problem during the event?
Name one person to check the public page and one route for bug reports or questions. Prepare a short response to likely installation or access problems.
This is a capacity decision. If the only person able to repair the build is unavailable, that matters more than having several announcement variants ready.
A worked preparation sheet
Here is a fictional example for an unreleased auto-battler with a demo. It illustrates the decisions, not a completed registration or a successful campaign.
| Decision | Example plan |
|---|---|
| Why this event? | Unit selection and upgrades are the core loop |
| What proves the fit? | A short sequence showing a choice and its battle outcome |
| Next action | Play the demo; wishlist the full game if interested |
| Page check | The main description and visible gameplay explain that same loop |
| Technical check | A new player can install, finish the opening and find the full game |
| Remaining gate | Confirm this app's eligibility, registration and deadline in Steamworks |
| Measurement | Record traffic, wishlist additions, demo behaviour and preparation hours separately |
| Stop condition | Do not rush an unstable build simply to meet the calendar |
Your version only needs to be specific enough that someone else on the team can identify what remains unfinished. Replace “improve marketing” with a task such as “show the unit-upgrade decision before the first battle in the gameplay clip.”
Decide what you want to learn before the event starts
For an unreleased game, you might choose wishlist additions as the main outcome and use visits and demo behaviour to understand the journey. For a released game, purchases and the discount's effect on revenue may matter more. Record the time spent preparing and supporting the event too.
Save the available pre-event data and write down any other changes: a new trailer, a creator video, a price change or a demo update. An increase during the festival cannot, by itself, tell you which of those caused it.
Use campaign links for external promotion where appropriate. Steamworks UTM Analytics separates total, trusted and tracked visits; conversions relate to tracked visits, with a 72-hour attribution window. Browser preferences and reporting thresholds limit coverage, so these numbers are not a complete count of every person influenced by your campaign. UTM reporting and limits
Compare like with like when reporting a rate. Do not divide one campaign's attributed wishlists by all store visits, or call demo downloads sales. If you cannot access the required report, record that limitation before claiming success.
Should you join this festival?
Join when the theme genuinely fits, registration is confirmed, the public page or demo supports the promise, and you can afford the preparation and support.
Wait when the build would be rushed, eligibility is unresolved or the work would displace a more important release task. A calendar is useful when it helps you choose what to do next, including choosing to skip an event.
Start with one event and complete the preparation sheet. You should finish with a specific decision, a short list of remaining tasks and a reason for spending the time.
Sources and scope
Valve documentation checked on 5 November 2026: upcoming events, themed sale events, Next Fest, discounting, written descriptions, demos and UTM Analytics.
This guide combines those rules with a proposed preparation method. It does not report measured wishlist growth, a tested conversion uplift or access to an individual developer's Steamworks account.