> ## Content Index > Fetch the complete content index at: https://seeindie.com/llms.txt > Use this file to discover other available public pages before exploring further. # Steam Playtest: what it's for, and when a demo is the better call - URL: https://seeindie.com/blog/steam-playtest/ - Published: 2026-09-15T11:00:00.000Z - Updated: 2026-10-04T20:30:29.000Z - Description: A Playtest is for data. A demo is for wishlists. What a Steam Playtest actually is, the two switches that catch people out, and when release override keys are the better route. - Author: Isabella-Viktoria Quilez - Tags: Steam, Indie Marketing, #hub-steam, #for-games A Steam Playtest is for data. A demo is for wishlists. If you want to know whether your game works, run a Playtest. If you want people to want it, that's a demo, and the two are not interchangeable. Valve's documentation explains every button. What it doesn't do is tell you which one to press, or warn you about the three or four settings that will eat an afternoon the first time you meet them. That's what this is for. I've written this from the [Steamworks documentation](https://partner.steamgames.com/doc/features/playtest?ref=seeindie.com) itself, and nothing else. Every quote below is Valve's own wording. The short version - **A Playtest is a separate app.** Playtesters can't review your real game, and their playtime touches none of your numbers. - **It won't get you wishlists.** There's no separate store page to convert on. That's the design, not a shortfall. - **Playtest is Valve's preferred way to run a closed beta.** Release override keys are the exception, for when you need NDAs. - **Two switches, not one.** Playable and signups are independent, and the off switch hides while signups are running. - **Don't run one during Next Fest.** Valve advises against it, and Next Fest requires a demo anyway. On this page [What it is](#what-it-is) [Playtest vs demo](#vs) [Setup](#setup) [Friend invites](#friend-invites) [The keys route](#keys) [FAQ](#faq) ## What a Steam Playtest actually is A Playtest is a **separate app**: a "child" appID linked to your main game but distinct from it. The game stays unreleased. Nobody buys anything, and it costs neither you nor your customers a thing. That separation is the whole feature. Valve's own summary of what it buys you is that a Playtest gathers data "without the stress of managing email lists and Steam keys or worrying about user reviews, or wishlists." Valve built the Steam Playtest feature because developers were already improvising around the problem, in Valve's words with "a demo that was really just an Open Beta" or a free "Prologue" game. Studios wanted to test with live customers without putting their reviews and wishlist numbers at risk. Here's what actually stays on the other side of that line: - **Reviews.** A customer who has only taken part in the Playtest cannot review your real game. Not "their review goes somewhere else" — they can't write one. - **Wishlists.** Joining or leaving your Playtest doesn't touch a customer's wishlist for your game. - **Playtime.** Playtest hours have no effect on the Steam refund policy or a player's ability to refund the real game later. - **Achievements and trading cards.** Playtest time doesn't unlock either on the main game. Think about what the review line alone is worth. Hand fifty testers keys to your actual game, and three of them review a build that was never meant to be judged. Those reviews sit on your store page. A Playtest makes that impossible rather than unlikely. A few properties worth having in your head before you start: - **There's no separate store page.** The sign up option lives as a section on your game's page. Valve's reason for building it that way: "any search traffic, store recommendations, etc all funnel towards the real product for users to wishlist and follow." - **Access is gated.** You let in as many or as few players as you want. - **You can switch it off,** and switch it back on later. - **The tech is not reduced.** A Playtest appID has the same Steamworks technical features as the main game — depots, builds, Steam Input, cloud saves. What's reduced is the store and community setup, not the toolbox. Some developers keep the Playtest app on afterwards as a testing ground for new tools or features, though Valve notes that probably only makes sense if the game is already free-to-play. If you're still working out the order of the whole Steam process, the [publishing guide](https://seeindie.com/how-to-publish-a-game-on-steam/) puts this step in context. ## Playtest, demo, or Next Fest? The comparison I wanted when I first read about this: | | Playtest | Demo | Next Fest | | ----------------------------- | ----------------------------------- | ------------------------- | ------------------ | | **Who gets in** | only who you let in | anyone | anyone, for a week | | **Own store page** | no, a section on your game | yes, optional | not applicable | | **Can they review your game** | no | not applicable | not applicable | | **Wishlists** | people still wishlist the main game | yes | yes | | **Can be switched off** | yes, any time | yes | ends on its own | | **What it's for** | data and feedback | conversion and visibility | a visibility event | And the rule that catches people out. Valve, in the Next Fest documentation: > Yes, as use of a Steam Playtest does not affect eligibility. However, we do not recommend having a Playtest live during Steam Next Fest, as this splits your players between the two builds instead of concentrating them in one spot. As a demo is required for Next Fest, we would recommend pushing all your users towards your demo during the event. Two things in there. Running a Playtest doesn't disqualify you. And Next Fest requires a demo anyway, so during the festival the demo is the thing you point people at. If you're planning [a Next Fest run](https://seeindie.com/blog/steam-next-fest/), the Playtest goes before or after. ## Setting one up Condensed from Valve's documentation: 1 Create the Playtest app From the *Associated Packages & DLC* page of your game. 2 Configure it You need library capsule assets and community assets at minimum. Get one thing right first time: the customer-visible name can't be changed after release. 3 Run the release process A simplified store page plus build review. Worth knowing: the store review checklist for a Playtest "only consists of capsule images and icons". Your [capsule art](https://seeindie.com/blog/steam-capsule-art/) is, quite literally, the entire review. 4 Turn on signups Under *Special Settings* in the Edit Store Page tools of your [main game's store page](https://seeindie.com/blog/steam-store-page/), not the Playtest's. 5 Upload builds Like any other app. 6 Let players in You add them in groups, and Steam picks them at random from the pool of signups. You can restrict which countries get in if server latency is a concern. 7 Deactivate it By setting the Playtest status to "Not Playable" when you're done. ### Signup type: limited or open Valve calls this the signup type, and there are two. **Limited** is the default: people request access, you grant access in batches as you have capacity. **Open** adds anyone who requests, automatically. One thing to know before you flip that switch. Changing from limited to open kicks off a process that accepts every pending request, and Valve says it "will generally start within a few minutes". If a few thousand people have been waiting and you're not ready for them, that's a surprise you get to have exactly once. ## Two switches, four states, and the one that hides This is the part I'd want someone to tell me in advance, because none of it looks like a setting when you're reading the documentation front to back. **Playable and signups are independent.** Valve lists all four combinations as normal configurations: not playable and not accepting signups (the default, and also the end state), not playable but collecting signups (useful before the build exists, or between rounds), playable and collecting signups, and playable but closed to new people. **The off switch hides while signups are running.** The "Not Playable" option is not shown while your store page is still accepting signups. If you're hunting for it and it isn't there, that's why. Turn signups off first. **Steam emails players when you admit them. It does not email them when the build becomes playable.** That gap is yours to fill, and Valve says so: use Steam Events and Announcements to tell people the Playtest is live. A [devlog or event post](https://seeindie.com/blog/devlog/) is the obvious place. The same goes for turning it off. Valve's wording is "Be thoughtful about this action!" — you'll frustrate people if you take the thing away without warning. If you do restart later, everyone who already had access keeps it. ## Friend invites, and how fast they compound This one is newer, experimental, and aimed at multiplayer games. When it's on, players with access can invite their friends, and those friends can invite theirs. You set how many invites each player gets: one, two or three. You can pause new invites at any time. Two details decide whether this is useful or alarming: - **Players can only invite friends they've been friends with for at least 30 days.** That's the built-in brake on invite farming. - **An invite that's already been sent stays active.** Pausing stops new invites going out. It doesn't recall the ones in flight. Valve's own arithmetic makes the shape of it clear: 5,000 players with three invites each, capped to people who had access as of today, is 15,000 potential invites. The documented way to keep it in hand is to watch the dashboard and pause, or to limit invite rights to players who joined by a cut-off date. Valve's framing is that this is "best for games with robust server capacity", and that if you're worried about growth outrunning you, "this feature may not be for you". That's a recommendation, not a gate. Nothing stops you turning it on. ## The keys route, and the number that decides it You can distribute keys instead of opening signups. No public sign up option, and it works even if your store page isn't live yet. The question is which app those keys point at. 2,500 where Release State Override keys on your main game typically top out Steamworks documentation 50,000 the threshold at which Valve calls your Playtest "effectively an open beta" and suggests opening signups — not a hard cap Steamworks documentation $0 what you may charge for Playtest access — not directly, not via keys, not in a bundle Steamworks documentation Between those two numbers sits the phrase **"generally much larger quantities"**, which is all Valve will say about Playtest key volumes. There's no number, and I'm not going to invent one. The 50,000 is worth being precise about, because I've seen it repeated as a hard cap. Valve names it twice, in two different senses. In the key section it's a threshold: once you want to request more than 50,000 keys for your Playtest, "your playtest is effectively an open beta and you should feel comfortable opening signups on your Steam store page". In the section on confidential playtests it reads as a ceiling: running your test through a normal playtest app "will enable you to request up to 50,000 keys". Both sentences are on the same page. So the honest version is neither "the limit is 50,000" nor "there's no limit" — it's the number at which Valve stops asking how many keys you need and starts asking why you aren't just opening signups. Either way, Valve looks at each key request case by case and reserves the right to say no. Three rules that aren't optional: **Playtest keys are Standard Release keys only.** You cannot request Release State Override (beta) keys for a Playtest app. A key activated before the Playtest is set to Playable simply won't run anything yet. **A redeemed key isn't revoked when you set the Playtest to "Not Playable".** Once someone has it, they have it. **You cannot charge for Playtest access.** Not directly, not by selling keys, not by bundling them into anything paid, and not through in-game transactions either. If you're ready to take money for a work-in-progress build, that's Early Access. ## So when do you use release override keys instead? Valve answers this directly, and the sentence inverts what most write-ups assume: > While Steam Playtest is the preferred method of enabling closed betas on Steam, release override keys are available if you want to manage your playtest off your main game's App ID and have things like NDAs in place. **Playtest is the default. Keys on the main app are the exception, for when you need NDAs.** The [Testing On Steam documentation](https://partner.steamgames.com/doc/store/testing?ref=seeindie.com) says the same thing from the other direction: requesting keys for the Playtest app is "now the preferred method of running beta testing for your game if you need more than small group of testers". Most of the advice I've read has this backwards, treating keys as the real way to run a beta and Playtest as the lightweight option. If you do go the release override keys route on your main app, Valve's recommended process: 1 Upload a build The one your beta testers will play. 2 Set up your Coming Soon page first Two reasons: you get to test your marketing presence against what players actually experience, and the Steam Community Hub gives them somewhere to talk. It also lets people wishlist. 3 Request the keys From your "Beta Testing" release override package. Anyone who activates one can play immediately, so don't hand them out early. 4 Track what you hand out By default a player owns the game permanently once they activate a key. To end the beta, revoke the keys with the key banning tool, and flag it as end-of-beta so testers get a friendly message instead of a silent lockout. You can also give different groups different builds — testers on one branch, press on another — and branches can be password protected. ## Confidential playtests, honestly If your game isn't announced yet, Valve's position is blunt, and I think they're right: > Even when configured properly, a confidential playtest will only ever be as confidential as your "least confidential" playtester. Leaked screenshots or video, they add, "could potentially spread around the internet in moments". Their actual recommendation is to announce the game first, then test. That's the boring advice and it's the correct advice. If you're doing a friends-and-family alpha anyway, the things nobody tells you: - **There are two documented routes, not one.** The most secure is Release Override keys on the unreleased base app. The other is the Playtest app with keys, set to Playable, with store visibility Hidden. Both need you to build your own registration. - **There's no NDA.** Accepting a Steam key binds nobody to anything. If you want one, that's your own system, before the key goes out. - **Third-party apps announce for you.** Plenty of testers run tools that surface whatever their Steam client is doing. Valve notes that some of them actively prompt: *"We don't recognize this game, can you tell us more about it?"* - **Use a codename,** and rename before the Coming Soon page goes up. - **The 2,500 cap applies here too,** and Valve draws the conclusion for you: past that, "the probability of a leak is increasing to the point where you're likely 'announcing' your product anyway". Their suggested fix is to announce, then run a normal playtest, which opens the door to up to 50,000 keys. One more thing that surprises people. An app becomes visible to players and third-party crawlers once it publishes a store page, becomes available for pre-load, or gets released — and that last one counts even if it releases with a Hidden store page. Plan your announcement for no later than the first of those. ## Resetting: the button with no undo If you want a second round with a completely fresh group, you can reset the Playtest. It removes every participant, and Valve is explicit that it is not reversible. Six things have to be true before it will let you: 1 Not Playable The Playtest app is deactivated. 2 Store visibility is Hidden On the Playtest app. 3 Signup type is Limited Not Open. 4 Friend invites paused or disabled Both count. 5 The app stands alone The Playtest app isn't in a package with other apps. 6 Everything is published All store page and Steamworks settings. And what a reset actually does, which is more than "clears the list": - **All product keys for the Playtest are disabled, including keys nobody has activated yet.** - Pending friend invites are archived. - Participants and everyone waiting for access are removed, and players with recent playtime get an email telling them this phase has concluded. If you've handed out a batch of keys for round two before resetting round one, that's the sentence that costs you the batch. ## Two things that will waste an afternoon Both are in the documentation, both are easy to miss, and both look like your build is broken when it isn't. **A new depot isn't automatically testable.** It has to be in your Dev Comp package. If files won't download, launch `Steam.exe -dev`, open the console, and run the command `licenses_for_app `. That shows the package being used and the depots in it. Missing one, edit the package. **Fresh Steam accounts can't send friend requests.** New accounts are Limited User Accounts, which blocks friend requests, so testing multiplayer with brand-new test accounts fails for reasons that have nothing to do with your game. Either send the request from a non-limited account, or activate a Dev Comp key on the new account, which lifts the limit. ## Collecting the feedback is your job Valve builds the room. It doesn't hand you a way to hear what happened in it. Collecting feedback from players is explicitly left to the developer, and that's worth planning before you let anyone in, not after. The pattern Valve says it sees most often: a big feedback button right on the main menu, pointing wherever you want to collect and manage responses. A Steam forum, your Discord, bug tracking software, your own site. Valve doesn't push one of them. Two things make the difference between a trickle and something you can act on: - **Tell players what you're actually after.** Valve's own suggestion is to engage directly with your audience and let them know what kind of feedback you want and where best to share it. "Let us know what you think" gets you opinions on the main menu. A specific ask gets you the gameplay data you were missing. - **Put the link where they'll see it.** You can provide links to your preferred feedback or communication system directly in a community announcement, which is the same channel you're already using to tell people the build is playable. ## What a Playtest won't do **A Playtest will not get you wishlists.** It isn't designed to. There's no separate store page to convert on, the audience is capped at whoever you let in, and the whole architecture exists to keep the test away from your game's public numbers. That's the design, not a shortfall. I can't tell you what a Playtest converts, either, and neither can anyone else honestly: Valve publishes no signup or conversion figures for it. What Valve does say is qualitative — search traffic and store recommendations point at the real product, not the test. What you get instead is the thing that's genuinely hard to buy: people playing your unfinished game, at home, on their own hardware, with nobody watching. Where they quit. What they misunderstood. Which system nobody touched. If you want visibility, that's a demo, ideally pointed at [Next Fest](https://seeindie.com/blog/steam-next-fest/). If you want to know whether the game works, that's this. Don't run them at the same time, and don't expect either one to do the other's job. ## FAQ What is a Steam Playtest? A Steam Playtest is a separate "child" app attached to your main game that lets you run gated pre-release testing. Because it's a distinct app, playtime, wishlists, reviews and refunds stay separate from the real game, and you control exactly who gets access. Is Steam Playtest free? Yes. Steam Playtest is free for both developers and players. You cannot charge for access, sell Playtest keys, include them in paid bundles, or monetise the Playtest with in-game transactions. Does a Steam Playtest have its own store page? No. The signup appears as a section on your main game's store page. Valve built it that way so search traffic and store recommendations funnel towards the real product, where people can wishlist and follow. Do playtesters leave reviews on my game? No. A customer who has only participated in the Playtest cannot review your actual game. That's the main reason to use a Playtest rather than handing out keys to your main game. Playtest or demo — which should I use? A Playtest is for gathering data and feedback from a controlled group. A demo is public and built for conversion and visibility. If you want to know whether your game works, run a Playtest. If you want wishlists, run a demo. Can I run a Playtest during Steam Next Fest? It doesn't affect your Next Fest eligibility, but Valve recommends against it, because it splits your players between two builds instead of concentrating them in one place. Next Fest requires a demo anyway, so point people at the demo during the event. How many Steam keys can I request for a Playtest? More than for a main-game beta. Release State Override keys on your main game are typically capped at 2,500, while Playtest key quantities are, in Valve's words, "generally much larger". Valve names 50,000 as the point at which your Playtest is effectively an open beta and you should open signups instead. Every request is reviewed case by case. Why can't I find the option to end my Playtest? The "Not Playable" setting is hidden while your store page is still accepting signups. Turn signups off first, then set the Playtest status to Not Playable. How do I end a Steam Playtest? Disable the store page signup, then set the Playtest to "Not Playable" in the partner settings. Tell your community first. Keys already redeemed are not revoked, and if you reactivate later, players who already had access keep it. What does resetting a Steam Playtest do? It removes all participants and is not reversible. It also disables every product key for the Playtest, including keys that were never activated, and archives pending friend invites. Six conditions have to be met first, including Not Playable, Hidden store visibility, Limited signup type and paused friend invites. How do Steam Playtest friend invites work? Players with access can invite friends they've been friends with for at least 30 days, and you choose whether each player gets one, two or three invites. You can pause new invites at any time, but invites already sent stay active. How do I collect feedback from playtesters? That part is up to you. Valve says the most common approach it sees is a feedback button on the game's main menu, pointing at a Steam forum, a Discord channel, bug tracking software or your own site. Valve suggests telling players what kind of feedback you want and where to share it, and you can provide links to your feedback system directly in a community announcement. Can I run a confidential playtest for an unannounced game? You can, but Valve recommends announcing first. There's no automatic NDA, third-party tools may surface your unannounced game from testers' Steam clients, and the 2,500-key limit applies. There are two documented routes: Release Override keys on the base app, or a Playtest app with keys and store visibility set to Hidden.