How Audiverify Works
From upload to verification in about a minute. Here is exactly what happens at each step.
Upload Audio
Upload a track and the system generates a unique SHA-256 fingerprint from the audio data. This cryptographic hash is unique to the exact file -- even a single byte change produces a completely different fingerprint.
Accepted format: WAV (16-bit / 44.1 kHz). Max 500MB per file.
Duplicate Check
The fingerprint is checked against every certificate in the system. If a match is found, you'll see the existing certificate and can file a claim, link it as a version (remix/cover), or upload a different file.
This prevents the same audio from being documented twice without transparency.
Make Your Declaration
You write a declaration about the relationship to the work -- original composition, remix, cover, sample, or AI-assisted. This statement is timestamped and stored as part of the certificate record.
Audiverify records the declaration as stated. It does not verify the accuracy of claims, ownership, or grant any rights.
Certificate Issued
A unique certificate number is generated (e.g. AUD-2026-YAQSXLXL) along with a downloadable PDF and a public verification link. The certificate is timestamped and linked to the audio fingerprint.
1 credit = 1 certificate. Credits never expire.
Share & Verify
Share the verification link with distributors, labels, collaborators, or platforms. Anyone with the link can verify the certificate exists, check the fingerprint, and see when the declaration was made.
No account needed to verify. The link is publicly accessible.
See It In Action
From upload to timestamped certificate in minutes
Upload & Process
Drag and drop your audio files for instant fingerprinting
Certificate Generated
SHA-256 fingerprint, timestamp, and verification link
The Trust Layer
Every feature is designed around one principle: make falsification significantly harder and leave clear inconsistencies if attempted.
SHA-256 Fingerprinting
Cryptographic hashing generates a unique fingerprint for each audio file. Any change to the file produces a completely different hash.
Server-Side Timestamps
Every certificate is timestamped at creation by the server. Timestamps are part of the auditable record.
Row-Level Security
Data is stored with database-level row security. Only authenticated workspace members can access their own records.
Claims & Disputes
If someone else uploads matching audio, both parties are notified and can file formal claims through the system.
What a Certificate Documents
It confirms
- A record with this certificate exists in the registry
- The SHA-256 fingerprint matches the original submission
- The record was created at the timestamp shown
- The declarant made the declarations shown
It does NOT confirm
- Ownership, copyright, or IP rights of any kind
- Licensing status or distribution rights
- Accuracy of the declarations made
- Endorsement or approval by Audiverify
Ready to get started?
Create your first certificate in about a minute.