Video game music licensing, copyright, and rights explained

A game designer told me recently that music and audio licensing is a minefield, and that I haven’t written enough on that topic. So here’s the map.

Music is where a lot of otherwise-careful studios get burned. Not because the law is exotic, but because one song hides more moving parts than anyone expects. You can pay for a track, drop it in your trailer, and still get a copyright strike. You can commission a full score, pay the composer in full, and still not own it. You can clear a song for your game and watch streamers get muted the day you launch.

None of that is bad luck. It’s the predictable result of a few rules nobody explained. Let me explain them.

Every track is two copyrights

Start here, because everything else hangs on it. Every piece of recorded music contains two separate copyrights, owned by two different people:

• The composition. The song itself. Melody, harmony, lyrics, arrangement. Owned by the songwriter, usually run by a music publisher.
• The sound recording. The specific recorded performance, the “master.” Usually owned by the recording artist or, more often, the record label that paid for the session.

These are legally distinct. Clearing one does not clear the other. The classic example: the Hey Jude composition and the Beatles’ recording of Hey Jude are owned by different companies. License the song, use the record, and you’ve still infringed.

For a developer, this is the root of most music clearance failures. Putting one commercial track in your game can mean getting permission from two different rightsholders. Miss either one, and you’re infringing.

The rights you actually need to clear

Placing music in a game can touch five different rights: reproduction, synchronization (sync), master use, public performance, and adaptation. In practice, they collapse into a manageable set depending on where your music comes from.

If you commissioned an original score: there’s nothing to license from a third party. You commission it and take ownership. All the risk lives in the composer contract, not in licensing. (More on that below.)

If you’re using a pre-existing commercial track: you need two licenses, every time.

• A sync license for the composition, from the publisher.
• A master use license for the recording, from the label.

Both are mandatory. Missing either is infringement.

If it’s for a trailer, ad, or store page: that’s a separate clearance from in-game use. This is the one studios blow constantly. Music cleared for the game is not automatically cleared for the trailer. Different use, different grant, sometimes a different price.

One more piece worth knowing. Normal purchase-and-play of a game in the US is generally not a public performance, so a player simply playing your game does not trigger a performance royalty domestically. Broadcast and trailer use can be a different story.

Where your game’s music comes from

Every track in your game came from one of four places, and each has a different risk profile.

1. Original commissioned score. A composer writes bespoke music. This is an ownership problem, not a licensing problem.
2. Pre-existing commercial music. A known song or recording. This is the two-clearance problem, and it’s expensive.
3. Library / production / “royalty-free” music. Pre-cleared catalogs. Cheap and fast, but the license scope is the trap.
4. AI-generated music. Cheap, fast, and legally the shakiest of the four.

Most indie games mix all four. The problem is that studios rarely track which cue came from where, or what each one is actually cleared for. That’s how you end up unable to answer a simple question at launch: am I cleared for the game, the trailer, streaming, and the soundtrack?

Who owns your video game’s music? The composer contract

Here’s the one that surprises people. You paid the composer, so you own the music, right? Not automatically.

For an original score, whoever owns the copyright controls your game’s music. You get ownership one of two ways, and good contracts use both.

Work-made-for-hire (WFH). A commissioned work counts as work-for-hire only if two things are true: it fits one of nine specific statutory categories, and both sides signed a written WFH agreement before the work was created. For music, the category that works is “part of a motion picture or other audiovisual work.”

A video game is an audiovisual work. Courts have treated games this way since the early 1980s, and the Copyright Office registers them as audiovisual works. So a commissioned score for a video game can qualify as valid work-for-hire.

But you rely on the assignment backstop anyway. The WFH pathway is imperfect for music. A standalone score delivered as separate tracks is arguably not “part of” the audiovisual work. So the best contracts pair the WFH language with a present-tense fallback: if this isn’t a work made for hire, the composer hereby assigns all rights. Belt and suspenders. You want both.

A few deal points that decide who actually walks away with what:

• Buyout vs. royalty. Games skew heavily toward a flat one-time buyout, where the developer owns everything. Backend royalty deals exist but are far less common than in film and TV.
• What composers keep even under a buyout. If the contract is silent, a composer usually retains the writer’s share of performance royalties, and a hiring party generally can’t capture that. But under a full buyout with an assignment, the developer owns everything else, including soundtrack rights, unless the contract carves them back out for the composer. That is usually not what the composer wants, so spell out the writer’s share and the OST rights on purpose rather than leaving it silent.
• Adaptive music. Interactive scores are built from stems and layers that recombine at runtime. Your contract should spell out that you own and receive the stems, and that you have the right to recombine and adapt them. This is a common drafting gap.

How video game music licensing actually works

If you’re licensing a commercial song, remember the two-clearance trap: sync license from the publisher, master use license from the label, usually two different owners. Miss either and you’re infringing.

The deal terms that actually move the price and the risk:

• Territory. Worldwide costs more than limited.
• Term. Perpetual costs more than a fixed window.
• Media and platforms. In-game only? Console plus mobile plus PC? Trailer? Store page? Each one is a scope decision.
• Exclusivity. “No other games for the term” spikes the fee.
• Options. The right to extend to sequels, DLC, and ports at pre-agreed rates.
• Most-favored-nations (MFN). If another rightsholder on the project gets a better deal, you match everyone up to the best one. Devs forget to track this.

And a myth worth killing: “royalty-free” is a marketing term, not a legal one. It usually means “no per-play royalty.” It does not mean “no license” and it does not mean “all rights included.” Most reputable libraries grant you sync and master but keep back-end rights. The license may not cover every use you have in mind, and in-game integration, streaming, and OST resale are all distinct scopes. Even the free and indie tiers can hit you with a takedown if you break the terms.

Will your music get streamers banned?

This is the section that lands hardest, because it’s a business problem wearing a legal costume.

Your game’s sync and master licenses may not explicitly cover third-party streaming by players. So a streamer playing your game with uncleared in-game music can get muted, Content-ID claimed, or DMCA’d, even though you licensed that music for the game itself. A license to use music in your game is not necessarily a license for streams of your game. Different right.

If you’ve paid attention to game streaming, you’ve probably watched this happen. Notices have gone from a trickle to thousands per week, mostly over background music in old clips and VODs, much of it policed by copyright enforcement companies and music aggregators who take down with impunity.

Streamers have had to delete their own VOD libraries to dodge a permaban. Twitch’s guidance was to check the game’s EULA for streaming rights, which quietly puts the duty on the studio to make its music stream-safe.

The platforms work differently, which changes how you get caught. Twitch is notice and DMCA driven. YouTube runs automated Content ID scanning against a rights-holder database. Same underlying risk, but two different avenues, and YouTube’s is a bit scarier because of how automated it is. Nobody has to decide to come after you.

Here’s the business damage. If your game gets streamers struck, streamers avoid your game. And streaming is the single most valuable free marketing channel an indie has. That’s why studios now demand “stream-safe” or “creator-friendly” music as a licensing requirement, and why some ship a “streamer mode” that swaps out copyrighted tracks.

When your music can get your biggest fans banned, that’s a marketing problem that’s written into the contract. Just make sure you’ve got that covered. And even if you do have a proper license, someone could be out there policing that music without the owner’s knowledge, or without taking your license into consideration. I’ve heard plenty of stories about false positives and errors in the takedown arena.

Can you copyright AI-generated music?

Reaching for AI music to save money? There’s two questions here, with two halves that have different answers.

Can you use it? Often yes, on a paid tier, subject to that tool’s terms.

Do you own it, and can you protect it? Often no, under US law.

Current US guidance is that purely AI-generated output isn’t protectable, and prompts alone don’t get you there. Only the human contributions in a hybrid work are copyrightable. The practical consequence is blunt: an AI-generated cue may have no copyright, which means a competitor can copy it freely. You have permission to use it, and no ownership to enforce.

There’s also live litigation over the training data behind these tools. Major labels filed suit against the big AI music generators in 2024. Treat AI-generated game music as an exposure item, though for end users there’s probably a low risk of someone coming after you directly. It’s not a safe harbor. Read the specific tier’s terms of service before you ship, because free tiers usually grant no commercial rights at all.

If you want AI music you can actually protect, keep a human meaningfully in the loop and disclose the AI material when you register.

Selling the soundtrack

Releasing the OST as its own product, on Steam, Bandcamp, Spotify, is a legally different use from playing it inside the game. Your in-game rights don’t automatically let you sell the soundtrack.

To distribute the OST, you generally need reproduction and distribution rights for downloads, streaming and distribution rights for the platforms, and separate clearance for any sample or cover. The master rights stay distinct from the composition, same two-copyright rule as always. If a track’s license doesn’t permit standalone sale, studios usually just leave it off the OST. And the composer typically takes a separate revenue share on soundtrack sales versus game sales, so settle that in the composer deal up front, not after the OST charts.

Very often, especially on lower-budgeted games, the composer is allowed to release their own soundtrack off the game platforms, while the publisher or developer takes the game-platform soundtrack rights. How the money gets shared is whatever the contract says.

What you should do

You don’t need to become a music lawyer. You need to be able to answer four questions about every track in your game:

1. Where did it come from? Original, licensed, library, or AI.
2. Is it cleared for the game? For licensed tracks, both sync and master.
3. Is it cleared for the trailer and store page? Separate clearance.
4. Is it stream-safe, and can you sell it on the OST? Two more separate questions.

If you can’t answer those cleanly, that’s the gap. Build a simple map: every track, every use, cleared or not. Most studios have never done this, which is exactly why the problems surface at launch instead of in pre-production.