Steam Playtest vs Demo: Which One Your Indie Game Needs

Steam Playtest vs demo is one of those choices that looks small in Steamworks and turns out to shape your whole pre-launch plan. Both are free, both are separate apps attached to your game, and both put a button on your store page. But one is built for learning in private and the other is built for being seen, and using the wrong one at the wrong time can cost you the one-shot wishlist email, a clean Next Fest, or a month of feedback you never collected. This guide lays out what each one actually does (checked against Valve's Steamworks docs on October 19, 2026), how to pick by goal, and the order that works for most indie games.

The short answer

Use a Steam Playtest when the build is still changing and you need people to break it: onboarding problems, balance, crashes, server load. It is gated, it can be switched off, and it cannot touch your reviews or your wishlist numbers.

Use a Steam demo when the slice is polished and your goal is attention: wishlists, streamers, festivals and Next Fest. It is public, it can show up on Steam lists like any free game, and its first release can trigger a notification to everyone who wishlisted you.

For most indies the answer is not "one or the other" but "Playtest first, demo second". The rest of this guide explains why, and when to break that rule.

What each one actually is

Steam Playtest

A Steam Playtest is a "child" app with its own App ID that lives on your main game's store page as a Request Access option. It has no store page of its own, so any search traffic still lands on your real game where people can wishlist and follow. Despite the name, Valve calls Playtest keys the preferred way to run beta testing once you need more than a small group, and our guide to playtest vs beta test explains how the two terms differ.

The details that matter:

• You control who gets in. With the default limited signup, players request access and you admit them in batches. Steam picks who gets in at random from the people who signed up, and you can restrict it to certain countries if latency matters. With open signup, everyone who requests access is added automatically.
• You can skip the store page entirely. You can request Steam keys for a Playtest and hand them out yourself, even before your store page is live. Valve says you can generally get much larger quantities of Playtest keys than the 2,500 release override keys you are typically limited to on your base game, and it treats requests above 50,000 keys as a sign you are really running an open beta.
• Friend invites exist for multiplayer. You can let each player invite 1, 2 or 3 friends (friends of at least 30 days), which is handy when your game needs full lobbies.
• It is walled off from your real game. Joining or leaving does not change wishlists, Playtest players cannot review your actual game, and Playtest playtime has no effect on refunds, achievements or trading cards.
• It is free and must stay free. You cannot charge for access, sell Playtest keys, or monetize it with in-game purchases. If you want to charge for a work-in-progress version, Valve points you to Early Access.
• It is not confidential. Players are not under an NDA by default. Anything they see can end up on social media within minutes.

If you want the click-by-click setup, our guide on how to set up a Steam Playtest walks through it.

Steam demo

A demo is also a separate App ID associated with your game, with its own builds and depots. The differences are in visibility and in what its release triggers:

• It is public. Once released, anyone can download it from your store page, either from a subtle sidebar link or a prominent green box you can toggle in the store page settings.
• It can be discovered on its own. Valve's docs say demos can appear anywhere a free game could appear, including New and Trending, tag pages and genre pages.
• It can have its own store page. That page is optional. If you enable it, you need demo-specific screenshots and a trailer, and players can leave user reviews on the demo.
• It can go "upcoming" first. You can publish the demo's store presence before the demo is playable so it appears in lists of upcoming demos.
• The first release can notify your wishlisters. When the demo becomes playable for the first time, you can trigger an email and mobile notification to everyone who has your game wishlisted. You get that button once, and only within two weeks of the demo's first release. Wishlist notifications also have a two-week cooldown per App ID.
• You can switch it off later. Deactivating a demo stops new downloads and launches, which is how some developers run a demo only during a festival.

Valve's own advice on timing is worth knowing: it generally recommends waiting until launch for a demo, but says a quality demo before release makes sense when players need to touch the game to understand it. For most indie games on Steam today, that describes you.

The differences that should drive your choice

Strip away the setup details and these are the five that decide it:

1. Visibility. A Playtest only finds people who are already on your store page. A demo can be found by people who have never heard of you. If you need reach, that settles it.
2. The wishlist email. A demo's first release is a one-shot marketing beat. Chris Zukowski of How To Market A Game pointed out after Valve's 2024 demo update that playtests and betas are not counted as a demo release, so they do not use up that email. That is the strongest reason to playtest before you release a demo.
3. Reviews and first impressions. Playtest players cannot review your game. A demo with its own store page can collect reviews, and a crashy first demo is a public first impression you cannot take back.
4. Next Fest. A publicly playable demo is required. A Playtest does not affect your eligibility, but Valve recommends not having one live during the fest because it splits your players between two builds.
5. Control. A Playtest lets you choose how many people play, from which countries, and when it ends. A demo is open to everyone once it is out.

Pick by goal

Write down the single most important thing you need from the next six weeks, then use the matching line.

• "I need to know if new players understand the first 15 minutes." Playtest, limited signup or keys, small batches. Five or so players per round is usually enough to surface the big problems; see how many playtesters you need for numbers by goal.
• "I need to find crashes on hardware I do not own." Playtest, larger batches or open signup, with a crash or feedback button in the menu.
• "I need to stress test servers or fill lobbies." Playtest with open signup or friend invites, scheduled at set times and announced with Steam Events.
• "I need wishlists and streamers." Demo, released with a plan: a festival, a streamer push, and the wishlist notification all pointed at the same day.
• "I want to be in Next Fest." Demo, playtested beforehand. More on dates below.
• "My game is not announced yet." Neither, ideally. Valve's advice is to announce first. If you must test in secret, it recommends release override keys on your unreleased base game with your own NDA and registration process.
• "I want people to pay for the early version." That is Early Access, not a Playtest or a demo.

The order that works for most indie games

Here is the sequence I would follow for a typical single-player indie game with a store page and a few hundred to a few thousand wishlists:

1. Coming soon page first. Both features hang off it, and Valve treats it as the first priority.
2. A small private round before Steam is involved. Friends of friends, a Discord, or players on a playtest platform who chose your game. This catches the obvious issues cheaply. On Get Playtests you can post an itch.io or Steam link for free and get written, video or livestream reviews from players who picked your game.
3. A Steam Playtest of your demo content. Same levels, same length, same tutorial you plan to ship as the demo. Use limited signup or keys so you can watch each batch before adding more.
4. Fix what the Playtest found, then end it. Announce the end ahead of time with a Steam Event so nobody feels cut off.
5. Release the demo deliberately. Line up the wishlist notification, any festival you got into, and streamer outreach for the same window instead of releasing it on a quiet Tuesday.
6. Next Fest with the demo, Playtest off. Push every player to one build.

When would you skip step 3? If your demo is a tiny, stable slice and you have already had strangers play it outside Steam, a separate Steam Playtest may add little. When would you do a Playtest and never a demo? A multiplayer game that cannot afford public servers for a permanent demo can stick to scheduled Playtest weekends until launch.

Planning around Next Fest: February 2027

Steam Next Fest October 2026 starts today, so if you are reading this because you are not in it, the next edition is your target. Valve's event page lists these dates for Steam Next Fest February 2027 (Pacific time; check the page again before you rely on them):

• January 10, 2027, 11:59pm PST: registration deadline. Valve also wants your marketing materials current by then if you hope to be considered for the official trailer.
• January 25: submit your demo build and store page for review if you want the demo live for the press preview. The store page review is needed even if the demo has no separate page.
• February 8: everything required must be submitted for review.
• February 11, 10am PST: press preview starts.
• February 22, 10am PST: the fest begins. Your demo must be live by then.
• March 1: the fest ends.

A game can only appear in Next Fest once, and prologues or "chapter one" style releases of the same content are not allowed. Valve's materials also say the event is open to upcoming games regardless of release date, but you only get one shot, so choose the edition closest to your launch that you can be ready for.

Working back from those dates, a sensible plan looks like this:

• Late October to November: private feedback rounds on your demo slice. Change things freely.
• Late November to mid December: Steam Playtest of the demo content in batches. This is where you catch install, hardware and onboarding problems at scale.
• Before January 10: register and refresh your trailer and capsule art.
• Mid January: final demo build, with the Playtest set to not playable.
• By January 25: demo and store page in review for the press preview.

If you already released your demo and used the wishlist email, that is fine. Valve lets you keep updating the demo, and the fest itself is the next big visibility moment. Just do not release a big update without testing it first.

For the week of the fest itself, our Next Fest demo feedback guide covers the daily routine.

Can you run both at once?

Yes, outside of Next Fest. A Playtest and a demo are separate apps, so you can keep a stable demo public while a Playtest tests the next big feature, a new character or a multiplayer mode. Two things to watch:

• Do not split a crowd you need in one place. During Next Fest, or any week where you are driving traffic to the demo, set the Playtest to not playable and hide the signup.
• Keep the names obvious. Players get confused when "Playtest" and "Demo" both sit on your page. Say in an announcement what each one is for and which build is newer.

Mistakes to avoid

• Releasing the demo on a whim. The first release and its wishlist notification only happen once. Plan it like a launch.
• Calling a demo "the playtest" in your messaging. If you want people to forgive rough edges, it should be a Playtest. A public demo gets judged as a demo.
• Running a Playtest with no way to give feedback. Valve leaves feedback collection to you. Put a big feedback button on the main menu that opens your form or Discord. Our game feedback form template has one you can copy.
• Assuming signups mean players. Not everyone who requests access will launch the build. Count sessions and feedback, not signups.
• Treating a Playtest as secret. It is not covered by an NDA. Plan as if every screenshot will be public.
• Leaving the Playtest up after a paid launch. Valve notes that keeping a free Playtest running after release mostly makes sense for free-to-play games.

Getting real feedback out of either one

Whichever you choose, the build is only half the job. The other half is getting people who will actually play and tell you something specific. Steam brings you signups, but it does not bring you a reviewer who answers your three questions about the tutorial.

That is the gap we built Get Playtests for. You post your game with a link and the focus areas you care about, players who chose your game write, record or stream a review, and you approve the ones that helped. Posting is free and there is no credit card. If you link a Steam Playtest, set it to open signup while the posting is up so reviewers who request access get in right away instead of waiting on Steam's random batches.

Quick checklist

• Write down your single goal for the next six weeks.
• Rough build or learning goal: Steam Playtest, limited signup or keys.
• Polished slice and attention goal: demo, released with a plan.
• Playtest the exact demo content before the demo's first release.
• Plan the wishlist notification; you get it once, within two weeks of first release.
• Feedback button on the main menu of whatever you ship.
• Playtest off and hidden during Next Fest.
• Next Fest February 2027: register by January 10, demo in review by January 25 for the press preview, live by February 22 at 10am PST.