Release Radar updates on Fridays and sends one new song per artist to each of its followers. If you pitch at least 7 days before release, the pitched track is the one followers receive. There’s no official minimum stream count, but strong early engagement (streams + saves) raises the odds of a broader algorithmic bump.

“Release Radar is a playlist of new releases that updates every Friday.” — Spotify for Artists.

“If you pitch at least 7 days before release, we’ll add the song to your followers’ Release Radar playlists.” — Spotify Support.

TL;DR

• Pitch ≥7 days ahead to control which track reaches followers’ Release Radar.
• Deliver 7–14 days early with final metadata; avoid last‑minute changes.
• Personalized rules: one song per artist per listener, up to 4 weeks if the song is not already in the listener’s library.
• No official thresholds. A helpful heuristic is ~2,500 streams + ~250 saves in 1–3 weeks for a broader push (directional, not guaranteed).
• Be main/featured (remixer‑only often excluded); use a new ISRC for materially new versions.

What Release Radar is (and what isn’t)

Release Radar is a personalized, weekly playlist of new releases tailored to each listener. Listeners get new music from artists they follow, listen to, and from others Spotify thinks they’ll like. Each listener receives one song per artist per week for up to 4 weeks if they haven’t heard it yet.

Pitching vs Release Radar 

• Do you need to pitch? No—followers can still get a song from your new release. But it is recommended.
• What does pitching do? If you pitch ≥7 days before release, the pitched song is the one sent to your followers’ Release Radar (control matters for multi‑track releases).
• What pitching doesn’t do: It doesn’t guarantee editorial or non‑follower reach.

“Submitting a pitch at least 7 days before release day will get your song on your followers’ Release Radar playlists.” — Spotify Support.

60‑Second Diagnostic (start here)

• Delivered 7–14 days early? Release date/time locked?
• Pitched ≥7 days, so you control which track hits followers?
• You are the primary or featured artist (not just a remixer)?
• New ISRC for materially new versions (not a straight re‑upload)?
• Are your territories and time zones aligned with your audience?
• Still within the ~4‑week “newness” window for each listener?
• Correct artist URI mapping (no duplicates)?
• Followers warmed up recently (listened to or saved in the past 1–2 weeks)?

9 Reasons You’re Missing Release Radar — and the Fix

1) Delivery was too tight

Symptom: Track didn’t show on the first Friday; it shows a week later or not at all.
Fix: Deliver 7–14 days ahead; lock metadata; avoid final‑week changes; set a precise global release time.

2) No (or late) pitch on a multi‑track release

Symptom: The “wrong” song hit followers.
Fix: Pitch one song ≥7 days before release so that the track goes to followers’ Release Radar.

3) Wrong artist mapping or duplicate profiles

Symptom: Release mapped to a look‑alike profile; your followers didn’t get it.
Fix: Verify your artist URI pre‑delivery; have your distributor request merges/splits.

4) Duplicate ISRC or “not‑new” re‑release

Symptom: Re‑uploads with the same ISRC aren’t treated as new.
Fix: Assign a new ISRC for materially changed versions (new mix/edit, radio edit, etc.).

“Any new or materially changed recording must be provided with a new ISRC.” — IFPI

5) Role/credit issues (remixer‑only or contributor)

Symptom: You’re credited only as remixer.
Fix: Ensure main or featured artist credit where appropriate; remixer‑only credits are often excluded from followers’ RR.

6) Territory restrictions/time-zone mismatch

Symptom: Fans in key countries didn’t see it at release.
Fix: Align territories and release time with your audience; avoid staggered availability for core markets.

7) The track aged out of the listener’s “new” window

Symptom: It appeared briefly, then vanished.
Fix: Stack content and collabs during the first 2–3 weeks while “newness” applies.

8) Personalized filtering + dormant followers

Symptom: Inactive followers don’t always get every drop.
Fix: Warm up 7–10 days pre‑release; drive pre-saves, saves, and completed plays; encourage repeat listens.

9) Over‑frequent releases dilute early engagement

Symptom: Weekly drops with falling save rate and rising skips.
Fix: Move to a 4–6 week cadence with quality gates; use a waterfall plan.

Minimums & metrics 

• Officially: Spotify doesn’t publish a stream minimum; followers get a song from your new release (subject to eligibility like role, newness, mapping).
• Helpful heuristic (Andrew Southworth, 2024): “About 2,500 streams with at least 250 saves in the first 1–3 weeks” often coincides with a broader algorithmic push from Release Radar. Use this as directional guidance, not a rule; quality of engagement matters.

Quality signals to watch: save rate (aim 8–12%+), low early skips, repeat listens, and engaged traffic from socials/ads.

How to check Release Radar traffic

In Spotify for Artists → Music → Songs → Playlists / Source of streams, look for Release Radar in the breakdown. (Stats are in UTC.)

Mini‑examples (realistic scenarios)

Collab credit misfire
Two artists (~3,200 followers each) release a duet but credit one as featuring only. Only the lead’s base reliably gets RR. Next collab: both credited as main artists → RR shows across both bases; week‑one saves rise from 6.4% → 9.1%.

Late delivery = delayed RR
An indie with 2,500 followers delivers a single 24 hours before release. Most followers don’t see it until the next Friday. After moving to 10‑day lead times, the next single’s early‑week streams recover and RR lands in week one.

FAQ

Do I need to pitch to appear on Release Radar?
No. Followers can still get a song from your new release. Pitching ≥7 days ahead ensures your chosen track reaches them.

Is there a stream minimum to “trigger” Release Radar?
No official minimum. A common heuristic is ~2,500 streams + ~250 saves in 1–3 weeks for a broader push—no guarantees.

How long can a song appear in Release Radar?
Each listener can get one song per artist per week, for up to 4 weeks if they haven’t listened yet.

Do re‑releases or remixes count as “new”?
Re‑releases are typically excluded; some alternates may be excluded. Remixes can be included, but remixer‑only roles don’t count for your followers’ RR.

Where do I see RR traffic?
In Spotify for Artists → Music → Songs → Playlists / Source of streams (note: stats are UTC).

References

• Spotify Support — Getting music on Release Radar. (Friday updates; one song per artist per listener; exclusions; delivery guidance; four‑week window.) https://support.spotify.com/us/artists/article/getting-music-on-release-radar/
• Spotify Support — Pitching music to Spotify playlist editors. (“If you pitch at least 7 days before release, we’ll add the song to your followers’ Release Radar playlists.”) https://support.spotify.com/us/artists/article/pitching-music-to-playlist-editors/
• Spotify Support — Source of streams. (Where to see Release Radar and other sources; stats in UTC.) https://support.spotify.com/us/artists/article/source-of-streams/
• Spotify for Artists (Blog) — Preparing for Release Day and Beyond (Aug 20, 2024). (“Pitching your song two weeks in advance also ensures it will make it onto your followers’ Release Radar playlist.”) https://artists.spotify.com/en/blog/release-guide-preparing-for-release-day
• IFPI — When to assign (ISRC). (“Any new or materially changed recording must be provided with a new ISRC.”) https://isrc.ifpi.org/en/using-isrc/when-to-assign
• Andrew Southworth — What is Spotify Release Radar? (Heuristic: ~2,500 streams + ~250 saves in 1–3 weeks.) https://andrewsouthworth.com/what-is-spotify-release-radar/

Post Summary — Core Ideas

• Pitch ≥7 days ahead to control which track hits followers’ Release Radar.
• Deliver 7–14 days early with final metadata; avoid re‑releases and remixer‑only credits.
• Release Radar is updated on Fridays, personalized, with one song per artist per listener, and up to 4 weeks if unheard.
• There’s no official stream minimum; use ~2.5k streams + ~250 saves (1–3 weeks) as a heuristic, not a promise.
• Protect early engagement (saves, completion, low skips) with a sensible **4–