A game demo can answer more than “does this look fun?” if you test it deliberately. This checklist shows how to evaluate playable content, performance, progression, controls, accessibility, online requirements, and monetization before deciding whether an indie game is worth buying.
Overview
A demo is useful evidence, but it is not automatically a complete preview of the finished game. Some demos are short slices designed to introduce a story or mechanic. Others are early builds, festival versions, prologues, or standalone samples that may differ from the eventual release. Your goal is not to finish every available objective. It is to collect enough information about the parts that matter to you.
Before playing, write down your decision criteria. For example, a narrative adventure may need convincing writing, readable subtitles, and stable controller support. A platformer may depend on movement precision, frame pacing, and checkpoint design. A cooperative game needs reliable joining, communication options, and clear information about whether online play is required. This prevents a visually impressive demo from distracting you from a deal-breaking problem.
Also record the demo version, platform, and date you tested it. Developers can revise demos, change hardware requirements, or remove trial builds. If you are comparing several upcoming indie releases, consistent notes make the comparison more useful than relying on memory.
Checklist by scenario
Use the checks below according to the kind of game you are considering. Mark each item as confirmed, unclear, or unacceptable rather than treating the demo as a simple yes-or-no review.
| What to check | Questions to ask | Why it matters |
|---|---|---|
| Playable content | How much can you play? Is it a tutorial, a complete short scenario, or a section taken from later in the game? | A polished opening may not represent the variety, pacing, or difficulty of the full release. |
| Time and content limits | Does the demo end after a timer, a fixed objective, a number of attempts, or a story milestone? | A limit can restrict your testing. It is useful to know whether you ran out of content or simply reached the demo boundary. |
| Saves and progression | Can you save freely? Does progress carry into the full game? Is transfer limited to the same platform, account, or edition? | Never assume demo progress transfers. Look for an explicit developer or store statement before treating the demo as a head start. |
| Difficulty and modes | Are difficulty options available? Can you change them during play? Does the demo show the mode you intend to use? | A fixed difficulty can make a game feel easier or harder than your eventual experience. |
| Performance | Are frame delivery, loading, image quality, and input response acceptable on your hardware? | Performance problems may be temporary, but they are still relevant evidence. Note whether an issue appears consistently or only in one area. |
| Controls | Does it recognize your controller? Can you remap buttons, adjust sensitivity, or use keyboard and mouse controls? | Comfortable controls can determine whether a promising game is enjoyable for long sessions. |
| Accessibility | Are subtitles readable? Can you adjust text size, contrast, motion, audio balance, aim assistance, or control inputs? | Features present in the demo are useful evidence, while missing options should be verified against the full game’s planned feature list. |
| Online requirements | Does the game require an internet connection, an account, voice chat, or other players? Is local play supported? | These requirements affect solo players, households with limited connectivity, and groups on different platforms. |
| Monetization | Are there paid items, a battle pass, optional expansions, or edition-specific content? Does the demo explain what is included? | Separate the quality of the playable sample from the total cost and structure of the finished product. For more context, see Battle Passes Explained. |
| Differences from the full release | Is the demo labeled as an old build, prologue, preview, or festival version? Are systems, maps, or features intentionally missing? | The more clearly the demo differs from the final product, the more cautiously you should generalize from it. |
If you are testing an indie narrative game
Pay attention to the quality of the writing, character motivation, dialogue pacing, world-building, and clarity of the central premise. A short demo may not reveal the whole plot, but it should show whether the tone and presentation suit your preferences. Check subtitle timing and readability as carefully as the story itself.
If you are testing an action, strategy, or platform game
Repeat the core activity rather than stopping after the first impressive moment. Test movement, attacks, camera behavior, enemy readability, menus, checkpoints, and failure recovery. Ask whether the basic loop remains satisfying after several repetitions. If the demo offers only one level, treat variety and long-term progression as unanswered questions rather than assumptions.
If you are testing a cooperative game
Check how players join, whether roles are explained, and whether the demo supports the platforms your group uses. Confirm cross-play and cross-progression separately; they are different features and may not be offered together. Our cross-play and cross-progression guide explains what to verify before coordinating a purchase.
If you are testing on a handheld or low-spec PC
Test the exact device and settings you expect to use. Note resolution options, text legibility, battery or heat behavior where relevant, loading times, and whether controls remain comfortable away from a desk. A general requirements list is not a substitute for testing your own hardware. See our low-spec PC performance guide for a broader checking method, or consult the Steam Deck compatibility guide when that handheld is part of your decision.
What to double-check
Save transfer: Search the game’s official store listing, demo notes, frequently asked questions, or developer announcements. Verify whether transfer works between the demo and full game, then confirm whether both versions must be on the same platform or account. If the answer is unclear, assume your demo save may not carry over.
Performance changes: A demo may use an older build or a different area of the game. Record specific symptoms instead of writing “it runs badly”: stuttering during combat, long shader compilation, delayed input, unstable resolution, or crashes after returning to a menu. Later patch notes may clarify whether a known issue was addressed. Our guide to reading game patch notes can help distinguish a meaningful fix from a minor change.
Full-game scope: Check what the demo does not show. You may not see later enemies, level structure, crafting, progression systems, endgame activities, online matchmaking, or the complete accessibility menu. Treat these as unknowns, not promises. If the game is in early access rather than a conventional pre-release demo, use a separate standard for roadmaps, updates, and refund risk; our early access buying guide covers those questions.
Store and edition details: Confirm which edition the demo relates to and what the standard purchase includes. Deluxe or premium editions can change the value calculation through bundled content, but a demo usually cannot demonstrate that content. Our game editions guide provides a useful comparison framework.
Common mistakes
- Judging the entire game from its tutorial: Tutorials are designed to teach, so their pacing and difficulty may not match later play.
- Confusing a content limit with a technical problem: A locked door, abrupt ending, or missing menu may be intentional. Check the demo description before treating it as a bug.
- Assuming silence means compatibility: Confirm controller layouts, operating-system support, handheld behavior, and online requirements rather than inferring them from a store badge.
- Ignoring comfort: Test text size, camera motion, audio balance, repeated inputs, and menu navigation. Small annoyances can become major barriers over a full campaign.
- Buying immediately after a strong first impression: Wait long enough to repeat the core loop and write down what remains uncertain. A good demo can justify further research without proving every part of the finished game.
- Using another player’s performance result as your own: Hardware, drivers, settings, and patches differ. Treat outside reports as clues and test your setup where possible.
When to revisit
Revisit this evaluation when the demo receives a substantial update, the full game launches, a platform version changes, or the developer publishes new information about saves, accessibility, performance, or multiplayer. Patch notes and revised store descriptions can resolve questions that were open during your first test.
You should also repeat the check when you change hardware. A game that felt comfortable on a desktop monitor may have unreadable text on a handheld, while a controller issue may disappear after moving to another platform. If you are planning purchases around a seasonal sale or release window, compare the current demo, current edition details, and current store terms rather than relying on an old impression.
For a practical final decision, use this three-step note:
- Buy now: The core loop works for you, your hardware performs acceptably, and the remaining unknowns are not deal-breakers.
- Watch and recheck: You like the concept, but progression, performance, save transfer, or full-game scope still needs confirmation.
- Skip: A fundamental issue—controls, accessibility, required online play, performance, or the core loop—does not fit your needs.
That process turns a demo into useful evidence instead of a sales moment. Keep the notes with your game wishlist, update them after major patches, and use the same criteria when exploring the next batch of indie games.