Playlist Finder · Research guide
How Playlist Finder ranks song matches
Understand the five matching signals, missing-data behavior, and the difference between song fit and playlist quality.
Song fit is a research ranking
Playlist Finder compares your selected genres, locally analyzed audio, and optional similar artists with the playlist catalog. The fit score ranks candidates for closer inspection. It is not a probability of placement, a forecast of streams, or a certification of a playlist’s listeners.
Scores run from 1 to 99. A higher number means a stronger match under the current inputs and available data. Changing genres or similar artists can change the order. Listen to the playlist and check its published submission rules before pitching.
Five signals contribute to the score
Genre contributes 40%: overlap with your selected genres, with less common catalog genres carrying more weight. Audio contributes 25%: locally derived song features compared with the playlist’s captured track distributions. Similar artists contribute 20%: artist discovery and adjacency evidence in the catalog. Playlist quality contributes 10%: the stored playlist score. Reachability contributes 5%: available contact evidence, with a missing-contact flag reducing that signal.
These weights describe the matching system, not a promise about audience size. Follower count breaks ties after the fit score; it is not an extra fit component. The catalog updates, so the same inputs can produce different candidates over time.
Missing audio data changes the calculation
Audio contributes only when enough comparable playlist metrics are available. When it is missing, the remaining signals are rescaled from their combined 75% weight to 100%. A result without audio comparison should not be read as evidence that its sound has been measured as a match.
For a worked example, assume genre overlap is 0.8, audio similarity 0.6, artist evidence 0.5, stored quality 0.7, and reachability 1.0. The weighted total is 0.69, displayed as a fit score of 69. Without audio, the same other signals produce 0.54 ÷ 0.75 = 0.72, displayed as 72. This is an illustrative calculation, not a real playlist or campaign result.
Playlist quality is separate from song fit
The playlist score is a stored catalog field used as one input to matching. It is distinct from the song’s fit score. A strong playlist score does not establish that the playlist suits your music, and a strong fit score does not prove the authenticity of its streams.
Follower history, track ages, recent activity, and verification dates provide context for your own review. Missing history or older readings limit what can be inferred. Artist audience information is not the playlist’s active-listener count. The stored quality score is a catalog research signal, not an independent fraud audit. Its underlying calculation is not explained by the song-fit weights above.
Audio analysis stays on your device
Your browser analyzes the audio locally. The audio file is not uploaded for matching. Derived numeric features and your confirmed selections are used to find candidates; they do not include a copy of the recording.
Audio features are estimates. They do not identify the rights holder, guarantee genre accuracy, or replace your judgment about the song. Review the suggested genres before matching and use the quality checklist to inspect the results.
Further reading: How to check playlist quality.