Have you ever wondered why SoundCloud monetization doesn’t always match how you report the rest of your catalog?

For many major DSPs, distributors are used to thinking about royalties through a pro-rata framework: revenue flows into a pool, that pool is allocated based on a service-wide share of streams, and payout is closely tied to volume. That framework is familiar across platforms such as Spotify, Apple Music and Amazon Music. However, it changes the moment the catalog enters SoundCloud. 

SoundCloud runs on Fan-Powered Royalties, a user-centric model that pays out based on what each individual listener actually does with each artist, not on aggregate stream count across the platform. A distributor reading SoundCloud payouts through pro-rata expectations will see monthly payouts that don’t track stream volume, and will have no coherent way to explain that variation to a label asking why a track with more plays earned less than one with fewer.

This stopped being a rounding error in November 2025, when SoundCloud eliminated the 20% revenue share it had been taking on distribution earnings. Artists and labels distributing through SoundCloud now keep the full royalty amount the platform pays out on their behalf. That change alone shifts the economics of treating SoundCloud as a real revenue channel rather than a secondary discovery platform, and it raises the operational stakes of understanding exactly how that revenue gets calculated in the first place. A distributor who doesn’t understand the mechanism isn’t just missing context. They’re mismodeling a channel whose payout logic has just become more consequential to get right. 

How SoundCloud Monetization Works Under Fan-Powered Royalties

What counts as engagement

SoundCloud's own documentation is specific about what feeds the calculation. Fan-Powered Royalties are driven by three factors:

1. How much of a fan's total monthly listening time goes to a given artist relative to everything else that fan listens to.
2. How many ads that fan has consumed.
3. And whether that fan holds a paying SoundCloud Go+ subscription. 

Repeat listens, longer sessions, likes and reposts are not inputs to that formula. They are the behaviors that increase an artist's share of a fan's listening time, which is the variable that actually determines payout.

That distinction matters because not all listening contributes equally to an artist's share of a fan's monthly revenue allocation. A fan who spends a significant proportion of their listening time with one artist can therefore generate a different royalty outcome from a fan who listens more broadly across the platform, even if both generate a similar number of plays. The key variable is not simply how many times a track was played, but how much of that listener's overall SoundCloud listening was attributed to the artist.

This is the mechanism labels and artists need distributors to understand and explain. A catalog with a smaller but highly engaged fanbase can therefore produce a different royalty outcome from one with higher raw stream counts but less retained listening.

Why the same stream count can produce different payout figures month to month

Once payout is a function of listening-time share rather than volume, stream count stops being a reliable predictor of revenue on its own. Two months with identical total streams can produce different payout totals if a fan's share of listening time shifts between them, if a fan's ad-supported sessions give way to unmonetized ones, or if a fan's Go+ subscription lapses or activates.

This is not a reporting inconsistency. It is the model working as designed. But it can look inconsistent to anyone reading a royalty statement with pro-rata expectations, particularly when stream counts remain stable while payouts change. The answer cannot be explained by stream count alone. Listening-time share and the underlying mix of monetized listening are key factors in understanding why the payout changes, even when the number of plays appears similar. And because most catalog reporting does not currently surface these underlying variables, distributors need to understand the model behind the number in order to explain the difference with confidence.

What this means for anyone managing third-party catalog

For a distributor reporting to labels, this changes what needs to be modeled and what needs to be monitored. SoundCloud revenue should not be forecast the way Spotify or Apple Music revenue is forecast, because the input variable is different. Volume growth on SoundCloud does not translate one-to-one into revenue growth in the way distributors may expect from a pooled model. Instead, changes in listening-time share and the underlying mix of monetized listening play a central role in determining revenue. 

This is not a niche mechanic confined to independent artists managing their own uploads. Warner Music Group formally adopted the Fan-Powered Royalties model for its roster, a signal that a major label concluded the engagement-based approach produces outcomes worth building into its own royalty operations at scale. A distributor treating this as a marginal or experimental payout structure is behind where the major label side of the industry has already moved.

The practical shift is in what a distributor needs to understand, not necessarily what a report currently shows. Instead of judging SoundCloud performance against total stream count, the real signal is listening-time share and the underlying mix between ad supported and subscription listening within that fanbase. Most royalty reporting today, across the industry, doesn't break this out. A distributor who can still explain to a label that a payout dip corresponds to a drop in retained listening time, rather than a data or reporting failure, converts a credibility risk into a demonstration of operational sophistication.

The real complexity isn't SoundCloud, it's reading every DSP through the same lens

SoundCloud's model is not, on its own, complicated. What creates operational risk is running it alongside pooled-royalty DSPs inside a single reporting pipeline built around one set of assumptions. A catalog spanning Spotify, Apple Music, Amazon Music and SoundCloud is a catalog spanning at least two structurally different royalty logics, and treating them identically means misreading what's actually driving revenue on at least one of them every month.

This is precisely the kind of structural complexity that infrastructure exists to absorb rather than pass on to the label relationship. SonoSuite standardizes royalty reporting across DSPs, taking the raw, DSP-specific report formats and turning them into a single consistent reporting output for the distributor. That removes the operational burden of manually interpreting a different format for every DSP a catalog is live on, including one, like SoundCloud, whose underlying payout mechanic doesn't resemble the rest. This gives distributors a consistent reporting layer across DSPs, while preserving the underlying differences in how each platform reports revenue.

The distributors who will handle SoundCloud correctly over the next few years are not the ones who learn the Fan-Powered Royalties formula. They are the ones whose infrastructure already accounts for the fact that a royalty report doesn't arrive in the same shape twice across their catalog, and that explaining the number still requires understanding the model behind it. If that standardization isn't built into the reporting layer today, every DSP with a non-standard payout model is a future conversation with a label that starts from a position of having to explain rather than having already anticipated.

For distributors, the takeaway is broader than SoundCloud. As DSPs continue to evolve their monetization and royalty models, reporting infrastructure needs to do more than standardize formats. It needs to account for the logic behind the numbers, so distributors can reconcile revenue accurately and explain it with confidence.

Want to see how your royalty reporting handles different DSP models? Talk to our team.