An indie game demo can reveal far more than its playtime suggests—but only if you test the right things. This reusable checklist helps you judge controls, performance, accessibility, save behavior, content, and storefront details before moving a game from your wishlist to your cart.
Overview
A demo is useful evidence, not a guarantee. Some demos closely represent the opening hours of the finished game; others are festival builds, prototypes, or custom vertical slices designed to show a particular mechanic. The difference matters when you are deciding whether to buy an indie game at launch, wait for a discount, or keep it on your wishlist.
Start by identifying what kind of preview you are playing. Check the store page, developer notes, or demo description for clues about whether it is an early build, a standalone sample, or a section taken from the full release. Do not treat a short demo as a complete review of a long game. Instead, use it to answer practical questions: Does the core loop appeal to you? Are the controls comfortable? Does the game run acceptably on your hardware? Can you use the accessibility options you need?
The same game may offer a different demo experience on Steam, itch.io, or a console storefront. Availability, update timing, input support, and save behavior can vary by platform. If you are comparing places to buy, our guide to Steam, itch.io, Humble, and key stores provides broader storefront context.
Checklist by scenario
When you are testing the core gameplay
- Controls: Test movement, aiming, menus, camera behavior, and the actions you will perform most often. Notice whether inputs feel responsive and whether controller, keyboard, or mouse controls match the store description.
- First-minute clarity: Can you understand the immediate objective without repeatedly checking a guide? A tutorial does not need to explain everything, but it should establish the basic interaction loop.
- Core loop: Play long enough to repeat the main activity. For a roguelike, that might mean completing several rooms or a run segment. For a cozy game, look for the rhythm of gathering, building, conversation, or exploration. For horror, check whether tension comes from the intended design rather than confusion or poor visibility.
- Friction: Separate deliberate difficulty from avoidable inconvenience. Unclear objectives, awkward inventory navigation, or inconsistent hit detection can affect the full game more than a missing feature in a demo.
When you are checking technical fit
- Performance: Test a busy scene, not only the opening area. Watch for stutter, long loading, crashes, input delay, or visual problems. Compare what you experience with the listed system requirements, while remembering that a demo may not use the same build as the final game.
- Hardware: If you plan to play on a Steam Deck or low-spec PC, test resolution, frame-rate options, text readability, and battery or heat behavior where practical. Use our Steam Deck and low-spec compatibility guide as a companion checklist.
- Accessibility: Look for subtitle controls, text size, color options, remapping, difficulty adjustments, screen effects, aim assistance, and audio controls. Record what is present, absent, or difficult to find rather than assuming the full game will add it.
When you are deciding whether to buy now
- Content length: Note how long it took to reach the demo's endpoint, but do not multiply that time into a predicted full-game length. A demo can be deliberately paced, trimmed, or built from a special showcase section.
- Replay value: Ask whether you want to replay the available section because the systems are interesting, or only because you have not solved it yet. This is especially useful for roguelike, puzzle, strategy, and simulation games.
- Progress carryover: Check whether demo saves, unlocks, cosmetics, or achievements carry into the full release. Treat this as a storefront- or developer-specific detail, and verify it in current documentation before relying on it.
- Release condition: Read recent developer updates and the current store page for changes to the planned scope, platform list, or release status. A demo shows what exists in that build, not everything promised for launch.
Demo availability by storefront
| Storefront | What to check | Best use of the demo |
|---|---|---|
| Steam | Whether a separate demo is listed, the build's update date, system requirements, controller notes, and recent developer announcements. | Testing PC performance, input devices, and compatibility before wishlisting or buying. |
| itch.io | Download format, operating-system support, version notes, installation instructions, and whether the build is experimental or pay-what-you-want. | Exploring early prototypes, unusual formats, and developer-led previews while accepting that presentation may be less finalized. |
| Console stores | Whether the demo is available in your region and on your console, plus control options, save behavior, and any platform-specific version notes. | Checking couch play, controller comfort, readability from a distance, and performance on the actual console. |
Availability changes, so use the current listing rather than an old showcase page or social post. A missing demo does not necessarily indicate a problem, and a polished demo does not guarantee that every full-game feature is complete.
What to double-check
Before buying, write down the answers to five questions:
- Did I enjoy the repeated activity? A striking art style or promising premise cannot replace a core loop you want to revisit.
- Did the game behave well on my setup? Record your hardware, graphics settings, controller, and any issues so you can distinguish a configuration problem from a broader concern.
- Were the important options easy to find? Check the settings menu before leaving the demo. Missing remapping or subtitle controls may affect your purchase decision more than a short runtime.
- What exactly does this demo represent? Look for build dates, labels such as “prologue” or “festival demo,” and developer notes.
- Does the purchase fit my backlog? Add a short note to your wishlist instead of buying automatically. Our guide to building a practical indie game wishlist can help turn a promising demo into a considered plan.
Also confirm the purchase version, language support, multiplayer requirements, and whether the game is sold directly or through a key-based arrangement. For broader value checks, compare the demo result with our guides to cheap indie games worth buying and indie game deals and bundles.
Common mistakes
- Judging a full game by an unfinished interface: Note problems, but separate temporary presentation issues from flaws in the central design.
- Assuming demo length predicts value: A ten-minute preview can demonstrate a system effectively, while a longer demo may include content that will not appear in the final structure.
- Ignoring settings: A poor first impression may come from motion blur, audio balance, tiny text, or an unsuitable control layout. Check options before deciding.
- Confusing novelty with fit: An unusual mechanic can be worth trying without being a reason to buy immediately. Ask whether you want to spend several hours with it.
- Forgetting the demo's version: Save the date you played and any notable build number. A later update may address—or introduce—important changes.
- Buying every promising preview: Keep a tested-demo list and rank it by interest, hardware fit, and available playtime. This avoids turning discovery into another backlog.
When to revisit
Revisit this checklist before major seasonal sales, digital festivals, publisher showcases, and large wishlist purchases. It is also worth repeating when a demo receives a substantial update, the game moves from early access toward full release, the system requirements change, or a new platform version appears.
For an efficient refresh, open the current storefront page first. Check the demo's update date, version notes, screenshots, system requirements, accessibility information, and recent developer announcements. Then replay the parts that matter most to your original concern: a demanding scene for performance, a complete control sequence for input feel, or the settings menu for accessibility.
Finish with a simple decision: buy now, wishlist and wait, or remove from consideration. If you choose to wait, add a note explaining why—such as “retest after performance update” or “check save carryover at launch.” Pair that note with an organized wishlist-to-play plan so demos lead to deliberate purchases rather than an expanding queue.