Own & train · Preview
Music similarity search: see where two songs match, layer by layer
Compare a pair of songs, screen a release against a catalog, or sweep two catalogs. Trace scores each layer and lets you play the passages that match.
1,000 free tokens to start · No card needed · Cancel paid plans anytime
What you get
Catch what a fingerprint misses
Trace measures how similar songs are, so it can surface a cover, a reused melody or a sampled part, not only the same recording.
See where they match
Each layer, from the full mix and stems to sections, melody and lyrics, gets its own score, with the passages that line up.
Evidence you can keep
Play the matching passages, explore the 3D similarity space and save a PDF report of what matched, where and how closely.
Who it's for
Labels and publishers
Screen new signings and releases against your catalog, layer by layer, before they go out.
Music platforms and distributors
Check incoming tracks against a catalog in the Trace panel, or from your own systems through the Soundverse Enterprise API.
Rights and catalog teams
Get matched passages you can play back and a PDF report, as evidence for your own review rather than a legal finding.
Producers and songwriters
Check how close a new track sits to the reference you worked from, before you release it.
When to use it
- A new release sounds like a song in your catalog
- You suspect a cover, possibly sung in another language
- You need to show which part of two songs matches, not just that they do
- You're about to sign or acquire a catalog and want to check it against yours
- A vocal in someone else's track sounds like your recording
- Before release, you want to check your track against its references
What you can make with it
A pre-release catalog screen
Add your catalog to a dataset once, then run a 1 : N search on each new release before it goes out.
A cover check across languages
Cover detection compares melody, sections, stems, lyrics and lyrics translated to English, so a cover in another language can still surface.
A reused vocal recording
Voice timbre compares the full mix, stems and style tags; a high vocal-stem score points to the same recording, not a new performance.
Lifted or replayed material
Sample search compares sections, melodic phrases and stems to find a part taken from, or replayed from, another song.
A remix or re-arrangement
Remix / re-arrangement looks for reused stems and hooks across sections, phrases and lyrics.
Near-duplicate lyrics
Lyrics identity checks transcribed lyrics, translations included, for verbatim and near-duplicate lines.
Stylistic neighbors
Genre / stylistic proximity compares overall sound, instruments and style tags to find a song's closest neighbors in a dataset.
Catalog against catalog
Run M : N to sweep one dataset against another, such as your catalog against one you're about to acquire.
A PDF for the file
Export a result as a PDF in your Library and keep it with your notes on the case.
Searches from your own software
Create datasets, add songs and run searches through Trace's endpoints on the Soundverse Enterprise API.
Trace is Soundverse's music similarity search: it measures how similar songs are, and in what way, by comparing them on separate layers, from the full mix and individual stems to sections, melody, lyrics and style. Where audio fingerprinting only asks whether two files are the same recording, Trace can surface a lifted melody, a reused vocal recording or a borrowed drum groove. It's built for labels, publishers, platforms and creators who need evidence of where music comes from.
See it in action
- Soundverse Trace: Music Similarity at Track, Stem, Section and Lyric Level Three Trace searches, 1-to-1, 1-to-N and N-to-M, compared at track, stem, section and lyric level, then a walk through the final report.
- Every AI Tool in “Own”: Trace, Copyright Check, Watermarks, Moderation and Licensing | Soundverse AI From 0:12. The Trace part of Soundverse's Own walkthrough, from input to result.
How it works
Build a dataset
Add songs from your Library, audio files, a folder or a direct link, and Trace analyzes each one once so you can search it again and again. A one-to-one check needs no dataset.
Pick a search type
Choose 1 : 1 to compare two songs, 1 : N to screen one song against a dataset, or M : N to compare every song in one dataset with every song in another.
Choose a use case
Pick a ready-made check such as Cover detection, Melody similarity, Sample search or Voice timbre, or choose Custom and switch layers on yourself.
Run it and read the evidence
Click Run Search in Chat. Trace scores each layer, shows which moments of the two songs line up, and can turn the result into a PDF report saved to your Library.
Why use Trace
More than a fingerprint
A fingerprint asks whether two files are the same recording. Trace measures how similar two songs are, so it can surface a cover, a reused melody or a sampled part.
A score for every layer
Each layer you compare, from the full mix and four stems to sections, lyrics and style tags, gets its own score, and melody matches are counted phrase by phrase, so you see where the similarity sits.
From one pair to catalogs
Triage a single pair, screen a new release against your catalog, or sweep one catalog against another, with the same layers each time.
Evidence you can hear
Play the exact passages that matched, explore the result as a 3D similarity space, and keep a PDF report of what matched, where and how closely.
What it costs
In preview: in the app, only the Soundverse team can run Trace for now, and it isn't on any plan yet.
Businesses can use Trace now through the Soundverse Enterprise API. It's billed per job by the songs searched and the layers compared, with a $0.03 minimum per search.
In the app, a search is quoted in tokens before it runs, by the songs' length, the layers compared and the number of comparisons, with a 36-token minimum.
Soundverse plans start at $9.99 a month billed yearly, or ₹399 in India.
Prices outside India are in US dollars, billed through Stripe; in India they are in rupees, billed through PayU. Monthly tokens reset each month and don't roll over.
Frequently asked questions
Is Trace free?
No. Each Trace search uses tokens, priced by the work it does: the songs' length, the layers you compare and the number of comparisons, with a minimum of 36 tokens. The Trace panel shows the quote before you run a search and holds that amount, and if the search costs less, the difference is returned. Adding songs to a dataset is priced by their length in the same way.
Is a Trace result proof of copyright infringement?
No. Trace scores are similarity measurements, not legal or copyright determinations. A high score on the vocal stem means the same vocal recording was reused, not that the same singer sang something new, and melody matches are counted as phrases rather than given a percentage. Treat a Trace result as evidence to review alongside your own records and legal advice.
How is Trace different from Copyright Checker?
Copyright Checker identifies a recording by its acoustic fingerprint and tells you whether it matches a known, commercially released track. Trace answers a different question: how similar two songs are, and on which layer. That lets Trace surface a cover, a reused melody or a sampled part that a fingerprint would miss, but it compares against the songs and datasets you choose.
What is Trace, Soundverse's music similarity search?
Trace is Soundverse's music similarity search: it measures how similar two songs are, and on which layer, by comparing the full mix, stems, sections, melody, lyrics and style separately. On Soundverse, Trace returns a result for each layer with the evidence behind it, whether you check one pair of songs, one song against a catalog, or one catalog against another.
How do I check if two songs are similar?
Run a 1 : 1 search in Trace: pick the song you're checking and the song to compare it with, then choose a use case such as Cover detection or Melody similarity, or set the layers yourself. Trace scores each layer and shows which moments of the two songs line up. A one-to-one search needs no dataset, though over many layers it takes longer because both songs are analyzed on the spot.
What can Trace compare?
Trace compares songs on separate layers: the full mix, vocals against accompaniment, four stems (vocals, bass, drums and other instruments), song sections, melodic phrases, transcribed lyrics, lyrics translated to English, and genre and style tags. In 1 : N and M : N searches, the melody layer can also find a phrase moved to another key, and translated lyrics suit covers sung in another language.
What audio can I add to Trace?
In the Trace panel, you can add WAV, MP3, FLAC or M4A files, a whole folder of them, a direct link to an audio file (not a YouTube link), or songs already in your Soundverse Library. The lyric and translation layers need vocals, so they don't apply to instrumental tracks. You need the rights to anything you upload.
How long does a Trace search take?
Most Trace searches finish within seconds to a few minutes. A one-to-one search over many layers takes longest, because both songs are analyzed on the spot, while songs in a dataset were analyzed once when you added them and are only compared, on the layers they were analyzed for. Searches run in the background, and the result appears in the chat when it's ready.
Can I use Trace through the Soundverse API?
Yes. Trace has its own endpoints on the Soundverse Enterprise API for datasets, ingestion, custom and comprehensive searches, eight ready-made use cases and job status. Jobs run in the background and are billed per job by usage when they finish, based on the songs' length, the layers and the number of comparisons. Failed jobs aren't charged, and uploads and status checks are free.
See how close two songs really are
Compare a track with another song or a whole catalog, layer by layer, with the evidence behind every score.
