The Waterfall Release Strategy, Explained
The waterfall release strategy sequences singles one at a time so that each new release bundles the previous tracks alongside it, building toward an EP. Reusing the same ISRC for already-released songs carries their streams over instead of resetting. You get multiple Release Radar and pitch shots for a single project. The catch: only the newest track is new.
new track per waterfall release (only the newest track is new to Release Radar)
reuse the same ISRC on already-released tracks so streams carry over
typical waterfall before compiling to an EP or album
recommended gap between each waterfall release for Release Radar rotation
Key takeaways
- The waterfall sequences singles that build on each other: release A, then B+A, then C+B+A, compiling to an EP or album.
- Reusing the same ISRC for already-released tracks carries their streams over to the new release rather than resetting the count.
- Each waterfall release is a separate editorial pitch shot and a separate Release Radar push for the new track.
- The waterfall organizes a campaign and earns repeated pitch shots. Old tracks keep their existing streams while only the new track is featured in Release Radar.
- Not every distributor supports this workflow the same way. Check your distributor’s process before planning a waterfall campaign.
What the waterfall release strategy is
The waterfall is a sequencing tactic that’s been part of independent release strategy for several years. The basic shape is simple. You release a single. A few weeks later you release another single, but this time the release also includes the first single. A few weeks after that, a third single drops, bundled with the first two. Eventually you have a complete EP or album that’s been building in public the whole time.
A concrete example: you’re building toward a 4-track EP. You release single A. Four to six weeks later you release a 2-track release containing B and A. Four to six weeks after that, a 3-track release: C, B, A. Then the full EP with D added. That’s the waterfall. The project that started as one song accumulates tracks each time, and by the time the EP is “out” it’s been in listeners’ playlists for months.
This is a real tactic used by working independent artists, not a hack. It’s part of thinking about your release strategy as a campaign that unfolds over several releases.
The mechanic that makes it work: ISRC reuse
This is the detail that separates a waterfall from just releasing multiple versions of the same music. When you include an already-released track in a new release, you use the same ISRC that the original single carried. The ISRC is the identifier attached to that specific recording. Because it’s the same ISRC, the streams from the original release and any playlist placements carry over to the new release rather than starting at zero.
Without ISRC reuse, each bundle would treat the previously released song as a new recording and reset its stream count. That defeats the whole point. The growing release page works because the older tracks bring their history with them.
The new release date applies to the new track only
When you release a 2-track bundle (new single + the original single), the release date for the new track is the date you’re releasing. The original track keeps its original release date via the same ISRC. What’s new is only the new song.
For more on ISRCs and how they work across releases and distributors, the what is an ISRC code guide covers the full picture. If you’re switching distributors mid-waterfall, see switching music distributors for how ISRC carry-over works in that context.
What the waterfall gives you on Release Radar
Each waterfall release gives you one Release Radar push: for the new track. That’s the real pitch shot in the waterfall. The already-released tracks riding along in the bundle don’t get re-featured in Release Radar. They’re there for context, for discoverability on the release page, and for streams to continue accumulating. They’re not new, and the algorithm doesn’t treat them as new.
So a 4-track waterfall campaign gives you 4 Release Radar moments and 4 editorial pitch shots for 4 different new tracks over 3 to 4 months. Compare that to releasing the EP all at once, which gives you one Release Radar moment and one pitch shot for one focus track. That’s the real advantage of the waterfall, and it’s a meaningful one.
A 4-track waterfall gets you 4 Release Radar shots. The same 4 tracks dropped as an EP gets you one.
Waterfall pros and cons, side by side
The waterfall is a useful campaign structure. It also has real limits worth knowing before you commit to it.
| Advantages | Limitations | |
|---|---|---|
| Release Radar reach | Each single earns its own Release Radar push for the new track. | Already-released tracks don’t get new Release Radar exposure in the bundle. |
| Editorial pitching | Each new single is a separate pitch opportunity with Spotify editors. | Each pitch covers only the one new song, never the project as a whole. |
| Stream accumulation | Streams from individual singles carry over to the EP via ISRC reuse, so the full release lands with history behind it. | Requires careful ISRC management and distributor support; not every distributor handles it the same way. |
| Listener experience | Fans who followed the singles feel the EP as a culmination rather than a surprise. | Listeners who see the growing tracklist may find it confusing if they don’t follow your releases closely. |
| Campaign calendar | Built-in release schedule with a built-in story: the project building over time. | Requires planning across 3 to 5 months; a gap or misstep in the middle disrupts the arc. |
What the waterfall doesn’t do
Some guidance on the waterfall oversells it, so it’s worth being direct about the limits. The waterfall doesn’t trick the algorithm into treating old tracks as new. Release Radar features the new track in each release. Discover Weekly and other personalized playlists work off listener behavior and engagement on the recordings, not off what release they appear on. Putting track A on three different releases doesn’t re-surface track A to listeners who’ve already heard it.
The waterfall is genuinely useful for what it does: giving you a structured campaign calendar, multiple pitch shots, and streams that compound onto a release page over time. That’s a real advantage over releasing an EP all at once. Just don’t plan it expecting extra algorithmic reach for tracks that are already months old.
Check your distributor before you start
ISRC reuse and multi-track bundling in a waterfall has to be set up correctly through your distributor. Some handle it cleanly, some require specific steps, and some have limitations. If you start a waterfall campaign without checking, you can end up with the wrong ISRCs on the bundle releases and lose the stream carry-over you were counting on. Do this step first.
How to run a waterfall campaign
The setup is straightforward once you know what you’re doing. Start with the songs you’re building toward. Decide the order (usually your strongest track first to maximize the first Release Radar push). Set your release dates with 4 to 6 weeks between each drop, so each new single has time to breathe in rotation before the next one lands.
For each release after the first: collect the ISRCs for all previously released tracks. When you deliver the new release to your distributor, use those same ISRCs for the carried-over tracks. The new track gets a new ISRC. Pitch the new track to Spotify editorial at least 7 days before the release date, same as you would for any single. That’s the Release Radar and editorial window. If you miss it, you miss the feature opportunity for that single.
For the full timing breakdown, including the 7-day pitch cutoff and distributor delivery windows, see the music release timeline guide. For more on how this fits into your broader release strategy, see how often to release music.
map your waterfall release dates and pitch windows with the free release timeline builder
Frequently asked questions
Does the waterfall strategy trick the Spotify algorithm?+
No. Only the newest track in each waterfall release is new to Release Radar and to listeners. The already-released tracks aren’t re-featured just because they appear on an updated release. The waterfall organizes a campaign and gives you repeated pitch shots, but it doesn’t give old tracks fresh algorithmic reach. That’s an important distinction, because some guidance oversells what the tactic actually does.
Do all distributors support the waterfall release strategy?+
Not all, and the level of support and the exact workflow varies. Some distributors handle the ISRC reuse and multi-track bundling straightforwardly. Others require specific steps or have limitations around updating an existing release. Check with your distributor before you plan a waterfall campaign so you know what’s possible and how to set it up correctly.
What happens to streams on a waterfall EP after the full release?+
Because you used the same ISRCs throughout, the streams that accumulated on each individual single carry over to the compiled EP. The stream counts don’t reset. This is the main practical advantage of the waterfall: by the time the full EP drops, it already has listening history behind it.
How many singles before the EP in a waterfall?+
Typically 3 to 5 singles, which then compile into a 4-to-6-track EP. A common pattern is 3 singles released over 3 to 4 months, with the full EP following. There’s no fixed number. What matters is that each single has time to breathe in Release Radar rotation before the next one drops, which points back to a 4-to-6-week cadence between releases.
Can you waterfall singles into a full album?+
Yes. The same principle applies: release singles one at a time with ISRC reuse, then compile them with additional tracks into an album. The album can include the singles plus new tracks. The singles’ streams carry over to the album version via the same ISRCs. This is a common pattern for artists building toward an album campaign while maintaining release cadence.
Get better release strategy in your inbox
Release planning checklists, royalty explainers, and artist strategy notes from Velveteen. No daily noise.
Was this useful? Send a signal or flag a correction.
Keep reading
Pillar guide
Music release strategy
The strategic frame: why singles-led release plans suit most independent artists, how format and cadence interact with Spotify's systems and your fans, and when to make an album an event.
Related guide
Singles vs EP vs album
The format decision laid out: what each one costs and signals, how DSPs classify them, and which fits your career stage.
Related guide
How often to release
The cadence question answered honestly: the 4-to-6-week drumbeat, why consistency feeds Release Radar, and why five forgettable singles lose to one that converts.
Related guide
What is an ISRC
What an ISRC code is: the 12-character ID for one recording, why a remix needs a new one, and how to carry it across distributors so you don't split your streams.
Free tool · no signup
Build your release timeline in 30 seconds
Pick a release date and get a dated, backwards-planned checklist — upload, pitch, content, pre-save, and post-release — built around the 7-day Spotify pitch floor.