Musicians increasingly ask whether their music was used to train an AI model, and whether they can show a song existed before the model was built. A timestamp can help with one narrow part of that: it shows that your exact files existed no later than a recorded time. It can’t show whether a model was trained on your song, whether an AI output copied it or whether any use was lawful. Those questions depend on facts you may not have, on contracts and on law that is still developing in many countries. This is general information, not legal advice.
Table of Contents
What a dated record can show
- That a particular master, stem set or lyric sheet existed no later than a date.
- That it hasn’t changed since. If one byte changes, the fingerprint no longer matches.
- That your catalogue, or part of it, pre-dated a model’s release, a platform’s terms change or a release date, if the dates fall that way.
What it can’t show
- Whether your song was in a training dataset. That’s information held by the model’s developer.
- Whether an output is derived from your song. That needs comparison of the music and expert and legal analysis.
- That you’re the author or owner. Drafts, sessions and contracts help there.
- That any use was unauthorised. Licences, platform terms and law all matter.
Records worth keeping
- Masters and stems in original formats, with dates.
- Session files and demos that show how a song developed. See prove WAV stems existed before a date.
- Release records: distributor receipts, release dates and platform pages saved with dates.
- Terms you agreed to: distributor, platform and licensing terms at the time, saved as PDFs or screenshots.
- Evidence of suspicious use: dated saves of any output or page you think copies your work, with the tool and prompt if known.
- Correspondence with platforms and developers.
A routine
- Timestamp masters and stems before release, or now for existing songs. See how to timestamp a file and timestamp EP masters and stems before release.
- Zip older catalogues by year and timestamp each zip (up to 10 files per TimeBind).
- Keep the certificates with the catalogue.
- When you save a suspect output, record the date, source and steps. Add it to a TimeBind.
- Talk to an entertainment lawyer or your rights organisation if you think a use is unauthorised.
Your browser makes the fingerprint and the files stay on your device, so the audio isn’t shared by timestamping it.
Related reading
- How artists can get ahead of AI tampering
- Copyright and a song made with AI
- AI mastering, stem separation and copyright ownership
- Music copyright proof
Frequently Asked Questions
-
Can a timestamp show an AI used my song?
No. It can show that your song existed by a date. Whether it was used is a separate question.
-
Does it stop AI companies using my music?
No. A timestamp doesn’t prevent use.
-
Should I timestamp old catalogue songs?
It’s a reasonable step. A zip per year or per album is practical. A timestamp records the date you make it, not an earlier date.
-
Can I use a timestamp in a claim?
It may be one piece of evidence. Whether and how it’s used is a matter for your lawyer.
-
What does a TimeBind cost?
Your first Pooled TimeBind is free, with no credit card required. After that, Pooled TimeBinds start from US$5, and an ASAP TimeBind is US$15. See plans and pricing
Date what you have today
Free to start. The files stay on your device and your browser makes the fingerprint.
Last fact-checked: 10 November 2026.
Date your catalogue now
Add your masters, stems and lyric sheets to a TimeBind so you have a dated record of what existed.
Make your first TimeBind free → See plans and pricing
Your first Pooled TimeBind is free, with no credit card required. After that, TimeBinds start from US$5, and an ASAP TimeBind is US$15. Your browser makes the fingerprint and the file stays on your device. A TimeBind shows a file existed no later than the recorded time. It doesn’t show who made it.







