18 November 2026 · LicenseTrack Team
Video Game Music Licensing: A Guide for Independent Composers
Before music enters a game, map who controls each right and agree how the score or recording may be used in gameplay, releases, updates, and later projects.
When a game studio asks to use your music, work out which composition and recording are involved, who can approve each, and how the game will use and distribute them. Interactive playback, ports, downloadable content, updates and promotions can all affect the scope a composer and developer need to discuss.
This is general educational information, not individualized legal advice. It is not a contract template, a clearance decision for a particular track, or a statement of universal game-music law. Copyright rules and contract effects differ across jurisdictions and agreements. Ask a qualified music-rights adviser in the relevant jurisdictions to review a consequential or unclear grant.
Map the composition and the master separately
A piece of music and a particular recording of it are different works. The composition is the underlying music and any lyrics; the master is a specific fixed performance or recording. The U.S. Copyright Office describes them as separate works that are commonly owned and licensed separately. A licence for one does not automatically clear the other. U.S. Copyright Office, Circular 56A: Musical Compositions and Sound Recordings
Before you quote, sign or deliver files, ask:
- Composition: Who controls the music and lyrics? Are there co-writers or co-composers, agreed shares, a publisher, administrator, collecting-society mandate or prior agreement that affects who may approve this use?
- Master recording: Who controls this exact recording and version? Did a label, producer, studio, distributor or another party fund or acquire rights in it?
- Contributors and samples: Did performers, session musicians, producers or other contributors sign releases or agreements for the proposed game use? Does the track include a sample, loop, library sound, lyric, arrangement or other material that needs separate clearance?
- Authority: Who is entitled to sign for each interest, and can they grant all the proposed rights or only a share? Is another approval or licence needed?
The Copyright Office identifies composers and lyricists as authors of musical compositions and performers, producers and sound engineers as possible authors of sound recordings. Who owns or may license a particular work depends on the facts and agreements, so treat every role as a prompt to check the paperwork rather than an ownership conclusion. Circular 56A
Write down whether the proposal covers the composition, the identified master, or both. If you control only some shares, state the share you can offer and identify the permissions still needed. If the studio commissions new music, clarify who will control the composition and resulting recording, and when any licence or transfer takes effect. For more on the rights layers, see composition and master rights and recorded music rights.
Describe what the music does during gameplay
A soundtrack may be triggered, repeated, layered or changed in response to play. Put those expected behaviours into the brief and agreement instead of relying on a vague phrase such as “use in the game”.
Describe whether the music will:
- play in a title screen, menu, particular level, location, cut-scene or credits;
- start or stop on a player action, game event, route, score, character state or other condition;
- loop continuously or repeat after a transition;
- change through stems, layers, alternate mixes, crossfades, intensity changes or adaptive arrangements;
- be shortened, edited, faded, remixed, re-orchestrated, translated, or combined with dialogue and effects;
- be muted, skipped, selected or controlled by the player; or
- appear in a launcher, companion app, soundtrack feature or other part of the release.
Say whether the studio may make edits itself, may ask you to supply alternate versions, or must return to you for approval. Identify which delivered files it may use and whether it may create additional versions. If the grant covers only one supplied mix, make that limit explicit.
“Interactive,” “synchronisation,” “performance,” “adaptation” and similar labels may have different legal effects across jurisdictions and contract language. Do not assume that a familiar film or streaming licence label automatically describes every in-game trigger or adaptive use. In the United States, for example, 17 U.S.C. § 106 lists rights such as reproduction, preparation of derivative works, distribution and public performance, while the sound-recording performance right is described separately; statutory limitations and other provisions also matter. That U.S. statute does not settle how a specific gameplay use is classified elsewhere or under a particular contract. Describe the acts the game needs and have the proposed grant reviewed under the governing law. 17 U.S.C. § 106
Cover the intended game releases and platforms
List the named game and the releases the developer expects to make: for example, digital or physical distribution, intended storefronts, PC, console, mobile or cloud versions, and ports. Treat each as a scope question; do not assume that a licence for one release automatically includes every later platform, region, bundle or subscription catalogue.
The game publisher must also satisfy the terms of the services through which it distributes the title. Steam’s onboarding guidance says publishers should not publish content they do not own or have adequate rights to use. itch.io’s publisher terms place responsibility on the publisher to have rights needed for submitted content and grant itch.io a stated licence to use the content in connection with its service. These platform obligations are separate from the composer’s permission to put music in the game: a store’s rules do not themselves clear the composition or master for the developer. Review the platform’s current terms and make sure the music grant gives the developer only the downstream permissions it needs for the agreed release. Steamworks: Onboarding · itch.io Terms of Service, section 4
Ask the developer to identify:
- each store, console, mobile service or other distribution channel in the planned release;
- the countries or territories in which the game will be offered;
- whether music is bundled in the build, downloaded later, streamed, or otherwise delivered;
- what limited rights a platform, distributor or hosting service needs to operate, host, promote or deliver the named game; and
- whether platform, publisher or distributor terms require a warranty, permission or technical use beyond the proposed grant.
Platform terms change, and publisher-facing language may be broader or narrower than a composer’s agreement. The parties should compare them and resolve a mismatch before submission. The music-rights grant should describe the actual game uses and permitted distribution chain; platform acceptance is not proof that every music right has been cleared.
Decide how updates and later uses are handled
A release may continue after launch through bug fixes, patches, new builds, translations, ports, downloadable content or expanded editions. Ask whether the agreed licence lets the developer keep the music in updates and replacement builds of the named game, and whether it covers new gameplay areas or newly added uses.
Name the boundary. The parties might treat technical patches that preserve the same game and music use differently from new DLC, a remaster, sequel, spin-off, separate soundtrack album, standalone music release, trailer campaign or new product. That is a negotiated scope choice, not a standard rule. State which changes remain within the licence and which require a fresh approval, fee or grant.
Also decide what happens if the licence expires or ends: may existing users keep playing a previously downloaded build, can the developer distribute updated builds, must new sales stop, can the music remain in promotional material, and what happens to copies held by a platform? Make the answer workable for both sides and consistent with platform distribution terms. Do not assume that an update or continued availability is automatically included.
A practical licence-scope checklist
Use these questions to review a proposed agreement. The answers are deal-specific; none is a universal required term.
- Named project: Which game title, edition, publisher and production does the grant identify? Are a demo or beta included?
- Rights and assets: Does the licence cover the composition, the exact master, both, or only a stated share? Which files, versions, stems and alternate mixes are included?
- Permitted uses: Can the game reproduce, embed, trigger, loop, adapt, mix, stream, download, distribute or perform the music as intended? Which gameplay states, edits and player controls are allowed?
- Distribution chain: Which publishers, platforms, storefronts, cloud services or distributors may handle the game, and what limited downstream permission may each receive?
- Territory: Which countries or regions are covered? Does the answer address global storefront visibility and any exclusions?
- Duration: When does the grant start and end? Is there a production period, release period, archive or sell-through period, and a process for renewal?
- Exclusivity: Is the grant exclusive or non-exclusive? If exclusive, to which game, rights, platforms, territory and period? What uses remain available to you?
- Updates and additions: Are patches, bug fixes, ports, DLC, remasters and expanded editions included? Which require a separate written grant?
- Uses outside the deal: Are trailers, advertising, social clips, livestreams, soundtrack albums, sequels, spin-offs, merchandise, mods or other products included or expressly reserved?
- Credit, payment and records: What fee or royalty is due, how will permitted use be credited, and what records or approvals should each party retain?
If an agreement uses broad words such as “all media,” “all platforms,” “perpetual” or “in all versions,” check that they match the intended rights, title, term and uses. State exclusions clearly. If project identity, authority, territory, term, exclusivity or future-use boundaries are uncertain, pause delivery or signature until the wording is understood.
Sources and further reading
- U.S. Copyright Office, Copyright Registration of Musical Compositions and Sound Recordings (Circular 56A) — explains the difference between compositions and sound recordings, and identifies potential authors of each.
- U.S. Code, 17 U.S.C. § 106: Exclusive rights in copyrighted works — a U.S.-specific list of rights and qualifications; not a worldwide classification of game uses.
- Steamworks Documentation, Onboarding — publisher guidance that content distributed on Steam must be owned or adequately cleared.
- itch.io, Terms of Service, section 4: Publisher Content — publisher responsibility for rights and the service licence for submitted content.
Sources checked on 18 November 2026. Laws, platform terms and contract language can change and vary by territory. This page is general information, not legal advice for a particular composer, recording, game, agreement or release. It does not determine ownership, clear any track, or promise a legal outcome. Consult a qualified adviser in the relevant jurisdiction for a specific deal.
Related guides
LicenseTrack plans
Start using the live workflow
Compare the current subscription plans and see what is included before creating your account.