A client asks for “all the audio” for a small game. You estimate a few days of sound design, send a number that feels competitive, and then discover that “all the audio” also means alternate weapon versions, engine implementation, a late change to the combat system, extra export formats, and several rounds of feedback from people who were not in the original briefing. The problem was not simply that the quote was too low. It was that the quote never defined what the client was buying.
Pricing freelance game audio is part production estimate and part scope design. A useful rate has to pay for the audible work, but also for the less visible hours spent reading briefs, organizing sessions, naming and exporting files, integrating assets, handling feedback, and keeping the project moving. The numbers below are worked examples in US dollars, not universal market rates; adjust them to your location, experience, client type, and actual costs.
Start with the job, not a number you saw online
“Game audio” can describe several different services, and each has a different cost driver. A quote for 20 custom interface sounds is not directly comparable with a quote for 20 minutes of adaptive music or a Wwise implementation pass.
- Sound effects: price by a defined asset list or package. Complexity depends on the number of distinct sounds, variations, layers, loops, and delivery formats—not only the final file count.
- Music composition: price per finished minute, per cue, or by project when the number of cues and the interactive requirements are clear. Layered or adaptive music needs its own scope because stems, transitions, and state logic add work beyond writing a linear track.
- Implementation: estimate separately when you are wiring events into Unity, Unreal, FMOD, or Wwise, building parameters and states, tuning the mix, or testing in the client’s build.
- Dialogue editing or voice production: specify whether the work includes casting, recording, direction, cleanup, file splitting, naming, pickups, and integration. Editing supplied recordings is not the same service as producing the recording session.
This separation matters even when you sell one bundled package. A client may reasonably assume that “sound design” includes implementation, while you may mean delivered WAV files only. State the boundary before discussing the total. For more on how these production stages differ, the guide to selling game sound effects online covers the product-library side of audio work; custom freelance commissions need a more specific scope and approval process.
Calculate a sustainable hourly floor
An hourly rate is a useful internal planning tool even if you ultimately quote a fixed project fee. First estimate the annual amount your business needs to earn, then divide it by the number of hours you can realistically bill to clients. Do not divide by every hour you expect to work: proposals, accounting, marketing, learning, administration, and gaps between projects are real work but are not always billable.
For example, suppose your target is $60,000 a year before personal income tax, and your estimated annual business costs are $6,000. If you expect to bill 1,000 hours a year, the basic calculation is:
($60,000 target + $6,000 business costs) ÷ 1,000 billable hours = $66 per billable hour
That $66 is a planning floor under those assumptions, not a recommended rate for every freelancer. It does not automatically account for income tax, retirement contributions, unpaid invoices, equipment replacement, or a contingency reserve. Add the costs that apply in your country and business structure, and check whether your billable-hour estimate is realistic. If you can bill only 700 hours, the same $66,000 target and cost base implies about $94.29 per billable hour before those additional adjustments.
Review the calculation at least when your workload, tools, or client mix changes. A rate that works for a long-term studio contract with predictable weekly hours may not work for short jobs that require repeated onboarding and proposal writing.
Which pricing model fits the assignment?
| Model | Works well when | Watch out for |
|---|---|---|
| Hourly or daily | The brief is uncertain, the client expects ongoing support, or implementation involves investigation. | The client needs a budget ceiling; agree on an estimate, approval point, and reporting cadence. |
| Per asset or cue | The deliverables are countable and each item has a clear definition. | “One sound” can mean one file or a family of variations; define what counts as an asset. |
| Fixed project fee | The deliverables, review rounds, deadlines, and rights are stable enough to estimate. | Unpriced changes can erase the margin. List exclusions and a change-request process. |
| Retainer | A studio needs recurring access to a predictable amount of audio support. | Set the included hours or deliverables, response times, rollover rules, and overage rate. |
These models can be combined. You might charge a fixed fee for a defined set of sound effects, then bill implementation and additional requests hourly. Or quote a milestone-based project fee with a separate rate for work that falls outside the brief. The point is not to choose one pricing method for your whole career; it is to match the method to how uncertainty enters each job.
Build a quote from the actual production steps
Consider a hypothetical commission for 24 bespoke sound effects for a small action game. Your estimate might look like this:
| Work item | Estimated time | At $70/hour |
|---|---|---|
| Brief review, reference check, and planning | 2 hours | $140 |
| Design and production of 24 effects | 18 hours | $1,260 |
| Editing, naming, and export checks | 3 hours | $210 |
| One consolidated revision round | 4 hours | $280 |
| Delivery notes and handoff | 1 hour | $70 |
| Estimated total | 28 hours | $1,960 |
This is an illustrative estimate, not a claim that 24 effects should cost $1,960 in every market. Your actual time could be lower for a set of simple UI clicks or much higher for creature vocalizations, layered weapons, procedural systems, or sounds that must be synchronized precisely to animation. If you are not sure how long a task takes, track the next few projects by activity—design, revisions, exports, communication, and implementation—then use your own records to improve future estimates.
A fixed quote should not disguise uncertainty. If the client has not decided how many weapon types exist, whether the effects need random variations, or who will integrate them, give a range or propose a paid discovery phase. You can turn the estimate into a fixed price once the missing decisions are made.
Revisions, rush work, and rights are separate pricing decisions
Many underpriced jobs are not caused by the first version of an asset. They are caused by unclear approval rules. Put these items in the proposal rather than leaving them to an email exchange after delivery.
- Revision rounds: define one round as one consolidated set of notes on the agreed direction. Correcting a technical error is not the same as redesigning a sound after the gameplay brief changes.
- Scope changes: if the client adds new weapons, extra variations, a new language, or an implementation requirement, quote the additional work before starting it.
- Rush delivery: charge for the scheduling disruption and overtime it creates, not just for pressing the export button faster. Confirm that the deadline is feasible first.
- Usage rights: state whether the client receives a license or a transfer of rights, and whether the price covers the game only or also trailers, advertisements, ports, downloadable content, and future editions.
- Project files and source material: specify whether editable sessions, synthesis patches, stems, middleware projects, and unused takes are included. Delivering rendered WAV files does not automatically mean delivering every working file.
Music pricing is a useful example of why rights and scope should not be hidden inside one number. In its 2025 Game Audio Industry Survey, GameSoundCon reports different per-finished-minute figures for indie, mid-core, and AAA freelance composers. Those figures describe music-composition rates reported by survey respondents; they are not a universal price list for sound effects, and they should not be used as a direct benchmark for implementation work.
For a second perspective on the mechanics of pricing, game audio freelancer Javier Zúmer explains the trade-offs between hourly, per-asset, and flat project fees in How (and How Much) to Charge as a Game Audio Freelancer. His discussion is useful for understanding why a fixed fee needs careful limits: it gives the client budget certainty, but transfers estimation risk to the freelancer.
What should a professional quote actually contain?
A one-page proposal is often enough for a small commission if it answers the questions that cause disputes. Include:
- Deliverables: counts, asset types, variations, duration or loop requirements, formats, sample rate and bit depth where specified, and naming conventions.
- Implementation boundary: state whether the price covers audio files only, middleware authoring, engine integration, in-build testing, and optimization.
- Timeline and client dependencies: dates for the first review and final delivery, plus when the client must supply references, builds, and feedback.
- Price and payment schedule: total, currency, deposit or milestones, invoice due dates, and how work pauses if a payment is overdue. Choose terms appropriate to your jurisdiction and platform.
- Feedback and changes: the number of included revision rounds, who consolidates notes, and how additional work is approved and billed.
- License and handoff: allowed uses, ownership terms, source files, attribution if any, and what happens if the project is cancelled.
A written agreement should match the actual deal rather than copy generic legal language blindly. If a project mixes custom work with pre-existing libraries, explain which items are commissioned exclusively and which are licensed assets; the distinction also matters when comparing free and paid game sound effects for indie projects. Upwork’s freelance contract guide outlines common subjects such as scope, payment, intellectual property, revisions, and termination. For significant commercial work, cross-border clients, or a full rights transfer, get advice appropriate to your jurisdiction instead of treating a general guide as legal advice.
How to respond when a client says the quote is too high
Do not immediately cut the price while keeping every deliverable. First find out whether the problem is budget, uncertainty, or a mismatch in expectations. Then change the scope in a visible way.
For example, a $1,960 package might become a smaller first milestone: 10 priority effects, one review round, WAV delivery, and no engine implementation. The remaining effects can be quoted after the team has approved the direction. The client gets a lower initial commitment, and you avoid silently doing the original job for less money. Another option is to offer a paid prototype or discovery phase that answers the most uncertain production questions before the full quote is fixed.
If a client wants a lower price because they are offering portfolio exposure, revenue share, or a promise of future work, treat that as a separate business decision. Do not count uncertain future income as if it were guaranteed payment. If you accept a reduced fee for a specific reason, write down what is reduced in return—scope, turnaround, usage, or revision time—and keep the terms clear.
If the job is a large library rather than a short custom commission, estimate how the asset list will grow before agreeing to a per-sound price. The production breakdown of a 500-effect indie RPG library is a useful related example of why organization and repeatable delivery matter alongside sound creation. For AI-assisted work, clarify what tools and source materials are allowed and document the rights assumptions; the guide to AI-generated game audio copyright and licensing covers that separate risk. Your price should be explainable without apology: it covers a defined result, a defined amount of work, and defined usage rights. Keep records of actual hours and change requests, revisit your floor when costs change, and let the next quote reflect what the last project taught you. That is more reliable than copying a competitor’s number without knowing what their fee includes.