Finding worthwhile indie games is easier when discovery becomes a repeatable process rather than a scroll through random recommendations. This checklist shows how to find candidates, test them with demos or reliable evidence, estimate value, and decide whether to buy now, wishlist, wait for a patch, or skip.
Overview
Indie discovery works best as a funnel. Start broadly with storefront tags, festival showcases, demo roundups, curator lists, developer pages, and recommendations from players whose tastes match yours. Then narrow the list using practical questions: Does the core mechanic appeal to me? Is the expected playtime appropriate? Can I try a demo? Does the game appear technically ready? Is the price reasonable for the time and kind of experience I want?
The aim is not to predict whether a game is objectively “good.” A small puzzle game, a demanding roguelike, and a short narrative adventure offer different kinds of value. The aim is to reduce avoidable disappointment while leaving room for unusual ideas and personal taste.
Keep a discovery wishlist with three labels:
- Explore: The concept is interesting, but you need more information.
- Test: A demo, trial period, or hands-on opportunity is available.
- Buy or wait: You have enough information to make a purchase decision, but timing may depend on patches, sales, or your backlog.
If your list is already crowded, use the workflow in How to Organize Your Video Game Backlog and Choose What to Play Next to connect new discoveries to the games you already own.
How to estimate
Use a simple five-step estimate for every serious candidate. Record the answers in a notes app or spreadsheet so you can compare games without relying on memory.
- Define the appeal. Write one sentence explaining why the game caught your attention. Name the mechanic, setting, art direction, co-op feature, or storytelling approach—not just “it looks good.” If you cannot identify a specific appeal, keep the game in the Explore column.
- Check the primary loop. Look for gameplay footage that shows repeated play rather than only trailers. Ask what you will do most often: solve rooms, build a team, manage resources, fight, explore, make choices, or repeat short runs. The loop should match what you want to play now.
- Estimate the commitment. Separate the main path from optional content and replay value. A short game can be excellent value if you want a focused evening; a long game may be poor value if it competes with an unfinished backlog. For a more consistent estimate, use the categories in How Long Is This Game? A Practical Guide to Main Story, Side Content, and 100% Completion Times.
- Test risk before spending. Prefer a demo when one exists, but treat a demo as a sample rather than a guarantee. Check controls, readability, performance, save behavior, audio, and accessibility options. If there is no demo, look for unedited gameplay, recent player discussions, and the developer’s update history.
- Choose a decision. Mark the game as Buy, Wishlist, Wait for a patch, Wait for a sale, or Skip. A clear “not yet” is a useful result; it prevents an interesting game from becoming an impulse purchase.
You can turn the process into a lightweight score. Give each category a rating from 0 to 2: 0 means poor fit or unknown, 1 means mixed, and 2 means strong fit. Score concept, core mechanics, technical confidence, accessibility fit, expected playtime, developer communication, and price fit. A high total does not replace judgment, but a low score in a non-negotiable category—such as required accessibility features or controller support—should usually override the total.
Inputs and assumptions
A useful indie game evaluation checklist uses inputs that reflect your situation, not a universal ranking. Record these fields for each candidate:
| Criterion | What to check | Decision question |
|---|---|---|
| Art and presentation | Visual clarity, sound, interface, and whether the style supports the game | Do I enjoy looking at and listening to this for several hours? |
| Mechanics | The repeated actions, controls, difficulty, and learning curve | Would I still enjoy the core loop after the novelty fades? |
| Expected playtime | Main path, optional content, replayability, and session length | Does the commitment fit my available time? |
| Demo availability | Demo quality, save limits, performance, and how much of the loop it reveals | Can I test the risks that matter to me? |
| Developer track record | Previous releases, communication, updates, and clarity about known issues | Is there enough evidence to trust the current build? |
| Price fit | Current listed price, your budget, expected use, and likely opportunity cost | Would I be comfortable with this purchase if I only complete the main path? |
| Accessibility and performance | Text size, remapping, subtitles, difficulty options, frame pacing, loading, and crashes | Does it meet my personal requirements on my hardware? |
Do not use fixed price thresholds as if they apply to everyone. Instead, create personal bands such as “buy at listed price,” “buy during a sale,” and “only buy in a bundle.” Base them on your budget, expected playtime, and how urgently you want the experience. A two-hour game and a replayable game may deserve different standards even when they cost the same.
Also separate evidence from assumptions. “The demo ran smoothly on my system” is evidence. “The full game will definitely run smoothly” is an assumption. For technical questions, use the method in Game Performance Review Checklist: How to Test FPS, Stutter, Load Times, and Accessibility.
Worked examples
Example one: a short narrative game. The concept is highly appealing, the demo confirms the writing style and controls, and the main path appears compact. Optional content is limited, but that is not a problem because you want a focused experience. Your notes might read: concept 2, mechanics 1, presentation 2, demo confidence 2, accessibility 2, playtime fit 2, price fit 1. The result is “Buy if the current price fits the short format; otherwise wishlist.” The important point is that limited length was evaluated against your goal, not treated as an automatic weakness.
Example two: an early-access management game. The systems look promising, but the interface is unclear, performance is inconsistent, and the roadmap leaves important features uncertain. You may score the concept and replayability highly while giving technical confidence and completeness low scores. The appropriate decision is “Wait for a patch or a clearly documented milestone.” Revisit the evaluation after reading the update notes rather than buying solely on potential. The Patch Notes Explained workflow can help distinguish bug fixes from changes that materially improve the game.
Example three: a multiplayer indie game. The mechanics are attractive, but your decision depends on player availability, matchmaking, cross-play, and server stability. Check those requirements before judging the game’s value. If friends play on different systems, use Game Cross-Play and Cross-Progression Guide before purchasing. A game can be a strong solo recommendation yet a poor fit for your group if the necessary multiplayer features are missing.
For each example, save the reason behind the decision. “Wait because performance is uncertain” is more useful than a vague wishlist entry, and it tells you exactly what to check later.
When to recalculate
Re-run the checklist whenever an input changes. Recalculate after a demo is released, a major patch changes performance or systems, the listed price changes, a bundle alters the effective cost, or a developer clarifies the roadmap. Also revisit a game when your own situation changes: a new graphics card may remove a performance concern, while a busier schedule may make a long campaign less attractive.
Discovery sources change as well. Periodically review current storefront tags, festival pages, demo roundups, curator lists, and bundle collections rather than relying on an old article or saved social post. Treat recommendations as leads, then verify the current store page and available features before deciding.
For a practical monthly routine, choose five candidates from your Explore list, update their price and demo status, and test the highest-priority one if possible. Remove games that no longer fit your interests. Move only the strongest candidates into Buy or Wait for a sale. This keeps your wishlist useful instead of turning it into an unreviewed archive.
Finally, record what happened after each purchase: hours played, what worked, what did not, and whether the original estimate was accurate. Over time, this creates a personal discovery model. You will learn whether you usually prefer shorter polished games, experimental mechanics, replayable systems, or games with strong accessibility options. That history makes the next indie game spotlight easier to evaluate—and makes “Should I buy this indie game?” a question you can answer with evidence rather than impulse.
