When you add background music and sound effects to a game or app, the source asset files themselves become part of the distributed product, unlike when you use them in a video. It is therefore especially important to check how the asset provider’s terms address integration into games and apps and redistribution.
This article outlines the points to check from the planning stage through post-release updates. Always give precedence to the provider’s terms for the specific asset.
Define the Distribution Model First
Assets are used differently in browser games, mobile apps, PC games, in-store apps, free ad-supported apps, and paid apps. Also determine whether the product will be sold as a download or offered by subscription, whether it generates advertising revenue, and whether users can access the asset files.
Check Whether Integration Is Permitted
Even when audio assets are intended for use in videos, integrating them into a game or app may be subject to separate terms. Look for language in the terms covering games, apps, software, interactive content, or integration into a product.
Even when this use is permitted, check for restrictions on the number of titles, number of distributed copies, platforms, or scope of commercial use. Do not decide based only on whether commercial use is allowed; make sure app distribution is covered as well.
Do Not Leave Asset Files Accessible for Extraction
Even if audio files must be bundled with a game or app for playback, allowing users to extract and reuse them may constitute redistribution under the terms. Where possible, consider implementation and distribution methods that do not effectively distribute the assets in their original form.
Technical safeguards alone do not guarantee compliance with the terms. You must first confirm that integration into the product is permitted in the first place.
Test Loops and Sound Effects on Actual Devices
Game music often plays for extended periods, so check whether loop transitions sound natural and whether repeated phrases become distracting. Sound effects communicate responses to player actions, but you should also test whether they overlap excessively during rapid input or conflict with notification sounds.
For guidance on the timing and volume of short sound effects, see How to Add Sound Effects: Timing and Volume Basics.
Include Credits and Keep an Asset List
For assets that require credit attribution, place the credit where the terms specify, such as an in-app credits screen, game credits, or the official website. Keep a record of the assets used, their providers, the terms URL, and the date checked so you can review the information during post-release updates.
Assign Responsibility in Outsourced and Collaborative Development
When several people are developing a product, decide who will obtain the assets, who will review the terms, and who will add the required credits. In client projects, you need to distinguish between delivering the finished product and handling the underlying asset files. Also review What to Check When Using Audio Assets for Client Work.
Pre-Release Checklist
- Integration into games or apps is permitted
- Sales, advertising, and distribution platforms fall within the permitted terms
- You have confirmed that the implementation does not redistribute the assets themselves
- You have prepared the required credits and an asset list
- You have tested music loops and overlapping sound effects on actual devices
For the basics of reviewing terms, see Terms to Check Before Using Background Music and Sound Effects. For organizing downloaded assets, see How to Organize Background Music and Sound Effects After Downloading Them.
This article provides general information only. Whether a particular use is permitted depends on each provider’s current terms and license and on the actual implementation. If you are uncertain, consult the provider or a qualified professional.
