How Much Money Do Indie Games Actually Make?

The median Steam indie game earns very little — commonly cited analyses put typical lifetime revenue in the low thousands of dollars, while the top few percent earn most of the money. The spread is the lesson: plan finances around the median, build skills and audience across multiple releases, and treat outlier stories as survivorship bias. That's the short version — the sections below get into the how, the why, and the mistakes worth dodging.

The distribution, not the average

Indie revenue follows a power law: a small fraction of releases capture most of the revenue, the middle does modestly, and a long tail earns near nothing. Averages mislead because hits drag them up; medians tell the truth, and the median is humbling. Any plan that requires beating the median to pay rent is a lottery ticket with extra steps.

Within the gloom, the patterns are consistent: games with clear genre appeal, real wishlist campaigns, and demo-driven validation cluster well above median. The floor isn't random.

What separates the middle from the tail

Post-mortems repeat the same factors: a hook visible in one screenshot, a niche with proven buyers, six-plus months of store presence before launch, festival demos, and launch-week stability. None guarantee a hit; their absence reliably predicts the tail.

Notice what's missing from the list: engine choice, code quality, team size. Players buy the fantasy and the polish they can see. The craft matters insofar as it ships those.

Plan like a portfolio, not a jackpot

Sustainable indies treat each game as one draw from a distribution they're improving: every release builds audience, skills, and systems that raise the next draw's floor. First games are tuition; budgeting them as retirement plans breaks people.

Practical corollaries: keep scope small enough to survive a median outcome, keep the day job longer than pride prefers, and bank the audience (mailing list, Discord, wishlists on the next game) — it's the one asset that transfers fully between projects.

Protect the downside first

Indie game revenue is lumpy and unpredictable, and most advice quietly assumes a hit. Plan for the median outcome instead: a launch that earns modestly and grows slowly. Keep fixed costs low, keep some runway, and make deals you could live with if the game sells a tenth of your hopes.

None of this is pessimism — it's what lets you take real creative risks. A developer who can afford to miss is a developer who can afford to be interesting.

Get unglamorous things in writing

Splits, deadlines, deliverables, who owns what if the project dies — the awkward conversations are dramatically cheaper before money shows up. A one-page agreement between friends feels like overkill right up until it's the only thing that saves the friendship.

You rarely need a lawyer for a first project, but you do need clarity. Write down what was agreed, date it, and make sure everyone has a copy. Future-you will be grateful.

The quiet work that protects all of this

Everything in this post gets undone by an unstable build. A great store page, a clever marketing beat, a perfect jam entry — none of it survives 'crashed twice, refunded'. Stability isn't a feature players praise, but it's the floor everything else stands on.

Give yourself visibility before you need it: crash reports with stack traces, a simple way for players to flag issues from inside the game, and a habit of fixing the top recurring error before adding anything new.

Putting it to work

Don't try to act on all of this at once. Pick the one change that costs you the least and pays the most this week, do it, and see what actually happens before reaching for the next.

Most of this rewards steadiness over intensity. A small improvement made every week, checked against how real players respond, outruns any single burst of effort — in this corner of game development and every other one.

Make the guesses cheap, the agreements written, and the runway longer than the plan.