Quick answers
- Steam Playtest is a free, separate “child” app for testing a rough build. Its reviews, playtime and wishlists stay apart from your main game, you control who gets in, and you can switch it off at any time. You can't charge for it.
- A demo is a free, separate app that shows a polished slice of the game so players can try before they buy. It's required for Steam Next Fest, and it gives you one wishlist notification.
- Early Access isn't a separate app: it's your real game, released and on sale while you keep developing it. Once it's out you can't go back to Coming Soon, and it counts as released for Next Fest.
- Typical solo-dev order (ours): Coming Soon page, then Playtest, then a demo for Next Fest, then Early Access or 1.0 after the fest.
Playtest vs demo vs Early Access: side by side
| Steam Playtest | Demo | Early Access |
|---|
| Purpose | Free, lower-risk testing with live players “without stressing out about Steam keys, user reviews, or wishlists” | A free, playable portion of the game so customers can try before they buy | Selling the game while it's still in development, as a playable alpha or beta that is “worth the current value of the playable build” |
| Separate app? | Yes, a child app ID created from your game's Associated Packages & DLC page | Yes, its own app ID with its own release checklist, created from “All associated packages, DLC, demos and tools” | No, it's your main game with the Early Access checkbox turned on |
| Store page | None of its own: the signup shows as a section on your main game's page | Optional separate demo page; either way a demo button shows on the main page (re-publish the main page after releasing the demo). No Community Hub for demos | Your main store page, with Early Access branding and an Early Access Q&A that players see |
| Valve review | Simplified store and build review; the store checklist is only capsule images and icons | Store presence and build review. For Next Fest, the store presence review is needed even without a separate demo page | Store page and Q&A reviewed before release; if you turn on Early Access on a Coming Soon page, the page is reviewed again |
| User reviews | Kept apart: a player who has only been in the Playtest can't review your actual game | Players can leave reviews on the demo if you enable the separate demo store page | Normal reviews on your game. After 1.0, reviews written during Early Access are labeled as such |
| Wishlists and visibility | Joining or leaving doesn't change a player's wishlist; signup traffic lands on the main page where players can wishlist | One wishlist notification (email and mobile), sent by you within 14 days of the demo's first release. Demos can appear anywhere a free game can, such as New & Trending and tag pages | Wishlisters get an email when you launch in Early Access and again at full release. Early Access launches don't get the same launch visibility as a 1.0 release; that comes when you leave Early Access |
| Steam keys | Standard Release keys only, even before your store page is public; much larger batches than the usual 2,500 beta keys. Never sell them | You can request demo keys (for example to test on accounts outside your team); keys only for a demo that's also on Steam | Usual key rules; third-party key sellers must show Early Access branding and current info, at no higher price than Steam |
| Can you charge? | No, and no in-game transactions either | No, demos are free | Yes, it's a full purchase of the game as it is today |
| Next Fest | Doesn't affect eligibility, but Valve recommends not running it during the fest | Required: a publicly playable demo by the start | Only before you launch: Next Fest is for unreleased games, so a live Early Access game no longer qualifies |
| Ending it | Set it to Not Playable any time (turn off signups first) and restart later; keys already given out aren't revoked unless you reset the Playtest | Deactivate and reactivate any time; players keep it in their library but can't launch it through Steam | Release 1.0 when it's feature complete. You can't go back to Coming Soon. If you stop development, contact Valve: drop the Early Access tag (permanent, no launch visibility) or retire the game |
Steam Playtest: free testing that can't hurt your reviews
Valve built Playtest because developers kept faking it with “a demo that was really just an Open Beta” or a free prologue. The Playtest app has the same Steamworks features as your game (cloud saves, Steam Input templates and so on), but players reach it through a signup button on your main store page.
- Who gets in: by default signups are limited and you admit players in batches, picked at random; you can limit batches to certain countries if server capacity is the issue. Switch to open signup and everyone who asks gets in. For multiplayer, Friend Invites let each player invite 1, 2 or 3 friends they've been friends with for at least 30 days.
- Keys: you can hand out Playtest keys without any public signup, even before your store page is live. Valve says that past 50,000 keys “your playtest is effectively an open beta”, so open the signups instead.
- Not confidential: players aren't under an NDA. For an unannounced game Valve suggests announcing first; a “friends & family” test is safest on your base app with Release State Override keys (limited to 2,500 per app), with your own NDA process.
- Feedback is your job: Steam doesn't collect it. Valve has seen developers put a big feedback button on the main menu that links to a Discord, forum or bug tracker. Steam also doesn't email players when the Playtest becomes playable, so post an announcement.
- After launch: Valve notes a Playtest is free for players, so keeping one up after release “probably only makes sense if your game is already free-to-play.”
To turn tester notes into fixes faster, see AI tools for game playtesting and QA. Remember that Valve's build review only checks that the game launches and has the features you list; its Next Fest docs say it “is not a full QA process”. Automated testers such as nunu.ai and modl.ai play a build from plain-English tasks and report bugs, which helps before strangers see it.
Demos: a polished slice that sells the full game
Valve's advice on demos is about quality, timing and length: players use a demo to decide whether to buy, so it should measure up to the real game, and it shouldn't give away so much that they feel they've seen everything. Valve “generally” recommends waiting until launch for a demo, but says a pre-release demo makes sense when players need to touch the game to understand it. That's also how Next Fest works.
- The one-time wishlist notification: after the demo first goes playable, a button on the demo's landing page sends an email and mobile notification to everyone who wishlisted the full game. You can press it once, within 14 days. Deactivating and reactivating the demo doesn't give you another one.
- Cooldown: wishlist notifications have a two-week cooldown per app, so Valve suggests spacing the demo notification at least two weeks from other wishlist triggers such as your release or a discount.
- Carrying progress over: once the full game is out, you can share depots and Steam Cloud saves so demo players continue where they left off. Valve recommends turning achievements off in the demo and granting them in the full game instead (setup and icons: Steam achievements for indie games).
- Multiplayer: Steam doesn't support matchmaking between demo players and full-game players.
- Turning it off: you can deactivate a demo after a festival. It may still launch outside Steam unless it checks for a Steam license (ISteamApps::BIsSubscribedApp). After Next Fest, Valve encourages leaving the demo up for a while, since players are disappointed when demos vanish right away.
No “pay to keep playing” builds: Steam's pricing FAQ says it doesn't support models where players are blocked and have to pay to continue. Use a free demo and a paid full game instead.
Early Access: selling an unfinished game
Early Access is for a game that's already fun and playable now and that you'll keep building with your players. Valve is blunt about what it isn't: not a way to crowdfund development, not a pre-purchase (players get a playable game the moment they buy), and not the “advance access” other stores call early access. Its rules include:
- Don't make specific promises about future features or dates. Players should buy the game for what it is today.
- Don't launch without a playable game. A tech demo, or a concept where you haven't found the fun yet, is too early. At a bare minimum you need a video trailer that shows gameplay.
- Don't launch in Early Access if development is finished and you only need bug testing; Valve suggests keys for fans or more internal playtesting instead.
- Keep the Steam price no higher than anywhere else, and don't sell it on Steam later than elsewhere.
- Set expectations everywhere you sell it, for example if updates will break save files.
Setup: tick the Early Access checkbox on the Early Access tab of your store page settings and answer the Q&A (why Early Access, roughly how long, how the full version will differ, the current state, whether the price will change, how the community is involved). Valve reviews it before you can release. If you already have a Coming Soon page you can switch Early Access on yourself, but the page is reviewed again, and a game that's already released can't move back into Early Access.
Pricing: there's no rule on Early Access vs final price; most developers start lower and raise it, some start higher. You can't run a permanent discount in Early Access, so set a lower base price instead. Any price increase blocks discounts for 30 days, so if you raise the price within 30 days of leaving Early Access, your 1.0 launch discount won't apply. Valve's pricing FAQ asks you to request the price change a couple of days before the transition.
Staying in Early Access: Valve suggests revisiting your Early Access store page at least once a year. If more than 12 months pass without a build on the default branch or an “update” type event, Steam adds a notice to the store page saying the game hasn't been updated in a while. In Early Access you also have to wait two weeks after launch before you can start an Update Visibility Round.
Leaving it: when the game is feature complete, upload the build and press Release in the release options. That removes the Early Access branding, applies any launch discount, emails your wishlisters again, and gives you the full launch visibility of a first release.
Which should a solo dev use when?
Our recommendations, based on the rules above:
- Your vibe-coded prototype runs but you don't know if it's fun: Playtest. Admit 50 or 100 people from the signups, watch what they do, and turn it off when you've learned enough. It can't touch your reviews.
- Multiplayer and you need players online at the same time: Playtest with scheduled sessions (Valve says limited-time server windows are fine) and Friend Invites if your servers can take the growth.
- You're aiming for Next Fest: a demo, published on a public Coming Soon page, with the Playtest switched off during the fest so players aren't split between two builds.
- You need income and the game is already worth buying: Early Access, but only if you're ready to keep updating it for a long time and wouldn't be ruined by low sales. Valve calls it “a marathon, not a sprint”.
- The game is basically done: skip Early Access. Run a Playtest or send keys for bug testing, then launch 1.0 and get the full launch visibility.
- You want to test, then pull the build down later: Playtest. Valve's Early Access FAQ says that once a game is out in Early Access you can't take it down and go back to Coming Soon.
- A browser game you'd monetize with ads: none of these fix that. Steam doesn't allow advertising-based business models, so plan a paid or free build without ad SDKs (see how to put an HTML5 game on Steam).
Timeline example: Playtest, Next Fest demo, then Early Access
One way to sequence all three around the February 2027 Next Fest (our example; the dates in bold are Valve's for that edition, all PST):
| When | What | Rule behind it |
|---|
| November 2026 | Store page marked ready for review, then posted as Coming Soon so wishlists can start | Submit at least 7 business days before you want it live; review typically takes 3-5 business days |
| December 2026 | Run a limited Playtest in batches; add an in-game feedback button | Playtest is best after the Coming Soon page is up and before release |
| By January 10, 2027, 11:59pm | Register the base game for Next Fest; have a trailer and up-to-date store page by then if you want a shot at the official Next Fest trailer | Registration deadline; the base game's store page must be published and public |
| By February 1 (or January 18 for Press Preview) | Submit the demo build and demo store presence for review | All items due by February 1; January 18 if you want the demo live for Press Preview on February 11 |
| Before February 22, 10am | Set the Playtest to Not Playable (signups off first), release the demo (Valve suggests at least 30 minutes early), re-publish the main store page, send the demo wishlist notification | Next Fest starts; the notification must go out within 14 days of the demo's first release |
| February 22 - March 1 | Next Fest. Leave the demo up afterwards | The game must not release before the fest ends |
| Mid-March 2027 or later | Launch in Early Access (or 1.0), at least two weeks after the demo notification | Wishlist emails have a two-week cooldown per app, so players emailed about the demo may not get the launch email sooner (our reading) |
| Every few months, at least yearly | Update the Early Access Q&A, post update events, ship builds | Steam flags Early Access games with no update for 12 months |
Missed February? The next Next Fest is June 14-21, 2027, and Valve's general workback is: demo build submitted 3 weeks before the fest (5 weeks if you want it live for Press Preview), Press Preview 11 days before, and the fest trailer 4 days before. A game can only take part in one Next Fest, so pick the edition closest to the build you're proudest of. The fee, paperwork and minimum waits are in our Steam launch checklist.
Checklist
- Coming Soon page public before you run a public Playtest, a demo or Next Fest
- Playtest: capsule images and icons done, signups enabled under Special Settings on the main store page, a feedback link in the game, an announcement when it goes playable
- Playtest keys: never sold or bundled; remember a key isn't revoked when you mark the Playtest Not Playable
- Demo: application type set to Demo with your base game's App ID; capsules clearly say it's a demo; separate page (if any) lists only what's in the demo, with a trailer and at least 5 demo screenshots; Content Survey matches the demo
- Demo: achievements off, main store page re-published after release, wishlist notification sent within 14 days, spaced from other wishlist emails
- Early Access: playable build worth its price today, gameplay trailer, Q&A answered honestly, no promised dates or features, the same or lower price than other stores
- Early Access: Next Fest done first (if you want it), price changes planned around the 30-day discount rule, a plan for regular updates
- AI-made content in any of the three builds disclosed in the Content Survey (see Steam AI disclosure)
Related: Steam launch checklist · put a web game on Steam · AI tools for playtesting and QA · AI for trailers and Steam store pages · Steam AI disclosure.
Planning a Steam launch? Get the VibeStack Weekly digest: new AI game-dev tools and Steam rule changes, every Monday.
Sources (checked October 29, 2026), all Steamworks Documentation unless noted: Steam Playtest; Demos; Early Access; Steam Next Fest and Steam Next Fest: February 2027; Upcoming Steam Events; Coming Soon; Review Process; Release Process; Steam Direct Fee; Wishlists; Visibility on Steam; User Reviews; Steam Keys; Pricing; and Steam's player-facing Early Access page (store.steampowered.com/earlyaccessfaq). The “which should I use” advice, the timeline example and the tip about spacing wishlist emails are ours, built from those pages, not Valve's. Valve changes rules and dates, so check the linked docs before each step.
Get the Starter Stack ($12) Get the free weekly digest
FAQ
What's the difference between Steam Playtest and a demo?
Both are free, separate app IDs. A Playtest is for testing a work-in-progress build: players sign up on your main store page, you admit them in batches or open it to everyone, and you can switch it off any time. A demo is a polished slice meant to sell the full game; it can have its own store page, it's required for Steam Next Fest, and it lets you send one wishlist notification within 14 days of its first release.
Can I charge for a Steam Playtest?
No. Valve says Playtest is designed for free signups, you can't monetize it with in-game transactions or sell access, and you should never sell Playtest keys or put them in paid bundles. If you want to charge for a work-in-progress version, Valve points you to Early Access.
Does a Steam Playtest affect my reviews or wishlists?
No. The Playtest is a separate app ID, so playtime, wishlists, reviews and refunds are separate too. A player who has only been in the Playtest can't review your actual game, and joining or leaving the Playtest doesn't change their wishlist.
Can an Early Access game join Steam Next Fest?
Only before it launches. Next Fest is for unreleased games; Valve's FAQ says games planning to enter Early Access can take part, but the game must not be released yet. Once your Early Access version is on sale, it's released and no longer eligible.
Can I go back from Early Access to Coming Soon?
No. Valve says Early Access is for games that stay available and playable while development continues. If you want to test a build and take it down later, use Steam Playtest. A released game also can't move back into Early Access.
Should I keep my Playtest running during Next Fest?
Valve says having a Playtest doesn't affect Next Fest eligibility, but it doesn't recommend running one during the fest because it splits players between two builds. Push everyone to your demo instead.
Can I raise my price when leaving Early Access?
Yes. Request the price change a couple of days before the transition. Any price increase blocks discounts for 30 days, so if you raise the price within 30 days of your 1.0 release, your launch discount won't apply.
Do Steam demos get user reviews?
If you enable the optional separate store page for your demo, demo players can leave reviews on it. Demos never get their own Community Hub, and the demo always shows as a button on your main game's store page.