Small developers track wishlists more closely than any other pre-launch figure. The reason is that a wishlist does two separate jobs, and the second one is worth more than the first.
A wishlist is a deferred purchase
A player who wishlists a game has decided they want it but not to buy it now, usually because it is unreleased or not discounted. The intent is recorded and stored.
When the game launches or goes on sale, the store notifies everyone holding it. That notification arrives without the developer spending anything.
Conversion is far from complete, since interest decays over months. But a meaningful share of a wishlist converts within days of launch, and that concentration matters more than the total.
Launch-day density feeds the algorithm
Storefronts promote games that are selling quickly right now. Sales in the first days are weighted heavily because the systems are designed to surface things while they are current.
Wishlists convert into exactly that shape: a cluster of purchases in a short window. The queued audience is what produces the spike.
The spike then earns algorithmic placement, which brings buyers who never wishlisted anything. This is the mechanism developers are actually chasing.
Where wishlists come from is not uniform
Wishlists collected from a viral video and wishlists collected from a demo behave differently. The first group often does not remember the game months later.
A player who spent twenty minutes in a demo has a stronger association and converts at a higher rate. Volume and quality diverge.
This is why experienced developers distrust a large number gathered quickly from a single source. The figure looks the same and performs differently.
Timing changes what a wishlist is worth
A wishlist added the week before launch converts strongly. One added two years earlier often belongs to a player whose tastes have moved on.
That creates a tension in marketing plans. Announcing early builds a larger number, but the number ages, and the ageing is invisible until launch day.
Teams increasingly respond by concentrating visibility close to release rather than sustaining it for years. The intent is to collect fresher interest even if the total is smaller.
The number is a forecast, not a promise
Developers use wishlist counts to estimate first-week sales, applying a conversion rate from comparable releases. The estimate is rough and can be wrong in both directions.
Price, genre, review reception and competing releases all shift the rate. A game launching alongside a major title converts worse regardless of its own quality.
So the figure guides decisions about print runs, marketing spend and staffing after launch. It is planning information rather than a measure of how good the game is.