Steam Playtest or Demo?
The honest answer is that it depends on your build, your calendar and what you need back. Answer seven questions and this tool gives you one of four calls -- Playtest now, Demo now, Playtest then Demo, or neither yet -- and shows you which of your answers drove it, plus what the runner-up was and why it lost.
The short version, if you skipped the tool
Run a Playtest when you need information. Ship a demo when you need attention. They are not two grades of the same thing. A Playtest is a gated child app that only exists as a Request Access option on your store page, and it deliberately cannot hurt you: Steamworks states that "a customer who has only participated in the Playtest cannot review your actual game". A demo is a public free product with its own App ID that can carry its own store page, its own reviews and its own placement in Steam's store lists.
The trade-off is symmetrical. The Playtest costs you nothing and buys you nothing in marketing terms -- Steamworks is explicit that "a customer's wishlist for your game won't be impacted when they join or leave your playtest". The demo is the only one of the two that generates wishlists, gets into Next Fest, and appears anywhere on Steam a free game can appear. It is also the only one of the two that can go permanently wrong in public.
So the real question is not "which is better". It is which risk you can afford this month: the risk of learning too late, or the risk of showing too early. That is why this is a tool and not a table -- the answer changes with your build stability, your runway, and whether you have a Next Fest deadline sitting on the calendar.
Steam Playtest vs Steam Demo: the differences that decide it
| Steam Playtest | Steam Demo | |
|---|---|---|
| Where it lives | A separate child App ID associated with your game. Steamworks: it "will not have its own store page; instead, it will be listed as an option available on the main game's store page". | A separate App ID associated with your full game's App ID. Since 2024 you can optionally enable an entire separate store page for it, with its own description, screenshots and feature list. |
| Who gets in | You decide. Limited signup grants access in batches as you have capacity; open signup approves automatically. You can also admit players only from selected countries. | Anyone, any time, for free. There is no gate and no approval step. |
| Discovery | Only found by people already on your store page. No store-list placement of its own. | Steamworks: demos "can appear anywhere in Steam that a free game could appear", including lists such as New & Trending and lists inside store hubs. |
| Reviews | Steamworks: "a customer who has only participated in the Playtest cannot review your actual game". A rough build cannot leave a permanent public mark. | If you enable a demo store page, players of the demo can leave user reviews on it. Without that page there is nowhere for demo reviews to appear. |
| Wishlists | Steamworks: "a customer's wishlist for your game won't be impacted when they join or leave your playtest". Any effect is indirect store-page traffic. | One-time wishlist notification to everyone holding the full game, triggerable from the demo app landing page for two weeks after the demo first becomes playable. Steam also adds a prominent link from the demo page back to the full game. |
| Next Fest | Does not satisfy the requirement. Allowed -- Valve says "use of a Steam Playtest does not affect eligibility" -- but Valve does not recommend running one during the fest. | Mandatory. Eligibility requires a title that "will include a publicly playable demo by the time Next Fest begins". |
| Cost | Steamworks: "Steam Playtest is a completely free feature for both customers and Steam developers". | Free to players and no additional Steam Direct fee. The cost is production time and the fact that you only get one first impression. |
| Best at | Bug reports, telemetry, difficulty and balance data, multiplayer population tests. | Wishlists, press and streamer coverage, store-list discovery, Next Fest entry. |
Quotations above are from Steamworks documentation: Steam Playtest, Demos and Steam Next Fest.
When each one wins
A Playtest wins when
- The build still crashes, softlocks or eats saves. The Playtest is the only surface where that is survivable.
- You have no launch date, or launch is more than six months out. Wishlists collected now have the longest possible time to go cold; feedback does not decay the same way.
- What you want back is bug reports, telemetry and balance data rather than wishlists.
- The game needs concurrent players to be evaluated at all. A controlled Playtest window guarantees a population; a public demo for a multiplayer game risks empty lobbies as a first impression.
- Your content is right in systems but wrong in presentation. Playtest testers read past placeholder art; demo players read it as the game.
- You already have a large wishlist audience, so reach is not the scarce resource -- confidence is.
A Demo wins when
- You are entering a Next Fest. There is no alternative: the fest requires a publicly playable demo by the time it begins.
- Launch is one to three months away, which is where demo-driven wishlists are freshest at the moment they can convert.
- Your slice is representative of the finished game, so the judgement players form from it is a judgement you would accept.
- You need reach. The demo is the only one of the two with its own discovery: it can appear anywhere on Steam a free game can appear.
- Nobody on the team has bandwidth to work a feedback queue. A demo runs without you in the loop; a Playtest does not.
- You want the one-time wishlist notification to land while there is still something to convert it with.
And when the answer is "neither yet"
Three conditions make both surfaces a waste this month. The tool treats them as hard blockers rather than as points on a scale, because no amount of good news elsewhere makes them false:
- You have no published store page. Neither surface exists without one: a Playtest is a child appID that, in Valve's words, "will not have its own store page; instead, it will be listed as an option available on the main game's store page", and Next Fest eligibility requires that "the base game store page must be published and public". Publish a Coming Soon page first -- it is also the only thing that can collect wishlists while you build.
- The build crashes and it is not representative of the game. A Playtest forgives rough, but it cannot tell you anything useful about a game this build does not resemble -- you would spend a tester list to learn that a test harness is a test harness. Get to a slice that runs, then come back.
- The build crashes and nobody is free to act on feedback. Every report you collect in the next month lands in a backlog you have already told me you cannot work. Testers notice, and the goodwill does not come back cheap.
How Next Fest changes the answer
Next Fest is the single input that can override everything else, for one reason: a title may only ever participate in ONE Next Fest. You do not get a second attempt with a better build, and Valve will not accept "a different version or edition of a title that has previously participated". So the fest is not a marketing beat you can schedule twice -- it is a one-shot resource, and a demo is the only key that opens it.
| Edition | Dates | Registration deadline |
|---|---|---|
| October 2026 | Oct 19 to Oct 26, 2026 (10:00am PDT to 10:00am PDT) | Aug 31, 2026, 11:59pm PDT |
| February 2027 | Feb 22 to Mar 1, 2027 (10:00am PST to 10:00am PST) | Jan 10, 2027, 11:59pm PST |
| June 2027 | Jun 14 to Jun 21, 2027 (10:00am PDT to 10:00am PDT) | Apr 25, 2027, 11:59pm PDT |
For the October 2026 edition there are three dates behind the registration deadline that developers routinely miss: demos should be live by September 21 to be playable for the press preview, all required items are due October 5, and the press preview itself starts October 8. Registration on August 31 is the gate; the build deadline is the one that actually hurts.
Valve's published eligibility criteria
- Has not previously joined a Next Fest; titles may only participate in ONE Next Fest
- Is associated with a Steamworks developer account(s) in good standing
- The base game store page must be published and public
- Will include a publicly playable demo by the time Next Fest begins
- Will not be released before the applicable Next Fest edition concludes
- Is not a prologue, preview, or short-form version of an existing game already released on Steam
Two of those bite quietly. The fourth is why a Playtest can never be your Next Fest entry. The fifth is why an Early Access launch scheduled before the fest ends removes your eligibility -- Valve's own wording is that "if you plan on entering Early Access or launching your game for free, that's fine, but the game must not yet be released to remain eligible for Next Fest".
Having a Playtest does not disqualify you. Asked directly whether games with a Playtest are eligible, Valve answers "yes, as use of a Steam Playtest does not affect eligibility", then immediately adds: "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". That is guidance, not a rule -- but it is the only published word on running both at once, and it points the same way our tool does.
Valve's fest tips add one operational detail worth acting on: if you intend to take the demo down afterwards, "indicate on your demo home screen if you will deactivate the demo, and when", because plenty of players download demos during the fest meaning to play them later. Sources: Next Fest rules, October 2026 edition, Next Fest tips.
What changed in 2024, and why older advice is stale
Most playtest-versus-demo advice on the internet predates Valve's 2024 demo overhaul and describes a demo as a button on your store page. That is no longer the whole picture, and the difference changes the risk calculation on both sides.
- A demo can have its own store page. Steamworks: you can "optionally choose to enable an entire separate store page for your demo" with its own written description, screenshots and feature list. It still lives on a separate App ID associated with the full game.
- Demos can be reviewed. Enabling the demo store page means "your demo will let players of the demo leave user reviews". If you do not enable that page, there is no page for demo reviews to appear on. Whether demo reviews feed the base game's review score is not officially documented; the observed pattern is that they are scored on the demo page itself, the way any free product on Steam is.
- Demos are discoverable on their own. Steamworks: demos "can appear anywhere in Steam that a free game could appear. This includes lists such as the ‘New & Trending’ as well as lists within store hubs". This is the single biggest argument for a demo over a Playtest when your wishlist count is low.
- The demo wishlist notification is a one-shot. Once your demo is playable for the first time you can trigger notifications to players who already have the full game wishlisted. It is available from the demo app landing page for two weeks, and wishlist notifications carry a two-week cooldown per App ID. Spend it on the build you want judged.
- The Playtest side did not change much. It remains free for developers and customers, still has no store page of its own, still gates access in batches, and still cannot produce a review on your game. That stability is the point: it is a lab, not a shop window.
If you read our Playtest vs Demo guide before mid-2024, re-read the demo half. The strategic conclusion in that piece -- Playtest to fix it, demo to sell it -- still holds. The mechanics underneath it moved.
Every rule this tool uses
No black box. Below is the complete rule set, grouped by question. Each answer pushes toward some recommendations and against others; the tool sums them, then applies the three blockers listed above, which override everything.
How stable is the build a stranger would download today?
| If you answer | Pushes toward | Pushes against |
|---|---|---|
| Crashes or hard blockers in a normal session | Run a Playtest now, Playtest now, Demo later, Neither yet | Ship a Demo now |
| Playable end to end, but rough | Playtest now, Demo later, Run a Playtest now | Ship a Demo now |
| No known blockers, presentation is final | Ship a Demo now | Run a Playtest now, Playtest now, Demo later |
How long until you plan to launch?
| If you answer | Pushes toward | Pushes against |
|---|---|---|
| No date set | Run a Playtest now, Playtest now, Demo later | Ship a Demo now |
| More than 12 months | Run a Playtest now, Playtest now, Demo later | Ship a Demo now |
| 6 to 12 months | Playtest now, Demo later, Run a Playtest now | Ship a Demo now |
| 3 to 6 months | Playtest now, Demo later, Ship a Demo now | -- |
| 1 to 3 months | Ship a Demo now | Run a Playtest now, Playtest now, Demo later |
| Less than 1 month | Ship a Demo now | Playtest now, Demo later, Run a Playtest now |
Do you intend to enter a Steam Next Fest, and which one?
| If you answer | Pushes toward | Pushes against |
|---|---|---|
| Yes -- October 2026 | Ship a Demo now, Playtest now, Demo later | Run a Playtest now, Neither yet |
| Yes -- February 2027 | Playtest now, Demo later, Run a Playtest now, Ship a Demo now | -- |
| Yes -- June 2027 | Playtest now, Demo later, Run a Playtest now, Ship a Demo now | -- |
| Yes, but I have not picked an edition | Playtest now, Demo later, Run a Playtest now | -- |
| No -- I have already used my one Next Fest | Run a Playtest now, Playtest now, Demo later | Ship a Demo now |
| No Next Fest planned | Run a Playtest now, Playtest now, Demo later | -- |
Where is your store page, and how many wishlists does it hold?
| If you answer | Pushes toward | Pushes against |
|---|---|---|
| Not created yet | Neither yet | Run a Playtest now, Ship a Demo now, Playtest now, Demo later |
| Built, but not public yet | Neither yet | Ship a Demo now |
| Live -- under 1,000 wishlists | Ship a Demo now, Playtest now, Demo later | Run a Playtest now |
| Live -- 1,000 to 5,000 wishlists | Ship a Demo now, Playtest now, Demo later | -- |
| Live -- 5,000 to 10,000 wishlists | Run a Playtest now, Ship a Demo now, Playtest now, Demo later | -- |
| Live -- more than 10,000 wishlists | Run a Playtest now, Playtest now, Demo later | Ship a Demo now |
What do you actually want back from this?
| If you answer | Pushes toward | Pushes against |
|---|---|---|
| Bug reports, telemetry, balance data | Run a Playtest now, Playtest now, Demo later | Ship a Demo now |
| Wishlists, press, streamers | Ship a Demo now, Playtest now, Demo later | Run a Playtest now |
| Honestly, both | Playtest now, Demo later, Run a Playtest now, Ship a Demo now | -- |
Can you read and act on feedback over the next 4-6 weeks?
| If you answer | Pushes toward | Pushes against |
|---|---|---|
| Yes -- someone owns feedback | Run a Playtest now, Playtest now, Demo later | -- |
| Some -- we can triage, not iterate | Playtest now, Demo later | -- |
| No -- we are heads-down on content | Ship a Demo now, Neither yet | Run a Playtest now, Playtest now, Demo later |
Is the content you would ship representative of the final game?
| If you answer | Pushes toward | Pushes against |
|---|---|---|
| Yes -- a vertical slice at final quality | Ship a Demo now | Run a Playtest now |
| The systems are right, the presentation is not | Playtest now, Demo later, Run a Playtest now | Ship a Demo now |
| No -- it is a test harness or one mechanic | Run a Playtest now, Neither yet | Ship a Demo now, Playtest now, Demo later |
Frequently Asked Questions
Should I do a Steam Playtest or a demo?
Run a Playtest when you need information and a demo when you need attention. A Playtest is a gated child app listed on your store page that you let players into in batches, and Steamworks confirms that a customer who has only participated in the Playtest cannot review your actual game, so a rough build cannot leave a permanent mark. A demo is a public free product that can carry its own store page, can appear anywhere on Steam that a free game can appear, and can trigger a one-time wishlist notification. If your build still crashes, or your launch is more than six months out, or you mainly want bug reports, Playtest first. If your content is representative of the finished game, your launch is one to three months out, or you are entering a Next Fest, ship the demo.
Does a Steam Playtest count for Steam Next Fest?
No. Next Fest eligibility requires that a title will include a publicly playable demo by the time Next Fest begins, and a Playtest does not satisfy that requirement. Having run a Playtest does not disqualify you: Valve states that use of a Steam Playtest does not affect eligibility. But Valve also advises against running one during the event, because it splits your players between the two builds instead of concentrating them in one spot.
Do Steam Playtests generate wishlists?
Not directly. Steamworks states that a customer's wishlist for your game will not be impacted when they join or leave your playtest. Players do have to visit your store page to request access, so there is some indirect page traffic, but the Playtest has no store page of its own and does not appear in Steam's store lists. If wishlists are the goal, the demo is the surface that moves them.
Can I run a Steam Playtest and a demo at the same time?
Technically yes. They are separate child App IDs and neither blocks the other. Valve's only published objection is specific to Next Fest: it does not recommend having a Playtest live during Steam Next Fest because that splits your players between the two builds. Outside a fest, Valve does not document a restriction, so treat the case against it as judgement rather than policy: the same audience-splitting argument applies, plus the confusion of offering a store page visitor two different ways to play.
Can a game participate in Steam Next Fest twice?
No. Valve's eligibility rules state that titles may only participate in ONE Next Fest, and that you may not submit a different version or edition of a title that has previously participated. Entry also requires that the game will not be released before that edition concludes, so launching into Early Access or releasing for free before the fest ends removes your eligibility as well.
Does a Steam demo get its own store page and its own reviews?
Optionally, yes. A demo is a separate App ID associated with your full game's App ID, and since Valve's 2024 demo update you can choose to enable an entire separate store page for the demo, with its own written description, screenshots and feature list. Enabling that page also lets players of the demo leave user reviews on it. If you do not enable a separate demo store page, there is no demo page for reviews to appear on. Demos can also appear anywhere on Steam that a free game could appear, including lists such as New and Trending and lists inside store hubs.
Do demo reviews affect my game's review score?
Valve does not officially document a link between the two. The observed pattern is that demo reviews sit on the demo's own store page and are scored there, the way reviews work for any other free product on Steam, rather than being folded into the base game's review score. Treat that as the working assumption rather than as published policy, and note that it is not a free pass either: a poorly received demo page can still shape what a player reads before they ever reach your base game page.
When is the next Steam Next Fest and when does registration close?
The October 2026 edition runs October 19 to October 26, 2026, opening and closing at 10:00am PDT. Registration closes August 31, 2026 at 11:59pm PDT, demos should be live by September 21 to be included in the press preview, and all required items are due October 5. Valve has also published two 2027 editions: February 22 to March 1, 2027, with registration closing January 10, 2027, and June 14 to June 21, 2027, with registration closing April 25, 2027.
Related Resources
Steam Playtest vs Demo
The long-form comparison this tool is built on: setup, control, player expectations, and the sequence most studios should run.
Steam Demo Best Practices
How long a demo should be, where to end it, and how to build the wishlist prompt that turns a play session into a conversion.
Next Fest Prep Tool
Live countdown to the October 2026 fest with every registration, build and asset deadline, plus the prep checklist.
Store Page Checklist
If the tool told you to publish the store page first, start here. Everything that has to be right before either surface goes live.
Sources
Every mechanic asserted on this page comes from official Steamworks documentation, verified in July 2026. Where Valve has not published a rule, this page says so rather than guessing.
Disclaimer: Steam policy changes. Dates and eligibility rules were verified against Steamworks in July 2026 -- confirm the edition page for your fest before you register. The recommendation is a weighted opinion built from published Valve mechanics and observed developer practice, not a Valve product or endorsement.