How to update a Steam demo, and when to take it down
A Steam demo is its own app with its own App ID, depots and builds, so you update it like any app: upload a new build to the demo's depots with SteamPipe and set it live on the default branch. Valve's review process says that once a product has been reviewed and approved there is no need to go through review again. A demo with its own store page keeps its user reviews across updates, and demos have no community hub, so announce changes on the base game. The demo's wishlist notification is one-time and cannot be re-sent, and each game gets one Next Fest. Deactivating a demo stops downloads and launches, and can be undone; Valve encourages keeping demos up after Next Fest.
AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.
Intel or AMD Chromebook, with Linux turned on.
A demo is a living build
A demo that went up for Next Fest and never changed is showing a months-old game to every new player who finds it. The full game has better art, fewer bugs and a stronger opening; the demo still has the version you shipped in a rush the week before the festival.
The obvious move after a festival is to leave the demo alone and work on the game. A better one is to treat the demo as the first thing a new player sees, because it often is: refresh it when the game's first minutes improve, and say so.
How to update it
- Build the new demo from the current game, with the same content limits as before unless you mean to change them.
- Upload it with SteamPipe to the demo's own App ID and depots, not the base game's.
- Set the build live on the demo's default branch in Steamworks.
- Test the live build by downloading it through Steam on a clean machine.
- Post an announcement on the base game: what changed, especially fixes players asked for.
No new review is needed: Valve's review process says that once a product has been reviewed and approved, there is no need to go through review again. See uploading a build with SteamPipe.
Valve's Steamworks documentation: Demos, Branches (Betas), Review Process.
What carries over, and what does not
What an update keeps and resets, from Valve's documentation:
| Thing | After an update |
|---|---|
| User reviews (with its own page) | Kept; players can edit their own reviews |
| Players' demo saves | Kept if they are in Steam Cloud and the format still loads |
| Wishlist notification | Not sent again; it is one-time, within 14 days of first release |
| Next Fest | No second entry; each game takes part once |
| Store page | Unchanged until you edit it; new screenshots if the demo changed |
| Library entries | Players get the new build automatically |
Valve's Steamworks documentation: Demos, Steam Next Fest, User Reviews.
When to update
- After Next Fest: fix what the festival's players complained about, while their reviews and comments are fresh.
- When the first minutes improve: a better opening, art pass or tutorial is worth shipping to the demo.
- Before a beat: a festival, a creator push, a release date announcement or a launch; the demo will get traffic.
- When a bug blocks the ending: players who cannot reach the last screen never see the wishlist prompt.
- Not every week: each update risks a new bug; batch fixes and test them.
Saves, versions and the full game
If demo saves carry over to the full game through shared Steam Cloud storage, every update has to keep loading old saves, or players lose progress twice. Version the save format and migrate it. Valve's documentation notes a shared depot can be mounted into the demo only after the full game is released, so before launch, demo and game builds are uploaded separately. And demo players cannot matchmake with full-game players, so a multiplayer demo needs its own player pool.
Valve's Steamworks documentation: Demos, Steam Cloud.
Reviews
A demo with its own store page collects user reviews, and they stay with the demo through updates. Reply to them, fix what they name, and mention the fixes in the update's announcement. A demo with old negative reviews and a changelog that answers them reads well; one with old negative reviews and no reply reads like the game has not changed.
When to take it down
Keep a demo up while it earns wishlists and does not give away too much. Valve encourages leaving demos up after Next Fest, noting that players complain when demos disappear straight after. Consider taking it down when:
- It shows most of a short game, so players feel they have finished it.
- It is far behind the full game and misrepresents it, and updating it is not worth the work.
- Its reviews are weaker than the full game's after launch, and it is pulling the first impression down.
Deactivating it, under Technical Tools on the demo's landing page, stops downloads and launches; owners still see it in their library but cannot launch it, and you can reactivate it later. Players can still run an existing copy outside Steam unless the demo checks its license with BIsSubscribedApp. Separately, you can remove a demo's own store page, and its old links redirect to the full game.
Valve's Steamworks documentation: Demos, Steam Next Fest.
Test it on a private branch first
A demo has its own App ID, so it has its own branches in SteamPipe. Before setting a new build live on the default branch, set it live on a password-protected beta branch, install it through Steam on a clean machine, and play it from the first screen to the wishlist prompt. Check that an old save still loads, that the store link on the last screen opens the right page, and that the build runs on a low-end machine. Only then move it to the default branch. A broken demo update is seen by every new player until you notice, often for days, and it can cost reviews that stay on the demo's page long after the fix. Ten minutes on a private branch is cheap insurance, and the same branch is where you can let a few community members try the update before everyone else does.
Valve's Steamworks documentation: Branches (Betas).
Where the principle breaks
Updating is not always better. A demo that is earning wishlists at a good rate has a working first impression; a big content change can break it. Change one thing at a time, and watch demo players to wishlists and median playtime for a week after each update. If the numbers fall, roll back to the previous build, which SteamPipe keeps, and try the change again on a private branch with a few testers before it goes back to everyone.
Valve's Steamworks documentation: Uploading to Steam.
Where Flockbay fits
Flockbay's playtest links test each demo update on testers' machines before you upload it, with crashes, frame times and play time reported back. Building is free to start; playtest links are a paid feature.
Questions
- Does a Steam demo update need Valve review?
- No. Valve's review process says that once a product has been reviewed and approved, there is no need to go through review again. Upload the build to the demo's App ID and set it live.
- Can I send the demo wishlist email again after an update?
- No. The demo notification can be triggered once, within 14 days of the first playable release, and disabling and re-enabling the demo does not reset it.
- What happens when I deactivate a Steam demo?
- It can no longer be downloaded or launched through Steam; owners still see it in their library. You can reactivate it later.
- Should I keep my Steam demo up after launch?
- Usually yes, while it earns wishlists and sales and reflects the full game. Take it down if it gives away most of a short game or drags the first impression below the full game's.
Flockbay builds and play-tests your game and its demo, free to start.
Download Flockbay freeAppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.
Intel or AMD Chromebook, with Linux turned on.
