Business · July 6, 2026
Itch.io vs Steam for an Indie Shmup: Distribution Tradeoffs Small Teams Actually Face
Picking a storefront gets treated as a marketing footnote when it is actually a structural decision, one that shapes how builds get patched, how reviews accumulate, and how much of the sale price the developer actually keeps.
Published July 6, 2026
A lot of advice on selling an indie shmup focuses on wishlist counts and trailer cuts, which matter, but the choice of storefront underneath all of that changes the mechanics of a launch in ways that are easy to underestimate until the first patch needs to go out under real player load. Itch.io and Steam are not simply two places selling the same file; they impose different constraints on revenue split, discovery mechanics, and build management that a small team should weigh deliberately rather than defaulting to whichever platform is more familiar.
Revenue split and payout mechanics
Itch.io defaults to a suggested revenue split that the creator can adjust, including down to zero, which is unusual generosity by industry standards and makes it attractive for a first release with no marketing spend to recoup. Steam's cut is fixed regardless of the developer's preference, structured in tiers that reduce slightly at very high revenue volumes that most first shmups will never reach. For a small team, the practical difference shows up less in the percentage itself and more in payout thresholds and schedules — itch pays out through third-party processors on a rolling basis, while Steam consolidates payouts monthly with its own minimum thresholds, which affects cash flow planning more than most first-time developers expect going in.
Discoverability is not the same kind of problem on each
Steam's discovery surface runs almost entirely on its recommendation algorithm and wishlist mechanics, which reward a strong pre-launch wishlist count built through visibility events and a well-timed announcement, tying directly back to the groundwork covered in marketing an indie shmup on no budget. Itch's discovery is comparatively manual and community-driven — browsing, tags, and direct links shared in Discord servers or forums do more work than any built-in algorithm, since itch's own front-page curation is thinner and less automated. Neither is inherently easier; they reward different kinds of pre-launch effort, and a team with an active Discord community but no marketing budget for wishlist-driving ads may find itch's model a better match for the effort they can realistically sustain.
Build management differs more than it looks
Steam's back end supports branches — separate build channels for a public release, a beta, and an internal testing track, each independently updatable — which is genuinely useful for the kind of staged, hotfix-then-verify patch cadence described in post-launch patch planning. Itch has no equivalent branch system in the same sense; every uploaded build effectively becomes the current version for whoever downloads it next, with channel tagging available but nothing as structured as Steam's beta-opt-in flow. A team planning frequent post-launch patches, hotfixes, and a public beta channel for testing changes before wide release will find Steam's tooling does more of that work automatically, while an itch-only release needs a manual process, often just a pinned devlog post, to communicate which build is which.
Refunds, reviews, and platform reputation effects
Steam's refund policy is generous and automatic within its window, which is good for player trust generally but means a shmup with a rough, unclear difficulty curve in its opening minutes can accumulate refunds specifically from players who bounce off a spike before adjusting to the game, a risk worth weighing against the onboarding and pacing decisions covered elsewhere in this devlog. Itch has no comparable formal refund system; most creators handle refund requests manually and inconsistently, which cuts both ways — less structural risk from an early difficulty spike, but also less of the trust signal that a formal refund policy provides to a hesitant buyer.
Running both is normal, not an either-or
Most small teams that release on Steam also maintain an itch page, often as a lower-friction landing spot for a demo build, a soundtrack bundle, or a version sold at a different price point without going through Steam's pricing constraints described in Steamworks' own pricing documentation. The decision is rarely which one to pick exclusively; it is which one carries the primary launch and which one plays a supporting role, and that split is worth deciding early rather than improvising it after a launch date is already public.