People asking me “how are games made” are usually really asking one of two things: either the creative pipeline (idea to shipped product) or the much blunter question underneath it — could I actually do this, and what would it cost me. The pipeline stuff is genuinely interesting, but the numbers are what actually matter if you’re weighing whether to start.
The blunt version first: the median indie game costs $30,000–$60,000 to make once you count your own time as opportunity cost, takes 1–3 years, and earns a median of $5,000–$15,000 gross over its lifetime. Only about the top 0.5% of releases clear $1 million. That’s not meant to scare anyone off — plenty of people make games for reasons other than profit — but going in blind to those numbers is how people end up bitter about a project that was never going to pay for itself financially, when it could have been a great creative project on realistic terms instead.
Pre-Production: Where Most of the Real Decisions Get Made
Before any real building starts, pre-production is where a team figures out what the game actually is — core mechanics, art direction, scope — and, critically, what it isn’t. This is also where most budget overruns get seeded, not caused: a vague or overly ambitious scope decided here is what turns a planned 18-month project into a 3-year one later, because nobody said no to a feature when saying no was still cheap. The teams that actually ship on time are usually the ones that cut hard in pre-production, not the ones that manage their time better during production.
Choosing an Engine Isn’t a Neutral Decision Anymore
This used to be a fairly simple choice; it isn’t anymore, and the data shows an actual shift happening in real time. For the first time, more developers now name Unreal Engine as their primary tool than Unity — 42% to 30% among developers with a stated primary engine — a genuine reversal from Unity’s long-standing lead. But that mindshare number hides an important split: Unity still powers the majority of actual Steam releases (51% versus Unreal’s 28%), while Unreal now leads on revenue per release (31% to Unity’s 26%), the first time that’s happened since 2018. Translation: more games get built in Unity, but the games built in Unreal are, on average, making more money per release — which says something about the type and ambition of projects each engine tends to attract right now, not that one engine is simply “better.”
If you’re on mobile specifically, that whole conversation is moot — Unity still powers roughly 48% of mobile development and sits inside an estimated 70% of top-grossing mobile titles, a dominance that hasn’t meaningfully shifted. And if you’re a solo or small-team developer put off by either giant, Godot is worth a genuine look: it’s grown from 25,000 starred GitHub projects in 2020 to over 100,000 in 2026, the fastest growth of any engine by developer adoption, particularly among indie developers in the UK, Germany, and Sweden. It’s free, open source, and has crossed the threshold from “hobbyist alternative” to a real third option.
Production: The Long, Unglamorous Middle
Production is where the actual building happens, and it’s also where the timeline math gets real: most indie games take one to three years to reach release, and that range mostly reflects scope decisions made back in pre-production, not how hard the team worked. A tightly scoped 2D game with a solo developer can land at the low end of that range and the low end of the cost range too — as little as $10,000 for a simple mobile title. A more ambitious multi-person project pushing toward $150,000+ in budget is playing a genuinely different, higher-risk game, closer to the mid-range indie budgets ($40,000–$150,000) that most funded indie projects actually fall into.
Testing and Launch: Where the Realistic Expectations Matter Most
QA and polish at the end of production is where a lot of that earlier scope creep gets paid for, in crunch or in cut features, and it’s worth budgeting real time for rather than treating it as a formality before launch. On the business side, going in with the actual lifetime-earnings numbers in mind — median gross revenue in the $5,000–$15,000 range for indie releases — changes what “success” reasonably looks like for a first project. Breaking even, building a portfolio, and learning the actual production pipeline end to end is a completely legitimate goal for a first game, and treating it that way going in tends to produce a much healthier relationship with the result than assuming you’re one hit away from quitting your job.
What This Actually Means If You Want to Make a Game
Scope down harder than feels comfortable in pre-production — almost every timeline and budget overrun traces back there. Pick an engine based on your actual project (mobile leans Unity, ambitious PC/console projects increasingly lean Unreal, solo/budget-conscious projects have a real option in Godot now) rather than habit or hype. And go in with realistic numbers on both timeline (1–3 years) and outcome (most games don’t make their budget back) so the project succeeds on the terms you actually set for it, not on terms the market rarely delivers.
This pairs well with our guide, Getting Into Game Journalism: The Industry Has Actually Changed.
FAQ
How long does it actually take to make an indie game?
Most take 1 to 3 years from start to release, with the range driven almost entirely by scope decisions made early in pre-production rather than team size or work ethic.
Which game engine should I choose in 2026?
Unity still dominates mobile development, Unreal has taken the lead in developer mindshare and revenue per release for ambitious PC/console projects, and Godot is the fastest-growing free option for solo or budget-conscious developers.
Can you actually make money making indie games?
It’s possible but statistically unlikely to be your primary income — median lifetime revenue for indie releases sits around $5,000–$15,000, and only about 0.5% of releases exceed $1 million.
1 thought on “How Games Are Actually Made: Real Budgets, Timelines, and Engine Data”