Getting music rights for a game is not a final-week paperwork task. It is a creative decision with a release plan attached. The earlier a team knows what it wants to use, where it needs the music to appear, and who can approve that use, the more confidently everyone can build around it.

This is a practical planning guide, not legal advice. Every project, agreement, territory, and release is different. Use it to make a clean brief, identify the questions that need an answer, and know when a music lawyer or rights professional should take over. Keep the decision notes close to the creative brief, so the team can make the next choice with context rather than memory. For the wider picture of choosing original, catalogue, or commissioned music, read our music licensing guide for video games.

1. Decide what the music must do

Start with the actual player and release moments. Is the music in gameplay, a menu, a cutscene, a launch trailer, a social clip, a downloadable soundtrack, or all of them? Will the game launch on one platform and later reach consoles? Will players and creators stream it? A useful clearance request describes the work instead of asking for a vague yes.

Write a one-page use map before contacting anyone: the track or brief, the game and scene, platforms, territories, term, anticipated launch window, marketing uses, whether edits or loops are needed, and creator-video expectations. This does not replace an agreement. It prevents the team from discovering late that the permission covers the build but not the trailer that brings people to it.

Blank colored cards arranged as a game music planning path beside a controller and headphones

A small game does not need to predict every future opportunity. It does need to be honest about likely ones. If a trailer, festival demo, console port, or community stream is already part of the plan, put it in the request. A rights holder can evaluate a clear proposal. Nobody can safely approve “whatever we do later.”

2. Separate the song from the recording

One of the most important checks is also the easiest to miss: the song and a particular recording of that song can be separate works. The U.S. Copyright Office explains that a musical composition covers the music and lyrics, while a sound recording is the particular recorded performance. They are commonly owned and licensed separately. That means permission for the song is not automatically permission for a famous artist’s recording, and permission for a recording is not automatically permission for the underlying composition.

Abstract diagram showing two separate music rights

For a commissioned cue, the creator and team may be able to make these decisions together in one agreement. For an existing song, the path may involve a songwriter, publisher, artist, label, producer, or more than one contributor. Do not infer ownership from a public upload, a streaming listing, or a social profile. Treat those as leads, not approvals.

When ownership is unclear, pause the plan rather than building the track into a public piece. The Copyright Office’s public records portal can help begin research, but it is not a substitute for a current clearance conversation. Keep a note of who was contacted, what was requested, and what was confirmed in writing.

3. Match the permission to the full release

A licence is useful only when it matches how the game will travel. Make the scope specific: platforms, countries, duration, media, paid advertising, trailers, social clips, patches, downloadable content, events, and soundtrack plans. If music needs to be edited, looped, mixed under dialogue, or supplied as stems, say that too.

Streaming deserves a direct line in the conversation. A game can be playable and still create frustrating claims or removals for community members making videos about it. The realistic goal is not to promise that every platform decision is controllable. The goal is to understand what the agreement allows, communicate honestly with the community, and avoid making a claim the team cannot support.

Abstract route map for defining the scope of a game music license

Watch loose language. “Royalty-free” usually describes a payment structure, not a universal permission. “Exclusive” can depend on territory, category, and time. “In perpetuity” may be broader than a small team needs. Read the definitions in the agreement, then compare them to the use map. If the language does not cover a likely use, raise it before signing rather than relying on a helpful email thread.

4. Choose the music path that keeps the project moving

Original commissioned music, a direct licence for an existing song, and catalogue music can all be good choices. The right one depends on the game’s creative needs, budget, timing, and rights scope. Commissioned music can give a team playable variations, loop points, and a close creative relationship. Existing music can carry a precise cultural signal, but it may require a longer clearance path. Catalogue music can be efficient when its terms clearly fit the planned use.

Do not choose only on price. A free download with unclear terms can cost more attention than a paid option with an understandable agreement. Likewise, a familiar song can become a poor fit if the team cannot secure the rights it needs in time. The best option is the one that supports the player experience and the project’s real release plan.

If the game needs music that changes with play, make that part of the brief. Our guide to video game music composition shows how a cue can be planned for loops, layers, and transitions before it enters a build. That creative planning makes the clearance conversation more concrete too.

5. Know when the question needs a specialist

A team does not need to become a law office to make a better first decision. It does need to recognise when the stakes have outgrown a quick search or a template. Bring in a qualified music lawyer or clearance professional when ownership is unclear, the song has several writers, the release reaches multiple territories, the project uses a well-known recording, the agreement includes royalties, or the team needs a broad long-term grant. Those are moments where a precise answer can save a much larger problem later.

It is also reasonable to ask for help when the language does not match what was discussed. If a call or email says the game can use a track in trailers and creator videos, but the draft agreement only describes gameplay, stop and reconcile the difference. The most useful agreement is not the longest one. It is the one the creators and the team can read together, understand, and use when the project changes.

Keep the creative conversation respectful. A rights holder is not a final obstacle between the team and a launch. They are a collaborator with work to protect. Be ready to explain the game, the audience, the use, the schedule, the payment structure, and the credit. A clear, grounded request makes it easier for the other side to decide whether the project is a fit.

If the answer is no, or the scope is beyond the project’s budget, move on while there is still time. A replacement is easier before the cue has become the identity of a trailer or a level. The strongest small-team habit is not forcing every idea through. It is keeping enough room in the process to choose a path that everyone can support.

6. Keep proof with the audio files

Once the permission is in place, create one delivery folder that another teammate can understand. Keep the signed agreement or licence, approved credit language, contact details, proof of payment when relevant, the final audio files, stems or alternate mixes, and a plain-language note on approved uses. Make one person responsible for keeping it current.

Abstract audio delivery graphic with a keyboard-like grid and arrows

This is not paperwork theatre. It means the team can answer a question when a trailer editor needs a cue, a platform asks about rights, a collaborator joins late, or a community creator asks whether a clip is okay to post. Clear records protect the relationship with the music creator as much as they protect the game.

For a small team, use a simple naming system and a release checklist. Record the track name, version, source, ownership contact, agreement location, approved uses, credit, and any expiry or renewal date. Do not let the only explanation live in one person’s inbox. The same care that helps a build ship also helps the creative collaborators behind it feel respected.

Make the folder useful in the moment, not merely complete. A trailer editor should be able to find the approved mix and the credit without chasing a producer. A new community manager should be able to tell whether a short clip is covered without translating legal language from scratch. A composer should be able to confirm which version was used and how they will be credited. These ordinary handoffs are where a good clearance plan proves its value.

7. Use the clearance plan to support the community

Good music is part of how players remember a game. Good rights planning is part of how that music can keep reaching people through trailers, streams, updates, and conversations. That is why the planning work belongs near the beginning, beside the creative brief, not after the world already depends on the cue.

That early work also gives creators a cleaner way to collaborate. Instead of asking them to guess how broad the use might become, the team can share the project’s real intentions. Instead of treating credit as an afterthought, it can be agreed with the same care as the mix. The result is not only safer. It is a more durable creative relationship, with less friction between the people making the game and the people helping it sound like itself.

Jams and Joysticks is built around the people doing the work. Explore the creator conversations, follow the stories from the community, or connect with the team when you have a project or perspective to share.

Before the music enters the build

A music-rights check

  • Name every place the music will appear.
  • Separate the composition from any chosen recording.
  • Ask the rights holder for permission that matches the real release plan.
  • Get the answer and the scope in a clear written agreement.
  • Store the agreement, credit, and final files together.

Frequently asked questions

Do I need permission to put a song in my game?

Usually, yes. A team should have clear written permission that covers the planned game use. A song and a particular recording can have different owners, so using a familiar recording may involve more than one permission.

Can I use royalty-free music in a commercial game?

Sometimes, but only if the actual licence permits the intended commercial game use. Check platforms, duration, advertising, trailers, creator videos, attribution, and whether the team needs to edit or loop the music.

When should a game team start music clearance?

Start as soon as a track becomes a real candidate, before it is built into a trailer, level, or public demo. Early scope decisions make it much easier to replace a track or ask for the right permission.