Quick answer: Commissioned indie game music commonly runs from around $50 to several hundred dollars per finished minute depending on the composer's experience, production complexity, and rights granted — a small soundtrack often lands in the low thousands. Library licensing costs from free to tens of dollars per track, trading uniqueness for budget.

Commissioned indie game music commonly runs from around $50 to several hundred dollars per finished minute depending on the composer's experience, production complexity, and rights granted — a small soundtrack often lands in the low thousands. Library licensing costs from free to tens of dollars per track, trading uniqueness for budget. That's the short version — the sections below get into the how, the why, and the mistakes worth dodging.

What the per-minute number includes

Quotes anchor to finished minutes of music, but you're really buying everything around them: composition, production and mixing quality, instrument and sample costs, revision rounds, loop-ready editing, and the rights package. A $300/minute quote with full game-and-OST rights and two revision rounds can be cheaper in practice than $100/minute with none of that defined.

Orchestral and live-recorded work costs multiples of solo synth production. Genre expectations matter — a chiptune platformer and a cinematic RPG have very different floors.

Budget shapes that work for indies

Common smallest-viable approach: commission one signature main theme, then fill with carefully chosen library tracks until revenue justifies more — players remember the theme. Mid-range: 8-15 minutes of commissioned music with loops and variations stretched via layering. Reduced-fee-plus-royalty hybrids stretch budgets further when composers believe in the project.

Whatever the shape, define deliverables in writing: track list, lengths, loop points, stems or not, file formats, and revision counts. Scope ambiguity is where music budgets explode.

Where money is wasted, and where it isn't

Wasted: paying for length over quality (twenty mediocre minutes lose to eight great ones with smart reuse), full orchestration for a game whose aesthetic doesn't need it, and rushed end-of-project commissions where the composer never played the build.

Well spent: the main theme, the music players hear most (combat loop, hub theme), and the composer's time actually playing your game. Music written to the real pacing of real gameplay fits in ways spec-sheet music never does.

Audio bugs hide better than visual ones

A missing texture is obvious in any screenshot. A sound that silently fails to load, an audio device that disconnects mid-session, or music that stops looping after an hour only shows up in real play sessions — and players almost never file a report that says 'the music stopped'. They just feel the game got worse.

It's worth capturing errors and logs from real sessions for exactly this class of bug. The problems players can't articulate are the ones your tooling has to catch for you.

Audio is half the feel of your game

Players rarely praise game audio directly — they say the game feels 'satisfying' or 'atmospheric' and can't tell you why. Sound is doing that work. A well-timed impact sound makes a weak animation feel strong; a thin one makes a great animation feel hollow.

That's why audio repays attention even on a tiny budget. You don't need an orchestra; you need the handful of sounds players hear hundreds of times — jump, hit, click, collect — to feel exactly right.

Close the loop with real players

Advice gets you to a sensible starting point; only real player behavior tells you if it worked. Ship the change, then watch what actually happens — the reports that come in, the errors that spike or vanish, the place sessions end.

Make that loop short. When a player can report a bug in ten seconds and you see it with logs attached, you stop guessing what to fix next. Tight feedback loops are the closest thing indie development has to a cheat code.

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.

Get the five sounds players hear most to feel perfect before touching anything else.