Most indie demos are built like a nervous defense case. Here is the combat system, here is the crafting, here is the first boss, here is the map, here is the dialogue, here is the upgrade tree. The developer is trying to prove the game is real.
Players do not wishlist because you proved the game has enough stuff. They wishlist because one moment got stuck in their head.
That is the demo test I care about now. Can a stranger describe one repeatable moment from your game after ten minutes? Not the lore. Not the feature list. One moment they want to do again, send to a friend, or see get harder later.
Steam still treats demos as a separate store app, and Steam Next Fest is built around playable demos. That means your demo is often the first serious marketing asset a player touches. It has to behave like a playable pitch, not a tour of your backlog.
A Demo Is Not a Vertical Slice
A vertical slice is an internal production proof. It says, "the team can build this game." A demo is a public promise. It says, "this is the feeling you will pay to get more of." Those are different jobs.
I see teams confuse them all the time. They take the first thirty minutes of the game, polish it, and call it the demo. Sometimes that works. Usually it just means the demo inherits every slow tutorial beat from the full game.
The first thirty minutes of your game are often the worst marketing sample because they are full of setup. Controls. Exposition. Basic enemies. Empty pacing while the player learns what button does what. That material might be necessary in the full game. It is not automatically the best pitch.
Do not ask, "what part of the game can we show?" Ask, "what action do we want a player to repeat three times and still want a fourth?" Build toward that.
The Moment Has to Survive Retelling
A good demo moment has a sentence attached to it. "I kept rewinding time to save one doomed worker." "I built a deck that made every poker hand explode." "I tried to land on a tiny planet and missed by one meter."
That sentence is marketing. It is what players say in Discord. It is what a streamer says before clicking Start. It is what a Steam review says when the full game launches.
If your demo moment needs a paragraph of setup before it sounds interesting, it is probably not the moment. The moment can have depth later. The first hook needs a clean sentence.
The Feature Tour Demo
It shows five systems at shallow depth, then ends before any of them bite.
Players leave saying the game has potential, which is polite code for "I did not feel anything yet."
The Repeatable Moment Demo
It teaches one loop fast, then lets the player push it until something funny, tense, or surprising happens.
It needs discipline. You will cut good material because it distracts from the hook.
The Fake Trailer Demo
It starts with the loudest scene and hides the real pacing of the full game.
This gets clicks and bad conversion. Players can smell when the demo promised the wrong game.
Start With the Clip, Then Work Backward
Before you design the demo path, imagine the ten-second clip you want players to share. Not a cinematic trailer shot. A player-made clip. The thing that happens because they touched the system.
For a tactics game, maybe it is a risky chain reaction that wipes half the board. For a cozy game, maybe it is the first time two systems combine into a cute little accident. For a horror game, maybe it is the moment the player realizes the safe room was not safe.
Once you know the clip, the demo has a job: get players to that clip with enough context to care and enough control to feel responsible.
The Arena
Use it when your hook is mechanical, such as combat, deckbuilding, movement, or puzzle solving.
Games where repeat attempts are more persuasive than story setup.The Pressure Cooker
Use it when the hook depends on rising stress, limited resources, or a hard choice.
Survival, management, horror, and strategy demos.The First Day
Use it when the hook is routine, place, tone, or habit.
Cozy games, sims, narrative games, and social RPGs.Cut Anything That Delays the Second Attempt
The second attempt is where the demo starts selling. First attempt, the player learns. Second attempt, they make a plan. Third attempt, they start imagining the full game.
That means anything between attempt one and attempt two is dangerous. Long dialogue. Unskippable tutorials. Slow walks back to the action. Inventory sorting. Upgrade screens that do not change the next run. All of it cools the player off.
This is why roguelite demos often convert well even when they look rough. They restart fast. They let the player form a tiny theory and test it immediately. A polished demo with a two-minute walk back to the fun loses to a rough demo with a five-second retry.
- The player reaches the main repeatable action within three minutes.
- The demo creates a second attempt without making the player replay slow setup.
- The best moment can be described in one sentence by someone who did not read your pitch.
- The ending points at one specific full-game promise, not a generic "more content coming soon."
- The feedback form asks what players wanted to try again, not whether they liked the demo.
Prototype the Moment Before You Polish the Demo
You do not need the full demo to test this. You need a playable draft of the moment. That can be a messy Godot scene, a Unity graybox, a GDevelop prototype, or a quick 2D browser-playable version from an AI game studio like Chatforce. The tool matters less than the question: does the loop make someone want one more try?
I would rather watch five strangers play a crude version of the core moment than watch one polished trailer review from a friend. Friends compliment. Strangers quit. Quitting tells you more.
Steam Demos
Steam lets demos live as separate apps attached to the main store page, which makes the demo its own conversion surface.
Steam Next Fest
Steam Next Fest centers discovery around upcoming games with demos, so your playable pitch has to land quickly.
Chatforce
A prompt-to-game workflow for quick 2D browser-playable first versions, useful when you want to test a loop before committing production time.
Godot
A flexible open-source engine that works well when you want direct control over the prototype and eventual production build.
Unity
A full engine choice for teams that need broader platform support, asset store workflows, and custom production control.
The Demo Ending Should Sell the Next Question
Most demo endings are weak. They fade out, show a wishlist button, and say thanks for playing. That is fine as plumbing. It is not a sales beat.
A good ending leaves one clear question open. What happens when the enemy type changes? What happens when the tool upgrades? What happens when the town sees the consequence? What happens when the same loop gets meaner?
Do not tease ten locked menus. Tease the next pressure point. If the demo sold a repeatable moment, the ending should make the full game feel like a sharper version of that moment, not a bigger folder of features.
What to Measure After the Demo Goes Live
| Signal | What It Usually Means | What to Change |
|---|---|---|
| Players quit before the hook | Your setup is too slow or too unclear. | Move the hook earlier and cut tutorial text. |
| Players finish once but do not replay | The first loop is understandable but not tempting. | Add a clearer second goal or faster restart. |
| Players replay but do not wishlist | The loop works, but the full-game promise is fuzzy. | End on a sharper tease of what expands. |
| Creators play but do not clip it | The demo may be fun in hand but hard to explain visually. | Add a stronger readable payoff or reaction moment. |
Demo Strategy FAQ
How long should an indie game demo be?
Long enough for the player to understand the hook and want a second attempt. For many launch demos, 10 to 20 minutes beats a slow 45-minute sample.
Should the demo be the start of the game?
Only if the start reaches the real hook fast. If your opening is mostly setup, build a custom demo path around the repeatable moment.
Should I include a feedback form?
Yes, but ask behavior questions. "What did you try twice?" and "where did you stop?" are more useful than a 1 to 10 fun score.
The Point
Your demo is not an apology for being unfinished. It is not a product tour. It is not a little museum of everything you built.
It is a playable argument for one repeatable moment.
Find that moment. Get players to it fast. Let them repeat it. Then end by making the full game feel like the place where that moment gets deeper, stranger, harsher, or funnier. That is the demo that earns a wishlist.