What is Steam Playtest, and what does it cost?
Steam Playtest is a free Steamworks tool to let players test your game before release. It costs nothing for you and nothing for the player. Valve describes it as "a free, low-risk way to get playtesting data for their game without stressing out about Steam keys, user reviews, or wishlists".
The playtest runs on a separate child app ID that is linked to your main game. Valve says that this app has the same Steamworks technical features as the main game, with a reduced store and community setup. It has no store page of its own.
Free also means that you cannot earn money with it. Valve says that it is not OK to charge for access, to sell items in the playtest, to sell playtest keys, or to put those keys in paid bundles or subscriptions. If you want to charge for a game in development, Valve points to Early Access.
Valve suggests the time before release, after your Coming Soon page is up. We found no extra fee for the playtest app in the public documentation.
Sources: Steamworks documentation, Steam Playtest; Steam Keys; Early Access.
How do I create the Steam Playtest app?
Create it from the page of your main game, then release it like a small app. Valve gives the steps below. The names of the pages and tabs are the names in the Valve text.
The review is short. Valve says that the store review checklist for a playtest "only consists of capsule images and icons". The public page does not say how long the review takes, so do not plan the first test day until the review is done.
- Create a new Playtest app from the Associated Packages & DLC page for your game.
- Configure the app in Steamworks. At minimum, give the required library capsule assets and community assets. Set the name that customers see now: Valve says that you cannot change it after release.
- Complete the release process for the playtest app. It has a simplified store page and build review.
- In the Edit Store Page tools of the main game, open the Special Settings tab, enable signups, and publish the change.
- Upload depots and set up builds for the playtest app, as for any other game or demo.
- In the Steamworks settings of the playtest app, follow the Manage Your Playtest link (or Playtest Settings under the Application tab) to add players.
Sources: Steamworks documentation, Steam Playtest; Library Assets.
Should I use limited or open signup, and how do I grant access in batches?
Start with limited signup, which is the default. Players request access, and you add groups of players when you have capacity. Valve says that players are "selected randomly from the pool of signups". You can limit a batch to countries, which Valve suggests when server capacity or latency is a problem.
Switch to open signup when the build is ready for everyone who asks. Each new request then gets access automatically. The change also accepts every pending player, and Valve says that this "will generally start within a few minutes". You can change the signup type at any time.
Two things are not in the documentation. Valve gives no maximum batch size. Valve also gives no way to pick named players from the pool: the selection is random. To let in specific people, such as your Discord moderators, send them playtest keys.
| Way in | How it works | Use it when |
|---|---|---|
| Limited signup (default) | Players request access on the store page. You add groups, and Steam picks at random from the pool. | You want a small first group, or your servers have a limit. |
| Open signup | Each player who requests access is added automatically. | The build is stable and you want volume. |
| Steam keys for the playtest app | You request Standard Release keys and send them. No public signup or live store page is needed. | You want named testers, or the store page is not live yet. |
| Friend invites (experimental) | Each player with access can invite 1, 2 or 3 friends. They must have been friends for at least 30 days. | The game is multiplayer and your servers can take fast growth. |
Sources: Steamworks documentation, Steam Playtest.
How do builds and branches work for a playtest?
A playtest app takes builds like any other app. Valve says to "upload depots and set up builds on the Playtest just like any other game or demo", and that you can add Steamworks features, Steam Input templates and cloud saves.
The Branches page of the Steamworks documentation describes apps in general. The default branch is the build that players get. An upload does not set the build live on the default branch: you do that by hand in App Admin. Other branches can have a password, which is useful for a build that only your team must see.
The Steam Playtest page does not mention branches, so test this in your own playtest app before the first batch. Give each playtest build its own build number in your game, so that you can tell two builds apart in your data.
Sources: Steamworks documentation, Steam Playtest; Branches (Betas).
What do testers see?
Valve documents four notices. A player who is added to the playtest gets an email from Steam, and sees the status on the store page of the base game. A player who gets a friend invite sees it in the Steam notifications, under the bell icon, and on the same store page.
Steam does not send an email when you set the playtest to playable or to not playable. Valve recommends an announcement in the Steam Events and Announcements system. When you set the playtest to not playable, Steam does not launch the playtest app. When you reset a playtest, Steam sends an email to players with recent playtime to say that this phase is over.
A playtest is not confidential. Valve says that players "aren't under nondisclosure agreements with you, and there shouldn't be an expectation of secrecy".
Sources: Steamworks documentation, Steam Playtest (Frequently Asked Questions, Resetting Your Steam Playtest).
Can playtest players review my game, and what happens to wishlists and ownership?
No, they cannot review it. The Valve text is: "A customer who has only participated in the Playtest cannot review your actual game."
For wishlists, the text is: "A customer's wishlist for your game won't be impacted when they join or leave your playtest." Valve gives the reason: the playtest has a separate app ID, so "playtime, wishlists, reviews, refunds, etc. are separate as well". Playtest playtime also has no effect on a refund of the real game, on trading cards or on achievements.
For ownership, Valve says less. The page does not use the word, and it does not say that a playtest gives a license for the main game. It does say that players with access keep it when you restart a playtest, that a playtest key is not revoked when you set the playtest to not playable, and that a reset disables all keys and removes all participants.
A key for the base game is different. Valve says that when a player with your game on their wishlist activates such a key, "it will remove your game from their wishlist". A review from a copy received before release is marked as a Pre-Release Review, and only purchases, not key activations, count in the review score.
Sources: Steamworks documentation, Steam Playtest; Steam Keys; User Reviews.
How do I end a Steam Playtest?
Turn off the signup on the store page first, then set the playtest to "Not Playable" on the Steam Playtest page of the partner site. Valve says that the option does not show while the store accepts signups. After that, Steam does not launch the app.
Tell your players before you do it. Valve warns that you "might frustrate or disappoint your community" if the game goes away with no notice.
To run a second test with the same players, set the playtest to visible again. Players with access keep it. To start with new players, use the reset on the playtest dashboard. Valve says that a reset is not reversible. It needs the playtest to be not playable, the store visibility hidden, the signup type limited, friend invites paused or disabled, the playtest app in no package with other apps, and all settings published.
Sources: Steamworks documentation, Steam Playtest (How do I set it up?, Resetting Your Steam Playtest).
Should I use a Steam Playtest, a demo or keys?
Use a playtest to learn, a demo to sell, and base game keys for a small group under your own rules. The table compares the three with facts from the Valve pages. Our tool asks seven questions and gives a suggestion.
Valve also says that most developers will find playtest keys "easier and safer" than Release State Override keys for the base game.
- Steam Playtest or demo? →
- What is a Steam demo? →
- What is Steam Next Fest? →
- Steam prologue vs demo →
- itch.io for playtesting: restricted pages and keys →
| Steam Playtest | Demo | Release State Override keys | |
|---|---|---|---|
| App | A separate playtest app | A separate demo app | The base game |
| Store page | None. A section on the page of the base game. | A button on the base game page, and an optional separate page. | The page of the base game |
| Reviews | Playtest-only players cannot review the base game. | With a separate page, players can review the demo. | Marked as a Pre-Release Review. Key activations do not count in the review score. |
| Wishlist | Not changed when a player joins or leaves. | You can notify wishlisters once, within two weeks of the first release. | Activation removes the game from the wishlist of the player. |
| Access | Batches, open signup, keys or friend invites. You can stop it. | Public. | You send each key. Access stays until you ban the key. |
| Limit | Valve reviews key requests case by case. Above 50,000 keys, Valve calls the test an open beta. | No number in the Demos page. | Generally 2,500 keys in total. |
| Steam Next Fest | Does not change eligibility. Valve does not recommend a live playtest during the fest. | Required. | Valve requires a demo for the fest. |
Sources: Steamworks documentation, Steam Playtest; Demos; Steam Keys; User Reviews; Steam Next Fest; Testing On Steam.
What is a run sheet for a Steam Playtest: before, during and after?
Work through the list below. It puts the Valve steps in order and adds the measurement steps that Valve leaves to you. Valve says that "collecting feedback from players is up to you".
- Before: write one goal for the test, such as "players finish the tutorial", and the number of testers that you need.
- Before: create and release the playtest app, then turn on signups with the playtest still not playable.
- Before: put analytics in the build with its own build value, and add a feedback button in the main menu. Valve says that a number of developers do this.
- Before: write the survey, and an announcement with the dates, the goal and the place for feedback.
- During: set the build live, set the playtest to playable, and add the first small batch.
- During: post the announcement, because Steam sends no email when a playtest becomes playable.
- During: read starts, crashes and the first session funnel each day. Fix blockers before you add the next batch.
- During: note the date and the size of each batch.
- After: tell players the end date, hide the signups, then set the playtest to not playable.
- After: compare the batches and the builds, read the survey answers next to the data, and write three changes for the next build.
Sources: Steamworks documentation, Steam Playtest; Manalens app events documentation.
What should I measure, and where does each number come from?
Measure five things: signups, access granted, players, session data and survey answers. Steamworks gives the first two. Your own tools give the others.
The Steam Playtest page names a playtest dashboard where you can "monitor users with access". It does not list the other numbers on that dashboard, and it does not describe a report of players or playtime for a playtest. We did not read the dashboard, so the table gives only what the documentation says.
Two more limits. Valve says that Steam "does not currently report conversions for playtest apps" in UTM Analytics. And all Steamworks numbers are totals, with no list of players.
On our side, the Godot and Unity SDKs send game_open, session_start and session_end, with a build field on each event. Funnels and retention take a breakdown by build. The automatic Steam sync is in early access, so the table says "Early access" for it. The Steam UTM Analytics CSV import works today.
- Playtest analytics: what to measure →
- Playtest to wishlist: track which playtesters wishlist and buy →
- How to read the Steamworks UTM report →
- Steam UTM link builder →
- What is D1 retention? →
- Funnels →
- Retention →
| Number | Where in Steamworks | In Manalens |
|---|---|---|
| Signups (requests) | The Steam Playtest page of the partner site. Valve does not list the fields. | No |
| Access granted | The playtest dashboard: users with access. | No |
| Playtest keys activated | Key Stats, under Request Steam Product Keys. | No |
| Store page visits of the main game | Store & Steam Platform Traffic Breakdown. | Tagged visits only, from an import of the UTM Analytics CSV |
| Wishlists of the main game | The wishlist report in Sales & Activations Reports. Totals per day, not per tester. | Early access: an optional daily sync with a Financial API key. |
| Players who started the build | Not documented for a playtest. | Yes: game_open, with is_first_open |
| Session length and returns | Not documented for a playtest. | Yes: session_end with duration_s, and retention by build |
| Where testers stop | Not in Steamworks. | Yes: a funnel of your own progress events |
| Survey answers | Not in Steamworks. Feedback is up to you. | No. The survey builder writes the questions; the answers stay in your form tool. |
Sources: Steamworks documentation, Steam Playtest; Steam Keys; UTM Analytics; Store and Platform Traffic Reporting; Wishlist Reporting. Manalens app events and Steam documentation.
What are the common mistakes?
Most mistakes come from a rule on the Valve page that the team did not read. The list gives the ones with a documented cause.
- No announcement at the start. Steam sends no email when the playtest becomes playable, so many players do not know.
- A name that you want to change later. Valve says that the customer-visible name is fixed after release.
- Open signup or friend invites with small servers. Valve says that growth "can compound quickly" with invites.
- A playtest that stays live during Steam Next Fest. Valve says that this splits your players between two builds.
- A plan to sell access or keys. Valve does not allow it.
- A secret game in a playtest. Players are not under an NDA.
- Base game keys for a large test. An activated key removes the game from the wishlist, and the limit is generally 2,500.
- A reset by mistake. It removes all participants, disables all keys, and is not reversible.
- UTM links as the measure of playtest signups. Steam reports no conversions for playtest apps.
- No end date. Valve asks you to set expectations before you take the build away.
Sources: Steamworks documentation, Steam Playtest; Steam Keys; Steam Next Fest; UTM Analytics.
How do I see what my playtesters did?
Manalens is the analytics and growth engine built for games. Install the Godot or Unity SDK in the playtest build, set the build value, and read starts, session length, the first session funnel and returns for each build and each batch. Steamworks keeps the signups and the access list; the events show what happened in the game.
Sources: Manalens Godot SDK, Unity SDK and app events documentation.
Frequently asked questions
Is Steam Playtest free?
Yes. Valve calls Steam Playtest a completely free feature for both customers and Steam developers. Playtest keys are also a free service, with limits. You cannot charge for access, sell playtest keys, put them in paid bundles or subscriptions, or sell items in the playtest. For a paid game in development, Valve points to Early Access.
How many players can I let into a Steam Playtest?
Valve gives no maximum for signups or for a batch in its public documentation. For keys, Valve reviews each request, and says that a request for more than 50,000 playtest keys means the test is effectively an open beta, so you can open signups on the store page. Base game override keys are generally limited to 2,500.
Can I run a Steam Playtest before my store page is live?
Yes, with keys. Valve says that a playtest does not require a public signup, and that you can generate and distribute keys for a playtest even if your store page is not live yet. You request Standard Release keys for the playtest app, then set the playtest to playable. Signups on the store page need a live page.
Is a Steam Playtest confidential?
No. Valve says that players who sign up are not under nondisclosure agreements with you, and that there should be no expectation of secrecy. For an unannounced game, Valve describes Release State Override keys on the base app, with your own signup and NDA process, and still warns that a test is only as confidential as its least confidential tester.
Can I run a Steam Playtest during Steam Next Fest?
Yes, but Valve does not recommend it. The Next Fest documentation says that a playtest does not affect eligibility. It also says that a live playtest during the fest splits your players between two builds, and that you should send all players to the demo, because a demo is required for Next Fest.
Does Steam show which playtesters wishlisted my game?
No. The wishlist report gives totals per day, and Valve says that Steam does not currently report conversions for playtest apps in UTM Analytics. A player can sign up for the playtest and wishlist the main game on the same page. To see what one tester did, track a Wishlist button click in your own build.
Sources and implementation
- Steamworks documentation: Steam Playtest (Valve, read 19 November 2026) ↗
- Steamworks documentation: Testing On Steam (Valve, read 19 November 2026) ↗
- Steamworks documentation: Steam Keys (Valve, read 19 November 2026) ↗
- Steamworks documentation: Demos (Valve, read 19 November 2026) ↗
- Steamworks documentation: User Reviews (Valve, read 19 November 2026) ↗
- Steamworks documentation: Branches (Betas) (Valve, read 19 November 2026) ↗
- Steamworks documentation: Steam Next Fest (Valve, read 19 November 2026) ↗
- Steamworks documentation: UTM Analytics (Valve, read 19 November 2026) ↗
- Steamworks documentation: Early Access (Valve, read 19 November 2026) ↗
- Steamworks documentation: Library Assets (Valve, read 19 November 2026) ↗
- Steamworks documentation: Store and Platform Traffic Reporting (Valve, read 19 November 2026) ↗
- Steamworks documentation: Wishlist Reporting (Valve, read 19 November 2026) ↗