How Much Does It Cost to Make a 2D Indie Game?

A solo developer can start a 2D game at $0, and the only unavoidable cash line between a finished build and a Steam launch is the $100 Steam Direct fee. Every other line in the budget is a choice. The engines people actually finish games in have free cores, complete art libraries ship under licenses that allow selling, audio catalogs are free, and the software that cuts a store trailer costs nothing at the tier a first game needs. The comfortable middle, where most working solo developers live, runs roughly $10 to $30 a month, spent on one or two specific limits rather than on a stack of habits. This article prices the whole stack line by line, including the lines that never appear on a receipt. One disclosure first: this blog belongs to Egmatic, a no-code 2D editor in pre-alpha, and what that has to do with your budget is near the end.

A scope note before the numbers. This is the cost of making and shipping the game itself on the PC route, Steam and itch.io, because that is where 2D indie games overwhelmingly launch first. What you charge for the finished game is a different question with its own article, our pricing walkthrough; the two budgets meet only at the store fee.

Quick answer#

The $0 start is real, not a marketing claim#

The free stack is complete enough that it stops being a claim and becomes a map. Godot's engine is free under MIT, and so is GDevelop's editor. Construct's free tier caps projects at 50 events, which is small but finishable, and GameMaker's free tier is licensed for non-commercial use. For art, Kenney publishes an entire coherent catalog under CC0, itch.io listed 53,641 free game asset packs in late August 2026, and OpenGameArt lets you filter every submission by license. Audio has the same shape, with free catalogs covering a first release end to end. The trailer needs OBS Studio to record, DaVinci Resolve's free build to edit, and CapCut's standard tier to trim cutdowns; all three are free at exactly the tier a store page requires.

Two developers from the customer interviews we run bracket this whole market. One entered game development at literally zero cost and has shipped nothing yet but owes nothing either. The other pays over $100 a month for engine and assets and keeps asking for a pay-once option instead. Both are being rational about their own situations, and the budget between them is the honest subject of this article: the floor is real, the middle is small, and the difference between the two developers is mostly what they are trying to finish, not what anything costs.

The $0 stack has one real price, and it is discipline. Free art from mixed sources shows its seams through mismatched outlines, palettes and grid sizes, so the free route spends attention where the paid route spends money. Our map of free asset libraries with per-library licenses is the practical answer to keeping that price low.

What the engines cost, and what the money buys#

The engine line is where the subscription-versus-pay-once argument lives, and the current prices are worth having in one place.

Two patterns are worth more than the table itself. First, every free tier in that list is finishable: a complete, sellable game fits inside Godot or GDevelop without paying anyone, and Construct's 50-event cap is the only limit in the list a project outgrows simply by getting bigger; the others gate selling or publishing rather than building. Second, the paid tiers sell edges, not capability. Construct's year buys unlimited events and native builds; GameMaker's one-time fee converts a hobby license into a commercial one; GDevelop's cloud tiers lift publishing quotas and remove a watermark. The detailed splits live in our Construct 3 pricing guide and GameMaker pricing guide.

The honest advice from the interviews is the same advice the table suggests: buy the limit you have actually hit. A developer paying annually for tools while the game is still an idea is renting a gym membership in January. The pay-once preference our $100-a-month interviewee keeps expressing is a preference for edges that stop charging when you stop using them, and GameMaker's one-time commercial license is the closest match in the current market.

Art: free covers a whole game, and buying is about consistency#

The art budget divides into three very different questions that pricing discussions usually blur together.

The first question is existence, and its answer is $0. A complete 2D game can be built this year entirely from Kenney packs, OpenGameArt submissions and the free sections of itch.io, all under licenses that allow selling the result. The catch is legal rather than financial: the license line next to the download button decides what you may ship, and it decides it per asset, not per library. A single CC BY-NC sprite quietly bars a paid release, and share-alike licenses can conflict with a closed commercial project, so the free route keeps a credits file with the asset name, source, license and download date.

The second question is consistency, and this is where small money helps. Free packs from different authors argue with each other on screen, through outline weight, palette and grid size, and the mechanical fixes, one resolution, one shared palette, complete ecosystems from a single creator, cost attention instead of cash. Paying for a pack from the artist whose free set you already use is the cheapest way to buy coherence, and it is pocket-money spending, not budget-line spending.

The third question is originality, meaning commissioned art, and it belongs to a different scale of decision. Commissioning is priced per asset or per pack by the artist, takes art direction you may not have practiced yet, and makes sense when a project has proven it will be finished. A first game rarely needs this question answered at all, and treating it as the default art budget is one of the reliable ways to spend money before earning any.

One habit keeps all three questions cheap: test the game before the art exists. Gray-box playtesting, running the mechanics on placeholders, is a discipline with its own guide, and it prevents the most expensive art mistake, which is paying to polish mechanics that were going to be cut.

Audio is the cheapest line to zero#

Audio deserves its own line in the budget only because people expect it to cost something. Free music and sound effect catalogs cover a first release, licensed for commercial use, and the workflow discipline is the same as for sprites: check the license per track, record it in the credits file, and move on. The zero-budget sound design guide maps the catalogs and the licensing rules in full. If a first game spends audio money anywhere, it is usually one commissioned main theme, and that purchase waits until the game it opens for is worth opening.

The services around the game#

Saves, accounts, leaderboards and analytics used to be the moment a hobby project met a credit card, and the current answer is gentler. Backend-as-a-service free tiers are generous at the scale of a first game: Firebase's Firestore free tier holds a gigabyte of data and 50,000 document reads a day, and Supabase's free tier carries 500 MB of database with 50,000 monthly active users. Most shipped first games never leave those numbers.

The trap in this line is not the price, it is the shape of the price. A service that charges per call quietly converts your most enthusiastic players into a bill, and the lesson a veteran backend developer offered in one of our community reads was blunt: never pay per call for what you can batch. Whether your game needs a backend at all is a question with its own article, and the short version is that more games than you expect run fine on files and free tiers.

Playtesting sits in this line too, and its free channels are strong enough that paying should feel like a scalpel. Steam Playtest costs nothing and recruits from your own store page, the testing subreddits run unpaid flairs as their standard route, and your own community supplies the testers most likely to return for a second round. The paid option earns its keep when you need strangers on a schedule or an audience slice you cannot reach otherwise, and developers who pay report budgeting $20 to $60 per session. The recruiting guide prices both routes honestly.

The one fee nobody skips: the store#

The Steam line is fixed and public. Steam Direct charges $100 per game, paid when you sign the agreement, and the fee is recoupable: Valve returns it once the game has earned $1,000 in adjusted gross revenue. The store then takes 30 percent of each sale, stepping down to 25 percent and 20 percent above $10 million and $50 million, tiers a first game will not meet. The full route, from signing through store page lead time to review, runs about four to six weeks, and our publishing walkthrough covers every step.

itch.io is the other store, and its pricing is deliberately flexible. Publishing costs nothing, every price on the platform is a minimum with pay-what-you-want above it, and the cut itch itself takes is chosen by the developer under open revenue sharing, anywhere from 0 to 100 percent with a 10 percent default. The one number worth knowing in advance is the payment processor's fixed fee, $0.30 plus 2.9 percent per transaction, which is why the platform itself recommends pricing at $2 or more: below that line the processor takes a share that no small seller survives. What the store takes out of each sale, and how the revenue models compare, is the business side our monetization walkthrough covers.

Mobile stores add their own developer registration fees, and this article deliberately does not price them: the PC route is where the 2D indie economics start, and porting is a decision that waits for revenue.

The budget line nobody prices: time#

Every cash line above has a free tier, and that fact sharpens rather than softens the largest cost. A first 2D game consumes months of evenings, and no purchase shortens that. What money can do is move months between categories: paid art saves drawing time, a paid engine tier saves export fights, a playtesting panel saves recruiting time. What it cannot do is replace the two things a first game actually runs on, which are finishing and iterating, and both of those are scope decisions.

This is also why the free stack is a better first budget than it looks. A developer who starts at $0 has no subscription guilt ticking in the background, no sense that every unfinished month costs money, and the correct response to that freedom is a scope small enough to finish. The discipline of finishing a first game, one mechanic, one screen, is worth more to the budget than any line in the tables above, because the most expensive 2D game is the one that never ships.

Where the money leaks#

• Subscriptions before a finishable scope. The Construct year ticks whether you build or not, and the annual price is only a deal for someone already shipping. Buy edges you have hit.
• Paid playtesting before the build is readable. At $20 to $60 a session, a panel watching a build nobody can parse buys you confusion at an hourly rate. Placeholder art playtesting first, payment second.
• Per-call pricing for batchable work. The backend veteran's rule cuts both ways: a service that bills per request turns players into costs, and batching or files often remove the bill entirely.
• One non-commercial asset in a paid game. The license line outranks the price line every time, and a single CC BY-NC sprite discovered late forces re-art, which is the most expensive kind of art.
• Packs bought for games you are not making. Sale-priced asset packs are seductive and cumulative, and a library of unused tiles is a museum, not a budget.
• Buying originality before consistency. Commissioned art on top of mismatched foundations still looks mismatched, at a hundred times the price of a shared palette.

How Egmatic fits#

Reading the stack this way shows where the real money goes: not into engines, but into the months of glue between a working game and a shipped one. Exporting, re-uploading to each store, wiring saves, accounts, leaderboards and analytics by hand, and then doing all of it again for every update. That loop is what Egmatic is being built around: a no-code 2D editor whose ship layer carries a scene to a released game, so the demo, the update and the web build are movements of one tool rather than three projects. The AI in the editor executes under your direction and every file stays yours. We are pre-alpha, we do not announce dates, and our pricing does not exist yet in any form worth quoting. The waitlist at egmatic.com is where the shape of that answer is being argued out, and requests arriving during pre-alpha are the ones that steer it.

Cut the line that costs you months.

The expensive part of a first game is the shipping loop around it. Egmatic is a no-code 2D editor with a ship layer that treats the demo, the update and the web build as one movement. Reply on the waitlist with the cost line that surprised you most; requests sent during pre-alpha are the ones that steer the build.

you@example.comGet Build News

No spam. Unsubscribe anytime.

Conclusion#

The cash floor for a solo 2D game is one fee: $100 to Steam, returned after the first $1,000, or nothing at all on itch.io. The comfortable stack is a $10 to $30 month, and only when a specific limit has been hit. Art, audio, trailers, playtesting and backend services all start free at exactly the tier a first game needs, and the discipline that keeps them free is consistency, licensing care and scope small enough to finish. The largest line in the budget is months of evenings, and it is also the only line that pays anything back. Budget the $100, protect the evenings, and let the first game's receipts teach you which edges are worth renting.

Sources#

1. Valve — Steam Direct documentation ($100 fee per product, recoupable at $1,000 adjusted gross revenue; the 30, 25 and 20 percent revenue tiers; the signup-to-launch timeline, cross-checked in our publishing walkthrough)
2. itch.io — Pricing and Payments, creator documentation (pay-what-you-want above the minimum; open revenue sharing from 0 to 100 percent, 10 percent default; the $0.30 plus 2.9 percent processor fee; the recommendation to sell at $2 or more)
3. GDevelop — gdevelop.io (MIT-licensed engine, free editor; cloud tiers Silver at €4.99 and Gold at €9.99 a month covering publishing quotas, iOS builds and watermark removal; verified August 2026)
4. Scirra — Construct 3 pricing (free tier capped at 50 events with web export; Individual at $129.99 a year; Business at $468.99 a seat a year; verified August 2026)
5. GameMaker — pricing (free tier for non-commercial use; the one-time commercial license at $99.99; verified August 2026)
6. Unity — pricing (Personal tier free up to $200,000 in revenue and funding; Pro at $2,310 a seat a year; verified 2026)
7. itch.io — free game assets browse (53,641 free game asset packs listed, late August 2026) and Kenney — kenney.nl (whole catalog under CC0)
8. Firebase — Firestore pricing and Supabase — pricing (free tiers: 1 GiB of stored data and 50,000 document reads a day; 500 MB of database and 50,000 monthly active users)
9. Egmatic customer interviews, September 2026 (two waitlist respondents: one $0-cost entry; one paying over $100 a month for engine and assets, expressing a pay-once preference) — first-party reads
10. Community reads, r/playtesters and r/gamedev threads, August and September 2026 (paid playtest sessions budgeted at $20 to $60; the backend developer's batching rule from a ten-year PHP backend running on €10 to €50 a month) — community reads, not platform statements