Attribution infrastructure · beta

Attribution that
follows the audio,
not the file.

Wav Linq embeds an invisible watermark into every track. Wherever the audio ends up — compressed, re-uploaded, sampled — the ownership proof travels with it.

Start watermarking Create account
attribution log
A1B2C3D4E5F6 soundcloud · detected live
F9E8D7C6B5A4 tiktok · mp3 reupload direct
3C2B1A0F9E8D instagram · survived compression cache
____________ waiting
The approach

Protection fails.
Attribution scales.

DRM and takedowns are reactive. By the time you act, the audio has already moved. Wav Linq takes the opposite position — make ownership provable everywhere the audio lands, and let that proof work automatically.

ID3 tags are stripped in seconds. Platform metadata disappears on re-upload. The watermark in the signal doesn't.

Attribution lives in the file's metadata Attribution lives in the signal itself
Ownership proof depends on the platform Ownership proof travels with the audio
Compression and re-encoding breaks attribution Survives MP3, re-encoding, pitch shifts

Built for how audio actually moves.

Every piece is designed around the real lifecycle of a track — from DAW bounce to viral re-upload to royalty dispute.

01 Frequency-domain watermarking Embedded in the audio signal, not the wrapper. Invisible to listeners. Survives the full standard attack surface — MP3, AAC, re-sampling, pitch shift.
02 Composite signature system Every Linq carries both creator identity and track identity. Degrades gracefully — creator attribution survives even if song-level data is partially corrupted.
03 Federated partner API Platforms integrate via API. Federated embed means your metadata stays in your database — Wav Linq stores only a resolver pointer, nothing about your catalog.
04 Async detection jobs Submit audio, get a job ID, poll for results. Built for integration — not just a web UI. Rate-limited, idempotency-keyed, auth-gated.
05 Attribution dashboard Every detection logged. See which tracks are moving, on what platforms, and how often. Real signal, not vanity metrics.
How it works
01

Upload your track

Drop a WAV into Wav Linq. The system analyzes the audio's characteristics to determine optimal embedding parameters for that specific file.

WAV · beta — more formats soon
02

A Linq is embedded

A unique 20-character composite signature — your Linq ID — is written into the frequency domain. Inaudible. Not in the metadata.

03

Distribute freely

Share everywhere. The attribution travels with the audio regardless of what happens to the file — re-encoding, compression, format conversion.

04

Attribution is proven

Anyone running detection gets your identity back. The result includes the creator, the track, and where the attribution data came from.

Your work.
Your credit.

Free to start. No credit card.

Create account Partner API →