How to Document Music Licenses for Your Projects

Quick answer: Good music license proof ties one track to one permission at one point in time. For every track, save the license text or certificate, your receipt or plan, the track ID or file name, the download or generation date, where you used it, and any required credit line. Keep it in the project folder and in a central log, so you can answer a claim, a platform review or a client in minutes.

This guide is for anyone who publishes or delivers work with music in it: YouTubers, podcasters, wedding videographers, agencies and in-house marketing teams. It is about the boring part of licensing that determines whether a claim takes five minutes or five days.

You will get a list of what to save, a folder structure, a log template you can copy, and three worked examples showing records in action. The approach works for library music, Creative Commons tracks, and music you generate royalty-free for your projects. It does not replace reading each license; it makes sure you can prove you did.

Why records matter more than the license itself

Holding a license and being able to show it are two different things. Automated systems like Content ID match audio, not paperwork, so a correctly licensed track can still be claimed. When that happens, the claimant, platform or client will ask what permission you have. If you cannot answer specifically, your license is practically worthless in that moment.

Records also protect you from changes you do not control:

• Terms change. A library may revise its license. What matters is the version that applied when you obtained the track.
• Catalogues change. Tracks are removed from libraries, renamed or re-released. Your record proves what existed when you downloaded it.
• Accounts change. Subscriptions lapse, team members leave, email receipts get deleted.
• Third parties register tracks. A free track you used years ago can be registered by someone else later.

For a refresher on how claims work in the first place, see our guide on how to avoid Content ID claims.

The six things to save for every track

A few notes on each:

Source. Be specific. "Free music site" is not a source. Name the site and the artist or uploader.

License. Save the actual license text as a PDF, not just a link. Many paid libraries generate a license certificate per download; save that file. For Creative Commons tracks, save the track page showing the license badge and a copy of the license deed.

Payment or plan. A receipt or invoice shows you were a paying subscriber at the time. For subscription tools, note the plan name, since rights often differ by plan.

Identifier. Keep the original file name. Do not rename the master file; if you need a friendlier name, make a copy. Generated tracks have a generation record in your account history.

Date. The date links the track to the license version and plan that applied.

Usage. Where the track appears. For video, include timecodes if a track is only used in part of it.

A folder structure that survives years

Records only help if you can find them. Use the same structure for every project.

1. Create a music folder inside each project

   For example, a project folder named 2026-10 Spring campaign, with a subfolder called music containing the original audio files and a licenses subfolder.

2. Keep originals untouched

   Store the audio exactly as downloaded or generated, with the original file name. Edits and stems for the timeline live elsewhere.

3. Add a license file per track

   Name it to match the audio, such as the original file name plus license.pdf. Include the receipt or plan screenshot.

4. Write a short readme

   One text file listing every track, its source, license, date and where it is used in this project.

5. Update the central log

   Copy the same row into a single spreadsheet that covers all your projects.

The central log: a template you can copy

A spreadsheet is enough. One row per track per project. Here is a template with sample rows.

Sort by date, filter by source, and you can answer questions like "which videos use tracks from the library we are about to cancel?" in seconds. That question matters because many library licenses only cover content published while you were subscribed.

Generated music: what your record looks like

For generated tracks, your account's generation history is a core part of the record: it shows the prompt, the date and the account. Add the plan you were on and a copy of the license that applied.

On MusicVivo, Starter, Creator and Pro plans include a commercial license, and rights for tracks made while you were on a paid plan survive cancellation, so your record should note the plan at the time of generation. The Free plan covers personal, non-monetized use only. If a platform flags a MusicVivo track, you dispute with the platform and can ask MusicVivo to confirm the generation record. Read the current terms on the license page and save a copy with your records.

Saving the prompt is worth the ten seconds. If you ever need to show the track was created for your project rather than taken from elsewhere, a prompt that describes your specific scene is helpful context. For freelancers handing generated music to clients, our guide on using AI music in client projects covers what to include in the delivery.

Worked example 1: a Content ID claim on a tutorial

A tutorial channel gets a claim on a background bed from a paid library.

The record: log row shows the library, the track ID, a license certificate PDF dated when it was downloaded, and the fact that the channel was connected to the library account at the time.

The response: first, contact the library through its claim-clearing process, since many release claims for subscribers. If you need to dispute directly in YouTube Studio, write something short and specific:

Licensed via [library name], track ID 8812, downloaded 2026-09-28 under our active subscription. License certificate available on request. Used as background from 0:20 to 11:40.

Time spent: a few minutes, because nothing had to be searched for. Our guide on what happens after a copyright claim explains what the claimant can do next.

Worked example 2: a client asks for music clearance

An agency delivers a product video. The client's legal team asks for music clearance documents before running it as a paid ad.

The record: the project's music folder holds the original file, the license PDF, the plan or invoice, and a readme stating that the license covers paid advertising and client delivery.

The response: zip the licenses folder and send it with a one-line summary per track. Clients with legal teams generally want exactly this, and an agency that can produce it in an hour looks professional.

Without records: the editor would need to remember where the track came from, log into old accounts and hope the license still covers this use. That can delay a launch.

Worked example 3: deciding whether to cancel a subscription

A creator wants to cancel a library subscription. Before doing so, they filter the central log by source. Twenty-three videos use tracks from that library, and the library's terms say published videos stay covered but channel connection ends at cancellation.

Decision: they keep the license certificates, note the cancellation date in the log and stop using that library for new videos. They expect possible claims on old videos once the channel is disconnected, and they know exactly which videos and which tracks to point to. For a broader comparison of library subscriptions and generated music, see our Epidemic Sound alternative guide.

Backups and access: make records outlive your laptop

A perfect log on one hard drive is one spill away from being useless. Treat license records like financial records.

• Keep a cloud copy. Sync the central log and every project's licenses folder to a cloud drive your business controls, not a personal account.
• Export account histories periodically. If a service lets you download invoices or a list of generations, do it every quarter and file the export with the log.
• Give access to a second person. For teams, at least two people should be able to open the log and the license folders. For solo creators, a trusted partner or accountant will do.
• Archive, do not delete. When a project ends, move its folder to an archive, music and licenses included. Do not prune license files to save space; they are tiny.
• Store login details for music accounts in your team's password manager, so a license tied to an account does not disappear when the person who opened it leaves.

A quick annual review helps too. Once a year, filter the log for tracks from sources whose terms you have not checked recently, and look for licenses that depend on an active subscription. Note anything that has changed. It takes under an hour for most small channels and prevents surprises when you least have time for them.

Common record-keeping mistakes

One more pitfall: mixing personal-use and commercial-use tracks. If you generate or download music on a free personal plan, mark it clearly in the log. Later, when a personal project becomes a sponsored one, that note stops you from reusing a track the license never covered.

Attribution lines are records too

If a license requires credit, the credit line is both an obligation and evidence that you followed the terms. Save the exact text in your log and paste it into the description, show notes or end credits at publish time. Our guide on crediting music in your videos gives formats for different platforms. For context on how generated audio can be identified, see can AI music be detected, and for broader rights questions, is AI music copyrighted.

People also ask

What counts as proof of a music license? A record linking a specific track to a specific permission at a specific time: the license text or certificate, receipt or plan, track identifier, date and where you used it.

How long should I keep music license records? For as long as the content is online, plus a margin. Claims can arrive years later, and client contracts or local rules may require longer.

Is a screenshot enough as license proof? It helps, but it is stronger with the license text, a receipt or account record and the original file. Terms pages change, so dated copies matter.

What should I include when disputing a Content ID claim? The reason, the source, the license or plan, the date, the identifier and where the track appears. Short and specific works best.

Related reading

• Copyright-Free Music for YouTube: A Creator's Guide
• Music Licensing Basics for Small Businesses
• Background Music for Wedding Videos
• Is AI-Generated Music Royalty-Free?
• AI Music Commercial Use
• Export and Use AI Beats

Product and company names mentioned in this article are trademarks of their respective owners. MusicVivo is an independent product and is not affiliated with, sponsored or endorsed by any of them. Comparisons are based on publicly available information at the time of writing; check each provider's own site for current features, pricing and terms.