What wishlist count justifies delaying a Steam launch?

There's no fixed number. What matters is how far below your tier minimum you sit and whether growth is still climbing or flat. A studio at 80% of its tier minimum with strong growth is a weaker case for delay than one at 40% and flat, even if the two studios are targeting the same tier.

Is it better to delay or launch with a weak wishlist count?

It depends on whether the delay has a specific plan attached. A delay used for a concrete action (a Next Fest slot, a tested creative change) can close a real gap. A delay used only to "keep marketing longer" with no new plan usually arrives at close to the same numbers, later.

Does delaying a Steam launch hurt an existing wishlist base?

It can, if the base isn't actively nurtured through the delay. Wishlists can go cold without fresh content or communication, eroding exactly the readiness the delay was meant to protect.

How many times can you delay a Steam launch before it hurts you?

There's no hard limit, but each delay without a new, specific reason reads worse to the same audience the date was meant to motivate. One well-explained delay with a clear plan is very different from repeated delays with no new lever each time.

Should you delay your Steam launch?

The four questions that actually decide it

How far below your tier minimum is your count, not just whether it's below? Say you're targeting the $250K-$999K tier: how many wishlists do you need on Steam puts that tier's minimum at 30,000. A studio sitting at 24,000 (80% of the way there) with count still climbing each week is in a very different spot than one sitting at 12,000 (40% of the way there) with growth flat. The first is close enough that a few more weeks of normal growth likely closes the gap; the second would need months of accelerated growth that a short delay doesn't actually produce.

Is your conversion rate broken, or just not measurable yet? If you already have enough sales data (from a demo or early access) to calculate a real conversion rate, and it's confirmed below benchmark, that's a specific, fixable problem worth delaying for. If you simply don't have enough data yet to calculate a rate at all, that's a different situation, delaying because a number is unmeasured isn't the same as delaying because it's confirmed weak.

Does the extra time have a specific plan attached, or is it just "more marketing"? "A few more months of marketing" is not a plan you can point to. "A Next Fest slot we couldn't otherwise fit in, plus the trailer cut that already tested better with our audience" is a plan. A delay without a specific action to take rarely closes the gap that caused it, the same generic marketing that got you to 12,000 wishlists usually just gets you to a slightly higher number on the new date.

What does the delay cost beyond the calendar?Team runway (how many more months of paying salaries this buys you), an existing wishlist base that can go quiet while waiting, and any external commitments (a funding milestone, a publisher deadline) all have a real cost. A studio with two months of runway left can't afford a six-month delay no matter how far below its tier minimum it sits.

Worked example: two studios, two different calls

Studio A:targeting the $250K-$999K tier (30,000 minimum), sitting at 24,000 wishlists and gaining 200 a day, conversion rate not yet measurable (no demo run yet), six months of runway left, no specific new lever identified for extra time. Call: launch on schedule. At the current growth rate, 24,000 becomes roughly 27,000-28,000 by the original date, close enough to the tier minimum that a delay's uncertain upside doesn't clearly beat the certain cost of burning more runway.

Studio B:same tier and minimum, sitting at 12,000 wishlists with flat growth, a demo already run showing a conversion rate of 6% against a 10-15% benchmark, and a specific plan (a re-cut trailer that tested better, plus a Next Fest slot they hadn't yet used). Call: delay. Both problems are confirmed, not guessed at, and there's a specific plan attached, not just "more time."

Red flags to watch for

Delaying a second time with the same plan as the first. If the plan didn't close the gap once, running it again for longer rarely works better.
Treating the delay as a pause rather than a plan. The extra time only helps if something specific happens during it. Otherwise the same gap is still there on the new date.
Letting an existing wishlist base go quiet during a long delay. Wishlists can go cold without active content or communication, eroding the very count that justified waiting.
Delaying over one weak number when the other is strong. A studio at its tier minimum on wishlist count with a conversion rate that simply hasn't been measured yet is often better served launching and reading the real number, rather than delaying over a number that doesn't exist yet.

Sources: Public Steam revenue-tier and visibility-floor benchmark data, as compiled in how-many-steam-wishlists-before-launch; Steamworks Next Fest and discovery documentation.