The Waterfall Release Strategy, Explained

What is the waterfall release strategy?

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.

How does ISRC reuse work in a waterfall?

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. The shared code, identical audio, and matching metadata give services the strongest available signals that both deliveries contain the same recording. They may preserve play counts and playlist links, but the distributor and stores do not guarantee that outcome.

A new ISRC tells the service it is a different recording. That weakens the chance of linking the album track to the earlier single and creates a duplicate identifier for unchanged audio. Preserve the recording code, but treat catalogue linking as something to verify after delivery.

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 does a waterfall give 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.

What are the pros and cons of a waterfall release?

The waterfall is a useful campaign structure. It also has real limits worth knowing before you commit to it.

What doesn't a waterfall release 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 and multiple pitch shots. Matching identifiers can also help stores recognize the same recordings across releases. Just don’t plan it expecting guaranteed catalogue linking or extra algorithmic reach for tracks that are already months old.

How do you link pre-release singles to the final album?

Upload the final album as a separate release. For every unchanged single, enter the original ISRC, use the identical audio file, and match the track title and artist metadata. Give each genuinely new recording a new ISRC. The album receives its own release-level UPC because it is a separate release.

DistroKid says this setup may help preserve play counts and playlists on some services, but DistroKid and the services can’t guarantee it. Keep the single live while the album delivery is checked, then decide with your distributor whether to leave both releases available or remove the standalone single.

How do you 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 →

Where does this waterfall workflow come from?