A good indie game wishlist should do more than store attractive cover art. This guide shows you how to record the information that affects a purchase, estimate your real backlog capacity, compare storefront options, and review wishlist games each month so you know what to buy, play, postpone, or remove.
Overview
Wishlists become difficult to use when every saved game has the same status. A title you plan to play this weekend, a game you are waiting to see leave early access, and a curious demo you may never revisit should not compete for one undifferentiated queue.
The practical solution is to give each game a small set of decision-making fields. These fields turn a wishlist into a buying checklist and a backlog plan:
- Storefront and platform: Record where you can buy or play the game and whether that version suits your hardware.
- Price information: Note the current price, your target price, and whether a bundle or another storefront is worth considering.
- Time commitment: Estimate the likely playtime and compare it with the time you actually have available.
- Features and conditions: Track multiplayer needs, early-access status, accessibility requirements, and other deal-breakers.
- Confidence and intent: Write down why you saved the game and how much evidence you have that it is a good fit.
This approach is useful for Steam indie games, itch.io games, Humble selections, direct-store purchases, and other legitimate indie game stores. For a broader comparison of DRM-free options, see our guide to where to buy DRM-free indie games. The goal is not to calculate a perfect score. It is to make the next decision easier.
How to estimate
Start with two separate estimates: purchase value and backlog capacity. Keeping them separate prevents a low price from disguising the fact that you have no realistic time to play the game.
Estimate purchase value
Use this simple comparison:
Value ratio = target purchase price ÷ estimated hours you expect to enjoy
This is not a universal value judgment. A short narrative game may be worth buying for its mood, writing, or accessibility even if its hours-per-currency ratio is lower than a long roguelike. Use the ratio only to compare games that serve a similar purpose.
For each wishlist game, ask three questions:
- What price would feel comfortable without making the purchase impulsive?
- How many hours do I realistically expect to play, rather than the maximum advertised or reported duration?
- Would I still want this game if it did not go on sale soon?
Estimate backlog capacity
Calculate the number of games you can reasonably start during your planning period:
Available playtime = weekly gaming hours × number of weeks
Then reserve time for games already in progress. If you have 30 available hours over a month but expect an existing game to use 18 hours, your practical capacity for new games is about 12 hours. Do not treat that number as a target you must fill. Leaving some capacity for spontaneous discoveries makes the plan more sustainable.
For games with uncertain length, record a range such as 5–8 hours rather than pretending to know an exact total. For multiplayer games, estimate the time needed to coordinate with friends, not only the nominal campaign length.
Inputs and assumptions
Use the following reusable wishlist template for every serious candidate. A spreadsheet, notes app, database, or backlog tracker can work; consistency matters more than the tool.
| Field | What to record | Why it matters |
|---|---|---|
| Game and storefront | Title, Steam, itch.io, GOG, Humble, direct store, or another verified source | Prevents duplicate purchases and clarifies where updates, files, or keys may be managed. |
| Platform | PC, Steam Deck, console, or other supported device | Checks whether the game fits your actual setup. |
| Current price | Price and currency on the date checked | Creates a baseline for comparing a future discount. |
| Target price | The amount you would willingly pay | Turns vague waiting into a clear buy condition. |
| Estimated playtime | Short, typical, and extended estimates when available | Helps match the purchase to your schedule. |
| Multiplayer needs | Solo, local co-op, online co-op, player count, or friend availability | A multiplayer game may not be useful if the required group is unavailable. |
| Early-access status | Released, early access, demo, or announced; note your tolerance for unfinished features | Separates games you can enjoy now from games you would rather revisit later. |
| Review confidence | High, medium, or low, with a short reason | Distinguishes informed interest from a compelling trailer or recommendation. |
| Accessibility requirements | Text size, subtitles, remapping, color options, input support, difficulty controls, or other needs | Prevents a discount from leading to an unusable purchase. See our indie game accessibility guide for a fuller checklist. |
| Reason for saving | One specific sentence, such as its setting, co-op format, demo, or developer | Shows whether the original interest still exists when you review the list. |
| Decision and next review | Buy now, wait for target price, play demo, research, remove, and a review date | Gives every saved game a next action. |
Several assumptions need to remain visible. Storefront prices, regional taxes, bundle contents, platform support, and availability can change. A wishlist notification may indicate a change without proving that the current offer is the best available option. Price-tracking tools may have incomplete coverage, delayed data, or limits on regional and storefront comparisons, so verify the listing before buying.
Refund eligibility and time limits also vary by storefront and can change. Check the relevant store’s current rules before relying on a refund as part of your buying plan. A demo is often a better test of controls, performance, and accessibility when one is available; our guide to evaluating indie game demos can help you use that time well.
Worked examples
Example 1: A sale is not automatically a buy
Imagine a hypothetical game with a current price of 12 currency units, a target price of 10, and an estimated enjoyable playtime of 8–12 hours. You save it because of its pixel-art exploration and solo format. Your review confidence is medium because you have watched a trailer but not played a demo.
The decision is not simply buy or ignore. Because the current price is above your target and your confidence is medium, assign the next action play demo or read focused impressions. If the demo confirms that the controls and accessibility options work for you, raise the game to buy at the next suitable price. If the core loop feels repetitive, remove it without treating the research time as wasted.
Example 2: A multiplayer game needs a scheduling test
Suppose a hypothetical co-op game meets your target price and appears to offer 6–10 hours of content. You have two friends interested, but all three of you can play only once every few weeks. The price field says buy, but the multiplayer field says not yet.
Set a review date after confirming a shared play window. If that date does not work, move the game to a seasonal sale list rather than buying it for an imagined future session. This prevents a cheap co-op purchase from becoming inactive backlog weight.
Example 3: Early access changes the timing decision
For a hypothetical early-access roguelike, record the current build status, the features you consider essential, your tolerance for resets or balance changes, and the reason you are interested. If you want a finished narrative experience, the correct action may be wait and review later. If you enjoy following development and the current build already meets your expectations, the game may belong in a small active-play queue.
Use the same discipline with bundles. Calculate the value of the games you genuinely expect to play, not the advertised total of every included item. Our guide to finding useful indie game bundles covers that decision in more detail.
When to recalculate
Review the wishlist once a month and perform a shorter check before major sales. A monthly review is long enough for priorities to change but short enough to prevent the list from becoming an archive of forgotten recommendations.
- Capture changes: Update current prices, storefront availability, platform support, early-access status, and any relevant demo or accessibility information.
- Remove expired reasons: Delete games saved only because they were featured, discounted, or recommended by someone whose preferences no longer match yours.
- Check capacity: Count unfinished games and compare their expected hours with your available playtime for the next month.
- Apply decisions: Move games into four practical groups: buy now, wait for target price, research or demo, and remove.
- Set a purchase limit: Choose a number of new games or a spending amount that fits your real play capacity. Do not use a sale deadline as a reason to abandon that limit.
- Revisit after finishing a game: Completing a title changes your available time and may clarify which genres or lengths you currently want.
Recalculate whenever pricing inputs change, such as a seasonal promotion, bundle, regional price adjustment, or storefront move. Also recalculate after a hardware change, a shift in accessibility needs, the end of a multiplayer group’s availability, or a change in your tolerance for early access. For a broader timing reference, consult the indie game sale calendar, then verify the live offer on the storefront.
A useful wishlist is deliberately smaller than every game you might someday enjoy. Record the evidence behind each entry, give it a target action, and remove it when the reason no longer holds. That turns browsing for indie game deals into a repeatable buying process rather than another source of backlog.