Find the terms for the exact asset
Begin at the product or asset page and locate the licence that applies to that specific acquisition. A marketplace may host several publishers with different agreements. A free promotion may have its own conditions. Save the relevant text, its version or date if available, the asset identifier and your receipt or download record. A later homepage summary may not preserve what you accepted.
This page offers general information, not legal advice or a clearance service. We cannot grant rights to third-party recordings or determine whether a particular agreement covers your release. Where the wording is unclear or the commercial exposure is significant, ask the rights holder for written clarification and consider qualified legal advice.
Translate labels into actual obligations
“Royalty-free” usually describes a payment arrangement, not an absence of copyright. It does not automatically mean unrestricted redistribution, unlimited team access or permission for every kind of product. “Free” may describe the price alone. “Public domain” is a different concept again, and its application can depend on jurisdiction and the rights involved.
Creative Commons licences require attention to their exact names and versions. CC BY includes attribution obligations. CC BY-NC adds a non-commercial restriction and should not be assumed suitable for a commercial game. CC BY-SA and CC BY-ND raise different questions about adaptations and sharing; their application to a particular use needs careful analysis. CC0 is intended as a public-domain dedication with a fallback licence, but it does not guarantee that every possible third-party right has been cleared.
Do not rely on a filename or an uploader’s casual description when more formal licence information is available. On community platforms such as Freesound, inspect each asset’s current licence information and retain a record. The platform’s existence is not a blanket licence for its entire catalogue.
Map permission to the production team
Identify who is actually licensed: an individual, a named company, a project or a defined group of seats. Check whether contractors may access source files, whether an audio vendor can deliver editable sessions containing them and what happens when the work changes hands. A purchase on one person’s account does not automatically establish permission for a whole studio.
Separate source sharing from incorporation in a finished work. An agreement may allow sounds embedded in a game while prohibiting distribution as a standalone sound library. Public repositories, modding kits, template projects and open development builds can expose audio in ways that a conventional packaged release does not. Encryption or compression alone does not decide compliance; the agreement’s actual wording controls.
Licence-reading checklist
- Confirm the licensee, project scope and any seat limits.
- Check games, trailers, livestreams and promotional uses separately.
- Check contractor access, transfers and source-file delivery.
- Record attribution wording and required placement.
- Inspect restrictions on redistribution, templates and user tools.
- Retain written answers to unresolved questions.
Consider rights beyond the recording
A recording can contain recognisable music, speech, a performance or other material with separate rights. A library licence may address some of these issues, but do not assume it covers everything merely because the file is professionally presented. Listen for background music in a location recording and examine any stated limitations around voices or identifiable content.
Editing is not a universal cure. Pitch shifting, layering or trimming a recording does not automatically remove contractual obligations or third-party rights. Nor does a licence field embedded in metadata establish the uploader’s authority. Provenance, the agreement and the nature of the recorded material each contribute different evidence.
Build a rights record that survives release
Maintain an asset register connecting the original source identifier to your internal filename, in-game event, licence record and credit entry. Include who acquired the asset and any written exception granted by the rights holder. Keep that evidence outside the engine project as well, so a future migration does not erase the context.
Review the record when the project changes. A port, downloadable expansion, soundtrack release or developer toolkit can introduce a use you did not originally evaluate. Revisit assumptions rather than treating a previous approval as universal. If permission remains uncertain, replace the asset or resolve the question before shipping; do not let a successful technical import become accidental legal approval.