Proof Bundle

Audiodrome | Last Updated: March 22nd, 2026 | 4 min read | Glossary

A proof bundle is a single, organized set of documents and references used to show that you had the right to use a track, asset, or recording in a specific project. In music licensing and copyright disputes, it usually combines license proof, transaction records, asset details, ownership or permission documents, and project-level context so you can answer claims quickly and consistently.

Quick facts:
Also called: license packet, evidence pack, claim support file
Applies to: YouTube claims, Meta Rights Manager disputes, client delivery, takedown and counter-notice workflows
Used for: proving rights, scope, ownership, and permission
Not the same as: a license by itself, legal advice, or platform approval.

Example:
A client uploads an ad to YouTube and gets a Content ID claim. Your proof bundle includes the license certificate, invoice, track title and ID, the export date, the client name, the campaign URL, and the email showing the music was cleared for that specific use, which gives you a clean package for dispute or escalation.

Free tools icon

Free Tools:

Am I likely to get flagged? Claim Risk Checker

Gotchas:

  • A receipt alone is rarely enough. It may show payment, but not the exact rights granted, project scope, territory, term, or whether client transfer was allowed.
  • Platform disputes are time-sensitive. YouTube gives claimants 30 days to respond to a dispute, so missing files or messy records can slow you down when speed matters.
  • A proof bundle should match the exact asset used. Wrong edit, wrong stem, missing track ID, or a license tied to a different channel or client can weaken your position.
  • It does not guarantee a win. Platforms do not make final ownership determinations, and a counter-notice is a legal process with required statements and identification details.

FAQs

Usually: the license or grant of rights, invoice or order confirmation, track title and ID, creator/client name, project URL or file name, usage notes, and any approval or correspondence that clarifies scope. Where relevant, add registration, transfer, or permission documents.

Not by itself. Screenshots help, but they are stronger when backed by a full license document, transaction record, and asset identifiers that connect the permission to the exact use.

Use one before client handoff, before publishing paid or commercial content, and any time you expect automated matching, copyright claims, or later reuse across channels, ads, or platforms.

No. A proof bundle supports your position, but a counter-notice has its own legal requirements, including identification of the removed material and required statements.

Yes. Registration can strengthen the evidentiary position of a copyright owner, and transfer or recordation documents can help show who actually controlled the relevant rights.

Related terms

License Certificate • License ID • EULA • Allowlisting • Copyright Claim • Counter-Notice • Usage Scope • Rights Clearance • Track ID