When Your App Needs Music Licensing and How Much It Costs?

Music has a way of making digital products feel alive. The right track behind a montage feature, a clip of a beloved song attached to a shared memory, background audio in a fitness app, these are not decorations. They change how the product feels and how long people stay. But the moment you introduce real music into an app, you step into a licensing framework that has caught out teams far better resourced than most startups.

Understanding who owns what in music is the foundation of every legal audio integration.

The music rights system was not designed with apps in mind. It was built for radio, then adapted for television, then stretched again for streaming, and every time a new format arrived, the rules got a layer more complex. App teams often discover this after they have already committed to a feature, which is the worst possible moment to find out that the song they planned to use requires three separate licences, two of which belong to different companies in different countries.

This article works through the full picture: which rights you need, who holds them, what it costs to acquire them, and where the practical alternatives sit. Some of this will save you money. Some of it will save you from a legal bill that dwarfs whatever you spent building the feature in the first place.

Why Music Licensing Catches App Teams Off Guard

The assumption many editors make is that paying for a track on a music platform, or finding it on YouTube, means they can use it. It does not. Purchasing a song gives you the right to listen to it. Using it inside a product you distribute to others is a different transaction entirely, governed by a separate set of agreements that most developers have never read.

The other assumption is that small scale means low risk. A beta app with a few hundred users feels very different from a television campaign, but music rights holders do not grade enforcement by audience size. They grade it by whether permission was granted, and no permission means infringement regardless of how many people heard the track.

The Gap Between Awareness and Action

App teams are generally aware that licensing exists. The gap is between knowing it is a thing and understanding what it actually requires. A team building a memory-sharing feature, for example, might plan to let users attach songs to shared moments and assume that because the user owns the music on their streaming service, the app inherits that right. It does not. The user's streaming subscription covers personal listening, not redistribution through a third-party application.

The result is that music features get built, sometimes fully, before anyone has spoken to a music lawyer or looked at what a licence actually costs. By that point, the feature is tied to the product roadmap and the team is under pressure to find a route forward that may not exist at the budget they have left.

The Two Rights You Always Need: Sync and Performance

Every piece of recorded music carries at least two separate layers of ownership. The composition, the melody, the chords, the lyrics, belongs to the songwriter or their publisher. The recording, the specific performance of that composition, belongs to whoever paid to record it, usually a record label. Using a track in an app touches both layers, and each requires its own licence.

Sync Rights

A synchronisation right, commonly called a sync licence, covers attaching a musical composition to a visual or interactive medium. If your app plays music alongside video, images, or user-generated content, you need sync rights from the music publisher. This is a negotiated agreement, and the fee varies enormously based on the track, the usage context, and the distribution scale.

Performance Rights

A performance right covers the public performance or transmission of music. In an app context, streaming a track to users constitutes a public performance even if each user hears it privately on their own device. Performance licences in most markets are administered by collecting societies: PRS for Music in the UK, ASCAP and BMI in the United States, SOCAN in Canada, and so on. Music for Business Finder, 2026 puts ASCAP's minimum annual fee for a small business General licence at around $402, though the figure scales with the size and type of use.

Both licences are non-optional if you are playing real, released music to users. Missing either one does not halve the risk, it leaves you fully exposed on whichever right you skipped.

Mechanical Rights and When They Apply

A third right enters the picture when your app allows music to be reproduced, not just streamed. Mechanical rights cover the copying or reproduction of a musical composition, and they originated in an era when "mechanical" referred to player pianos reproducing sheet music through a roll. The name has stuck, and the right now applies to digital downloads, offline caching, and any feature that stores a copy of music on a user's device.

If your app caches or downloads tracks for offline use, mechanical rights apply on top of sync and performance.

If your app streams music purely in real time with no local storage, mechanical rights are unlikely to apply to your situation. But if you build an offline listening feature, allow users to save clips, or cache tracks to improve performance on poor connections, you are reproducing the composition and you need a mechanical licence to do it legally.

Who Issues Mechanical Licences

In the UK, mechanical rights are administered by MCPS, which operates alongside PRS for Music. In the US, the Mechanical Licensing Collective handles mechanical licensing for digital services under the Music Modernization Act. The process of obtaining these licences varies by territory, and the rates are typically set by statute or tribunal rather than freely negotiated, which at least gives you a clearer starting point for budgeting.

The important thing to understand is that mechanical rights sit entirely separately from sync and performance rights. Paying a sync fee to a publisher does not cover reproduction, and a performance licence from a collecting society does not cover it either. Each right requires its own agreement.

Who Actually Owns the Music You Want to Use

Before you can licence a track, you need to know who holds which rights, and this is often more complicated than it looks. A single popular song can involve a songwriter, a co-writer, a publisher who administers the composition, a record label that owns the master recording, and a distributor that controls how the master is made available commercially. Each party holds a different piece of the puzzle.

For most mainstream music, the master recording is owned by a major or independent record label. The composition rights sit with a music publisher, which may or may not be the same corporate family as the label. Some artists have reclaimed their publishing rights as they have become more established, which means you might be negotiating with an individual rather than a corporation. Some compositions are co-written, meaning multiple publishers hold shares and all of them need to agree.

Sub-publishing and Territorial Splits

International distribution adds further layers. A publisher in the UK might have sub-publishing agreements for the same songs in France, Germany, and Australia, meaning the entity that can grant you a UK licence has no authority to grant you a global one. If your app is available internationally, you may need to identify the rights holder in each territory separately, or find a publisher with genuinely global authority.

The practical consequence is that due diligence on a single track can take weeks. For an app planning to use dozens of tracks, the overhead of licensing each one individually becomes a significant operational burden before you have even discussed price.

Licensing Directly Versus Licensing Through a Platform API

App teams that want to integrate music have two broad routes. The first is licensing directly from rights holders, which gives you full control over how music is used but requires you to negotiate agreements yourself, maintain those agreements over time, and handle the compliance burden on your own. The second is integrating through a platform API, where the platform has already struck deals with rights holders and you operate within the boundaries of what that API permits.

Direct licensing makes sense when you have a specific catalogue in mind, a legal team to handle the agreements, and a usage model that does not fit what any existing API offers. It is the route taken by major streaming services and large media companies. For most app teams, it is expensive, slow, and operationally heavy for the value it delivers.

API Licensing as a Practical Route

Platform APIs shift the rights burden to the platform. The API provider has negotiated with labels and publishers on your behalf, and your agreement with the API provider sets out what you are permitted to build. This dramatically reduces the legal complexity, but it also constrains what you can do. You are working within the platform's commercial model, which means you inherit their restrictions on clip length, offline access, and how music can be displayed or attributed within your interface.

When evaluating a music API, read the API's terms of service before you design any music features. The technical documentation tells you what is possible; the terms tell you what is permitted, and those are often different things.

The choice between the two routes depends on your product's usage model, your legal resources, and how much flexibility you genuinely need.

How We Navigated Platform API Licensing on a Memory-Sharing App

We worked on a proof-of-concept for a company building an app that let users share memories with audio attached. The idea was that a user could find a song that meant something, a track from a particular moment in their life, and attach it to a shared memory within the app. The initial plan was to integrate with Spotify.

The problem became clear quickly. Spotify's API at the time did not offer robust support for short audio clips in the way the feature needed, and more critically, users would have needed an active Spotify account to interact with music within the app. That friction was a real barrier: the moment a user without Spotify hit a music feature, the experience broke. We looked at alternatives and switched to Deezer.

Why Deezer Solved More Than the Technical Problem

Deezer's API supported clips properly, and it did not require users to be logged in to Deezer to search or preview music. Users could search a catalogue that was actually larger than Spotify's and attach clips within the app without needing any existing Deezer relationship. Working with Spotify without a proper API would have required significant workarounds and custom technical solutions to stay within Spotify's rules. Using Deezer's official API in the way Deezer intended meant we were fully compliant without those workarounds, which simplified both the architecture and the compliance burden considerably.

There was a further commercial benefit. When a user wanted to hear a full track rather than the clip, there was a natural upsell to a Deezer subscription, which opened an affiliate referral revenue stream alongside the core product. The licensing route we chose was not just cleaner legally, it created a secondary income model the Spotify integration would not have supported.

Platform Rules: What Apple, Google, and Streaming Services Permit

Beyond music licensing agreements, your app operates within the rules of the platform it runs on. Apple and Google both set terms for how audio can be used within apps distributed through their stores, and those terms interact with your music licences in ways that are not always obvious.

Apple's guidelines, for example, restrict background audio playback for apps that are not primarily music players, and there are specific rules around how streaming content can be cached, attributed, and displayed. An app that caches tracks locally to improve playback performance might be solving a user experience problem while creating a policy violation with the App Store and a mechanical rights issue with the music's rights holders simultaneously.

Streaming Service API Terms

Streaming service APIs come with their own rulebooks on top of the platform rules. Spotify's developer terms prohibit a range of uses that might seem natural for an app integration: you cannot use their API to build a product that competes with Spotify, you cannot store their content beyond what the API explicitly allows, and you cannot alter how their player is presented without their approval. These restrictions are not edge cases buried in the small print, they define what the API is commercially available for.

Reading both sets of terms before designing a music feature is the only way to know what you are actually allowed to build. Designing first and checking compliance later is the pattern that creates expensive rebuilds.

Check both your music API's terms of service and the App Store guidelines for the platform you are building on before designing any audio feature. Conflicts between the two can force a rebuild at a very late stage of development.

How Usage Determines What You Owe

Music licence fees are not flat charges. What you pay depends on how the music is used, how many people hear it, and across how many territories. A licence that covers a small business playing background music in a single café costs a fraction of what a global streaming service pays for the same catalogue, and the pricing models that sit between those two extremes are where most app teams need to focus.

For apps, the most common variables are the number of active users, the number of streams or plays generated, the territories where the app is available, and whether music is a core feature or incidental background audio. A meditation app where music is central to the product will pay more than a fitness app where music is optional background content, even at the same user volume, because the rights holder's commercial interest in the first product is larger.

Revenue Sharing as an Alternative to Flat Fees

Some licensing agreements for digital services use a revenue share model rather than a fixed annual fee. The platform pays rights holders a percentage of revenue generated by the product, often with a per-stream floor to ensure minimum payments even when revenue is low. This can be attractive for early-stage products because it reduces upfront cost, but it also means the rights holder shares in your growth, which becomes expensive once the product scales.

Understanding the usage model is the prerequisite to understanding what any given licence will cost. Until you know how music will be used, you cannot get a meaningful quote, and any estimate you build a budget around will be provisional at best.

What Music Licensing Actually Costs

The range is genuinely wide, which is why budgeting for music licensing is difficult without specifics. At the lower end, stock music libraries charge annual subscription fees of a few hundred pounds for unlimited use of their catalogues within defined parameters. At the far upper end, licensing a well-known track for a major television campaign can cost between $10,000 and $500,000 according to Artyfile, with the variation driven by the track's popularity, the broadcast territory, and the duration of the licence.

For app products specifically, the cost depends heavily on which route you take. Direct licensing of major label music is rarely practical for early-stage apps. Platform API licensing costs are often built into revenue share or affiliate arrangements rather than upfront fees, which is part of what makes them attractive.

Royalty-Free, Creative Commons, and Stock Music Libraries

The phrase "royalty-free" is widely misunderstood. It does not mean free to use. It means you pay a one-time fee and then do not owe ongoing royalties each time the track is used. The upfront cost still exists, and the licence still has terms that restrict how the music can be used, in what contexts, and across which territories.

Creative Commons licences are a separate category. Music released under a Creative Commons licence comes with permissions baked into the release, but those permissions vary by licence type. A CC BY licence allows commercial use with attribution. A CC BY-NC licence prohibits commercial use entirely. An app that generates revenue is, in most interpretations, a commercial product, which rules out a significant portion of the Creative Commons catalogue.

Stock Music Libraries for App Use

Stock music libraries like Epidemic Sound, Artlist, and Musicbed offer subscription access to catalogues of tracks produced specifically for commercial use. Annual fees vary, but for a single app or product, an annual subscription in the range of a few hundred pounds typically covers a broad enough catalogue for most background audio needs. The limitation is that these catalogues do not include major label artists or recognisable songs, which matters if your product's value proposition depends on users finding music they already know and love.

For apps where music is functional rather than central, a sleep app, a focus timer, a meditation product, stock libraries are often the right answer and the compliance overhead is minimal. For apps where music recognition and emotional connection to known tracks are part of the core proposition, you will need a different route.

Commissioning Original Music as a Licensing Alternative

Commissioning original music sidesteps the licensing system almost entirely. If you pay a composer to create music for your app under a work-for-hire agreement, you own the resulting composition and the master recording outright. There are no ongoing royalties, no collecting society fees for the music you commissioned, and no restrictions on how you use it within your product.

The upfront cost is higher than a stock library subscription, but for a product where audio identity is part of the brand, a meditation app with a signature soundscape, a game with a composed score, it is often the most commercially sound approach over a three to five year horizon. You are not paying licence renewal fees, you are not exposed to a rights holder changing their terms, and you own an asset that compounds in value as the product grows.

What to Specify in a Commissioning Agreement

The agreement needs to be clear on several points or the ownership advantage disappears. The contract should specify that the work is created as a work for hire, that all rights in both the composition and the master transfer to you on payment, that the composer waives moral rights where the law permits, and that the agreement covers all territories and all uses including future formats you have not yet built. A composer who retains performance rights, for example, can still generate collecting society fees even on music you commissioned and paid for.

If you commission original music, have a music lawyer review the agreement before you sign. A standard freelance contract almost never covers the full transfer of rights you need for commercial app use.

Territorial Scope and International Distribution

Music rights are territorial by default. A licence granted by a UK publisher covers the UK. The same publisher, administering the same song, may have sub-published the rights in other markets to local affiliates who hold authority for their own territories. When your app is available globally through the App Store or Google Play, a single-territory licence leaves you unlicensed everywhere else.

This is one of the reasons platform API agreements are attractive for international products. When Deezer or a comparable service has negotiated global rights for their catalogue, using their API means you inherit that global coverage within the terms of the API agreement. Trying to replicate that coverage through direct licensing would mean negotiating with rights holders territory by territory, which is only feasible for a large music service with a dedicated rights team.

Territory Restrictions in Stock Licences

Stock music licences often specify the territories they cover, and some are restricted to a single country or region. An app team that purchases what they believe is a global licence needs to check the small print, because a licence covering "worldwide" use sometimes excludes specific markets, particularly where the library does not have clearance from local collecting societies. Distribution through a global app store does not automatically make a restricted licence valid in territories it was not granted for.

The simplest approach is to decide your distribution territory before you licence anything, and then confirm in writing that any licence you purchase covers every country on your list. Ambiguity on this point is a compliance risk that does not resolve itself over time.

The Compliance Risk of Getting It Wrong

Music rights holders enforce their rights. Major labels have dedicated legal teams whose function is identifying unlicensed use and pursuing it, and the scale of the infringing product does not reduce their appetite to act. An app using unlicensed music that happens to be small or niche is simply not yet on the radar, which is a different thing.

The financial exposure from infringement is not proportional to what a licence would have cost. Statutory damages in the US, for example, can reach $150,000 per work for willful infringement. A product using ten tracks without licences faces a damages calculation that could threaten the business itself. In the UK, infringement claims are calculated on the basis of loss and licence fees foregone, which is typically lower but still significant relative to what an early-stage app can absorb.

App Store Removal as an Immediate Risk

Rights holders can issue takedown notices that result in an app being removed from the App Store or Google Play, often with very little notice. An app pulled mid-growth for a music rights violation loses momentum that is very hard to recover, and the reputational damage with users who find the app suddenly unavailable is real. Sorting the compliance question before launch is always cheaper than sorting it after a takedown.

The pattern we see in projects where music was not properly licensed is that the team knew it was a risk, underestimated how quickly it would become a problem, and planned to address it at a later stage. That stage tends to arrive faster and more expensively than anyone expected.

How to Budget for Music Licensing Before You Build

Music licensing should be a line item in the product budget before a single line of audio-related code is written. The right amount depends on the route you choose, but the process of arriving at that number forces decisions that will shape the feature design itself.

1. Define what role music plays in the product. Is it central to the user experience, or is it background audio that supports another core feature?
2. Decide whether you need a recognisable catalogue or whether original or stock music serves the same purpose for your users.
3. Identify your distribution territory and confirm that any licence you consider covers all of it.
4. Get legal advice specific to music licensing before committing to a feature design that assumes a route that may not be available at your budget.
5. If you plan to use a platform API, read the full terms of service before designing any feature that depends on what the API can deliver.

The memory-sharing proof of concept we worked on is a useful example of how this process shapes decisions. The switch from Spotify to Deezer was not just a technical choice, it was a licensing and commercial model decision that changed the product's revenue potential and its compliance architecture at the same time. Starting with the licensing question rather than the technical question would have reached the same answer faster and without the detour.

Budgets for music features that require direct licensing should include legal fees for negotiation and agreement review, which are often as significant as the licence fees themselves. Allocating for the music cost but not the legal overhead is a common gap that creates problems when the invoice arrives.

Royalty-Free, Creative Commons, and Stock Music Libraries

Conclusion

Music licensing is not a box to tick after the product is built. The licensing question shapes which features are feasible, which routes to integration make sense, and what the true cost of audio in your product is. Getting to those answers early saves money, time, and the kind of legal exposure that can pull a product off the market at the worst possible moment.

The range of options is genuinely broad. Stock libraries work well for background audio where catalogue recognition does not matter. Platform APIs like Deezer offer a practical route to real music integration without the overhead of direct licensing, and as we found on the memory-sharing proof of concept, the right API can open revenue models that were not part of the original plan. Commissioned original music is worth serious consideration for any product where audio identity is part of the brand. Direct licensing is the right answer in specific circumstances, and expensive in most others.

The common thread across every route is that the decision needs to happen before the feature is designed, not after it is built. A product that reaches the App Store with an unlicensed music feature is one takedown notice away from losing the audience it spent months building.

If you are building a product where music plays a role and you are not yet sure which route fits your situation, let's talk about your product and what it needs.

Frequently Asked Questions