Editorial
A waterfall release, or separate singles
When each new single should carry the previous ones with it — and when it is metadata work for nothing.
There are two ways to put out five songs. One is as separate singles, each with its own date. The other is a waterfall: every new single is released as a record that also contains all the previous tracks, and the last one becomes the full EP.
The difference is not cosmetic. It decides where each new listener lands and what they see first.
How a waterfall works
- Release 1: track A.
- Release 2: tracks A + B, where B is new.
- Release 3: tracks A + B + C.
- Final release: all five, as an EP.
Each time you deliver a new release with a new date, but the older recordings travel with it. Same ISRCs, same masters — what changes is the release's UPC and the cover.
What it gives you
Streams gather in one place. With separate singles, someone who finds your third track sees three separate cards on your profile. In a waterfall they open one release and see everything you have made in six months.
Old tracks get fresh plays. Popularity counts recency, not the archive. When track A travels with release 3, it re-enters Release Radar and collects recent plays all over again.
The final EP does not start from zero. By EP day most of its tracks already have a history of saves and skips. That is the case where the algorithm has something to work with from the first hour.
When a waterfall is the wrong shape
When you have two tracks. The mechanic earns its keep from three or four; below that it is metadata work for nothing.
When the songs do not hold together. A waterfall ends in an EP. If five tracks do not read as one record, you have glued unrelated recordings together, and it shows.
When the gaps run past two months. The effect lives on density — three to four weeks between parts. Stretch it over half a year and nobody connects the parts.
When you pitch editorial with every part. An editor can see that two of the three tracks have been out before. The focus track has to be the new one, and the pitch has to say so.
Check before you start
- That your distributor allows an ISRC to be reused. This is the condition the whole thing rests on: track A must carry the same code in every release, or you create duplicates instead of accumulation.
- Covers. Each part needs its own. The same image on four releases looks like a failed upload.
- A calendar for every part up front. Waterfalls fall apart when part three slips by a month.
- Track order. The new track goes first, not last. People open a release from the top.
An honest assessment
A waterfall does not bring new listeners by itself. It works on the ones who already arrived: it holds them better, keeps the catalogue recent for longer, and gives the final release a better start.
With zero listeners, a waterfall from zero does nothing. With even a small audience that comes back, it is one of the few free ways to get more out of the same songs.