Pick a Steam Playtest for a closed test with hundreds or thousands of outsiders, a demo when you want public players and a Next Fest slot, and a password-protected beta branch for release candidates and patches. One number is easy to miss. Before release, a beta branch needs Release State Override keys, and Valve generally caps them at 2,500.
What is the difference between a Steam Playtest, a demo and a beta branch?
All three put a build on a player’s machine through Steam, but they live in different places in Steamworks. A Playtest and a demo are separate apps, each with its own appid, linked to your base game. A beta branch is a second build inside the base game’s own app. That one fact decides who can get in, what they can review and whether the test touches your wishlists.
The table below takes each row from Steamworks documentation: the Playtest page, the demos page, the branches page, the keys page, the testing page and the Next Fest page, all accessed 28 October 2026 (keys page rechecked 30 October 2026). The last row is our own estimate.
| Steam Playtest | Demo | Beta branch (main app) | |
|---|---|---|---|
| Separate appid | Yes, a child app of the base game | Yes, a separate App ID linked to the base game | No, a branch of the base game’s app |
| Store presence | Signup button on the base game’s page; no page of its own | Download button on the base page, optional own store page | None; listed in the client under Game Versions & Betas |
| Who gets in | Players who request access; you grant it in batches (limited) or automatically (open); Playtest keys also work | Anyone, once the demo is released | Owners of the app who know the password, if one is set; before release that means key holders |
| Keys before release | Playtest keys; Valve says quantities are generally much larger than 2,500, and above 50,000 the test is effectively an open beta | Not needed | Release State Override keys, generally limited to 2,500 |
| User reviews | A Playtest-only player cannot review the full game | Demo players can leave user reviews on the demo | Key activations can post pre-release reviews, which are listed but do not count toward the score |
| Wishlists | Joining or leaving does not affect the wishlist for the main game | Demo store page links back to the full game; one wishlist notification within 14 days of the demo’s first release | Activating a beta key removes the game from that player’s wishlist |
| Next Fest | Does not affect eligibility; Valve advises against having it live during the fest | Required: a publicly playable demo by the time the fest begins | Not mentioned by Valve |
| Valve review | Simplified store page and build review | Shorter store checklist plus build review | Base game reviewed once; Valve says updates after approval need no new review |
| Confidential | No, players are not under NDA unless you run it hidden with keys | No | Valve points to Release State Override keys when you need NDAs |
| Setup time (editorial estimate) | About half a day, plus review wait | One to two days of work, plus review wait | 15 to 30 minutes per build once SteamPipe works; keys add a request |
Whichever tool you choose, the testers will send you reports, and most of the value is in how good those reports are. The bug report grader scores a pasted report on 8 things a programmer needs and lists what is missing, which is a quick way to set the bar before the first wave arrives.
When does a beta branch beat the other two?
A beta branch is the right tool for a release candidate. It is the only option that tests the exact app players will buy. Achievements, cloud saves, the depot download and the launch path all run through the base game’s appid, the same way they will on launch day. A Playtest or a demo runs under a different appid, so it skips that layer. The beta branch glossary entry explains how players opt in.
If your release candidate has never left the team, a Smoke Test puts one tester on that exact branch for 8 hours. The prioritized bug report comes back in 2 business days. You need one key and one branch password, and the test runs on the same appid your players will install.
Before release, ownership is the catch. A branch is open only to accounts that own the app, so pre-launch testers need Release State Override keys. Valve generally limits them to 2,500, and a first-time developer can request keys only three weeks after creating the AppID. The keys do not expire on their own, so testers keep the game unless you revoke the keys. Activating one also removes the game from that player’s wishlist. Hand keys to a hundred fans and a hundred wishlists turn into a hundred key activations.
That makes a beta branch a tool for a small, named group: your team, an outside tester, a few press contacts. For that group it is the cheapest of the three. Once SteamPipe uploads work, a new branch is a name, an optional password and a “Set build live for branch” click on the Builds page. That takes 15 to 30 minutes per build by our estimate. Valve’s review page adds that once a game is reviewed and approved, you can update it as often as you need without another review.
When does a Steam Playtest make sense?
Valve’s testing page calls Playtest “the preferred method of enabling closed betas on Steam”. It fits the stage where you want strangers on the build without a public download. Signups sit on the base game’s store page, so people who sign up can wishlist the game in the same visit.
The access model is the main reason to choose it. In the default limited mode you let players in from the signup pool in batches, and Steam picks them at random, with an optional country filter. Open mode lets everyone in automatically. An experimental friend-invite setting lets each player bring 1, 2 or 3 friends, limited to friendships at least 30 days old.
Three limits matter. A Playtest is free and cannot be sold. It is not confidential, because players are not under NDA. If you need secrecy, the Playtest page suggests a hidden Playtest with keys, or the main app with Release State Override keys. And Steam does not email players when the Playtest becomes playable, so you announce each wave yourself.
You create the Playtest app from the base game’s associated packages page, add library capsules and icons, and pass a simplified store page and build review. Valve gives no review time for Playtests. Its review process page gives 3 to 5 business days as the typical time for a review, and our guide to how long Steam review takes lays out the full calendar. Plan the first wave a week after you submit.
What does a demo give you that a Playtest does not?
A demo is public. Once released, anyone can download it from the base game’s store page, and it can appear anywhere on Steam that a free game could. It is a marketing tool first and a test second. The demos page lists three things a Playtest does not give you.
- Next Fest entry. The Next Fest page requires a publicly playable demo by the time the fest begins. A Playtest does not replace it.
- One wishlist notification. Valve can notify wishlisters once, within 14 days of the demo’s first release. Disabling and re-enabling the demo does not reset that.
- Reviews of its own. Demo players can leave user reviews on the demo. Some third-party comparisons say demos take no reviews, so plan around Valve’s wording.
The cost is setup. A demo is a separate App ID with its own depots and builds, created like a full app. Its store checklist is shorter than the base game’s. If you want a separate store page for the demo, Valve asks for a trailer and at least five screenshots specific to the demo content. Our estimate for a team that has shipped nothing on Steam yet is one to two working days, plus a review round.
For Next Fest the review deadlines are fixed. Valve asks for the demo 5 weeks before the fest if you want it in Press Preview and 3 weeks before at the latest. Valve also does not recommend a Playtest live during the fest, because it splits players between two builds. The week-by-week test plan for the demo itself is in our February 2027 Next Fest demo QA plan.
Which one should you use at each stage?
The path below is our editorial recommendation built from the rules above, since Valve prescribes no order. The tools can also run side by side. Valve’s testing page suggests one branch for beta testers and another for press.
| Stage | Main tool | Why | Watch out for |
|---|---|---|---|
| Internal alpha (team and friends, under about 50 people) | Beta branch with Release State Override keys | Same appid as launch, password-protected, fastest to update | Keys come out of the 2,500 limit and remove the game from testers’ wishlists |
| Closed alpha or beta with strangers (hundreds to thousands) | Steam Playtest, limited signups | Wishlists untouched, no review on the full game, batches you control | Not confidential; plan a week for the first review |
| Demo for Next Fest | Demo, with the Playtest set to Not Playable | Only a demo counts; one wishlist notification | Demo reviews are public; Next Fest review dates are fixed |
| Release candidate | Password-protected beta branch on the base app | Tests achievements, cloud saves and the real install path | Note the build ID in every report; set the default branch live by hand |
| After launch | Beta branch for patches | Owners can opt in; no new review per update | Run a regression pass before default, as in the patch day QA checklist |
The last row is where most launch bugs get caught or missed. Upload the release candidate to a password-protected branch, install it through the Steam client on a clean account, then set that same build live on default by hand. The Early Access launch checklist has the branch and rollback steps for launch week.
How long does each one take to set up?
Valve publishes no setup time for any of the three. The ranges below are our editorial estimates for a first-time team whose SteamPipe uploads already work, with review waits on top.
- Beta branch: 15 to 30 minutes for a branch, a password and a build set live. Before release, add a key request. A first-time developer cannot send it until three weeks after creating the AppID.
- Playtest: about half a day for the child app, capsules, icons, depots, the build and the signup toggle. Then one simplified review.
- Demo: one to two days for the app, depots, build, store checklist and, if you want one, a demo store page with a trailer and five screenshots. Then one review, timed against Next Fest dates.
Count review rounds in business days and assume one comes back with feedback. The Steam review process glossary entry sums up what Valve checks. A Playtest wave or a demo is a first impression too, so test the build before it goes out.