Quick answer: Use a Steam Playtest to test an unreleased game with strangers: it is a free, separate app that players request access to from your store page, and it does not touch your reviews or wishlists. Use a beta branch to test new builds with people who already own the game, such as after launch or with key holders, optionally behind a password. Many games use a Playtest before release and beta branches after.
Steam gives you two ways to put a test build in front of players, and they solve different problems. Picking the wrong one either limits who can test or exposes an unfinished build to the wrong audience. Here is how they differ and when to use each.
Side by side
| Beta branch | Steam Playtest | |
|---|---|---|
| What it is | An extra branch of your game's own app with its own build | A separate, free “child” app linked to your game |
| Who can play | People who own the game, or hold a key; optionally only those with the branch password | Anyone who requests access from your store page and is granted it |
| How players join | Game Properties > Betas in the Steam client, entering a code for a private branch | A request-access button on your store page; you grant access in batches (random selection) or open it to everyone |
| Price | Owners already paid for the game | Must be free |
| Reviews | Testers are owners and can review the game | Playtest-only players cannot review your game |
| Wishlists | Not affected | Not affected by joining or leaving |
| Timing | Any time, before or after release | Before release, or after release for free-to-play games |
| Keys | Release-state override keys before launch (typically up to 2,500) | Playtest keys in much larger quantities |
| Builds | Set a build live on the branch in Steamworks | Upload builds to the Playtest app's own depots |
When to use a Steam Playtest
- Pre-launch tests with strangers. You want hundreds or thousands of new players without selling the game or handing out keys one by one.
- Protecting your reviews. Players who only joined the Playtest cannot review the real game, so a rough build cannot sink your rating.
- Building awareness. The request button sits on your store page, so the test itself brings people to the page.
Grant access in waves (limited mode) to control server load and the size of your bug inbox, and mark the Playtest “Not playable” when the test ends. Step-by-step setup is in how to run a Steam Playtest.
When to use a beta branch
- After launch. Test a patch with volunteers from your community before it goes to everyone on the default branch.
- Private builds. A password-protected branch for QA, press, streamers or content creators who already have keys.
- Rollbacks. Keep the previous build on a branch so players hit by a bad patch can switch back while you fix it.
Setup is in how to set up a beta branch on Steam.
Either way: plan how bugs come back
Neither Playtest nor beta branches give you crash reports or a bug report form; Steam just delivers the build. Before the test:
- Tag the build. Use a distinct version string for the test build so its crashes are separated from the live game's.
- Capture crashes automatically and add an in-game report button, so the hundreds of testers who never post on your forum still send you something useful.
- Attach the player's Steam ID to reports, so you can follow up with a specific tester.
- Watch your reviews after the beta goes live on the default branch: beta branch testers can review, and so can everyone after release.
Create a free Bugnet project to get crash capture, an in-game report widget that picks up the player's Steam identity automatically (through Steamworks.NET in Unity, GodotSteam in Godot or the Steam online subsystem in Unreal), and your Steam reviews in the same list. For other beta channels, see the best beta testing platforms for indie games.
Frequently asked questions
What is the difference between a Steam beta branch and a Steam Playtest?
A beta branch is an extra build inside your game's own app, available to people who own the game, optionally behind a password. A Steam Playtest is a separate free app that anyone can request access to from your store page, and playtest-only players cannot review your game.
Can I run a Steam Playtest after my game is released?
Generally no: Steam Playtest is meant for games before release, or for free-to-play games after release. Released paid games use beta branches to test new builds.
Do Steam Playtest players affect my reviews or wishlists?
No. A player who only joined the Playtest cannot review your game, and joining or leaving the Playtest does not change their wishlist.
Can I charge for a Steam Playtest?
No. Steam Playtests must be free.
How do I get bug reports from a Steam test?
Steam only delivers the build, so add automatic crash capture and an in-game bug report button to the test build, with a distinct version string so test crashes are kept separate from the live game.
Playtest finds new players before launch. Beta branches protect the players you already have after it.