Label, White-Label or API: Which Do You Need?
A label account, a white-label workspace and a distributor API are easy to confuse, because all three sit under the heading “for labels”. They answer different questions. A label account answers how your team releases music for a roster. A white-label workspace answers where your artists sign in and whose name is on the door. An API answers how your own software talks to a distributor. Label Software, the fourth product on the pricing page, answers a fifth: how you run the label side of the business when distribution is already arranged elsewhere.
This is the hub for those four. It compares them using WBBT’s public pages as they stood on 25 October 2026, gives a short decision path, lists the fee questions worth asking any provider and says what to bring to a sales conversation. The how-to detail lives in the guides for each route: releasing under your own label name, white-label distribution and the distribution API. If you are starting from nothing, begin with how to start a record label.
The short answer
- Your own team uploads and manages releases for several artists: the Label plan is the usual starting point.
- You already have a distribution deal and want label management tools: Label Software, which does not include WBBT distribution.
- Your artists should sign in under your name, and you approve what they submit: White-Label, which is early access.
- Your own application has to create releases and read reports: the Distributor API, which is early access and sits on top of an eligible Label account.
- You are one artist who wants your own label name on releases: you may need none of these. The label-name guide shows which plan covers which field.
Two of the four are in early access, with no public price, capacity or launch date. Treat anything written here about them as a map of what to ask, and rely on the written offer for the rest.
The four products side by side
| Label plan | Label Software | White-Label | Distributor API | |
|---|---|---|---|---|
| What it is | A WBBT account for managing a roster | Label management software with your own admin panel | A branded workspace for your own artists | A REST interface for your own application |
| Distribution through WBBT | Included | Not included | Included, scope agreed with sales | Through WBBT, by agreement |
| Branding | WBBT-branded, with your label name on releases | No WBBT brand | Your platform name, logo, colours and text | Your own product, showing the attribution the API terms require |
| Address | The WBBT app | A wbbt.net subdomain, or your own domain as an optional add-on | Confirmed in the written offer | Not applicable |
| Artists and releases | Unlimited | Unlimited | Sized to your roster | Set in your agreement |
| Who answers artists | Your team | Your team | Your team first, with escalation to WBBT | Your team and your product |
| Public price | $8.99 a month or $89.99 a year | From $14.99 a month or $134.99 a year, final price in a proposal | Starting price on request | Custom quote |
| How you get it | Choose the plan | Talk to sales | Apply in your account (early access) | Apply in your account (early access), needs an eligible Label account |
The amounts come from the pricing page on the date above and change when the page changes, so check it before you rely on them. The Label plan lists a 0% commission, a custom label name for “Provided to YouTube by”, YouTube Content ID, PPL collection and the pitch tools. Label Software lists none of the distribution-dependent features, because it is the software on its own. The White-Label page and the Distributor API page describe the two early-access products in full.
Start with your workflow, not the product
Write down the path from an artist delivering a master to a release appearing in stores, and put a name against each stage: intake, rights checks, metadata review, delivery, corrections, reporting and artist questions. Mark what happens often and what needs a person’s judgement. Then write three numbers for today and for twelve months from now: artists, releases a month and tracks in the catalogue. Ask what you would do about the answers if the roster doubled, rather than only what you do now.
Also map access. A label owner needs the whole catalogue in view. An artist should see only their own releases and the information they are meant to have. That boundary exists whichever product you pick, so settle it on paper first.
Three invented labels show how the same questions give different answers.
| Invented label | Today | What decides it | Likely route |
|---|---|---|---|
| A: six artists, one organiser | Two releases a month, all uploaded by the organiser | Nobody else needs to sign in | Label plan |
| B: forty artists who want to submit themselves | Staff check each submission and answer questions | Artists need a branded place to sign in, and the label approves before WBBT sees a release | White-Label, after a sales conversation |
| C: a production-tools app with its own users | Users finish tracks inside the app | Releases must start inside the product, with status shown back to the user | Label plan with the API, after an approved application |
None of these is a recommendation for a real business. They only show that roster size alone does not decide the product. Who needs to log in, and where the release starts, do.
A decision path
The same path in words, for anyone reading without the picture:
- If you do not need WBBT to distribute, because another distributor already does, look at Label Software.
- If you do, and your artists must sign in to a portal that carries your brand, with your approval before a release reaches WBBT, ask for White-Label.
- If your artists do not need that, and your own software must create releases and read reports, ask for the API on top of a Label plan.
- If none of that applies, start with a Label plan.
The path assumes a business with a roster. A single artist who only wants a label name on releases should read the label-name guide, because the copyright lines start on the Pro plan and the “Provided to YouTube by” name is part of a Label plan.
Common mismatches
- Buying a branded workspace to look bigger. A white-label portal changes the front end and the rules you control. It does not remove review, rights checks or support. Someone on your team still answers when a release is returned.
- Expecting Label Software to distribute. It does not include WBBT network distribution, YouTube Content ID, the pitch tools or PPL collection. It is the panel on its own.
- Starting an integration before the metadata is stable. Automating inconsistent inputs multiplies the corrections. Settle artist spellings, credits and approval steps by hand first.
- Assuming every dashboard action has an endpoint. Read the current API documentation and the list of operations before an engineer estimates the work.
- Using the API to release your own music. You do not need it. The Release Wizard, or an assistant connected through WBBT MCP, prepares your own drafts. MCP is for personal use and never submits a release.
- Treating a tool as an agreement. Software holds your artists’ details, and it does not replace a written contract about rights, splits and commission. Keep the signed copy beside the catalogue register.
Fee questions to ask any provider
A low headline figure can sit beside limits, optional charges or service fees, and a higher subscription can replace a real running cost. Ask for an itemised answer, and ask it of every provider you compare, WBBT included.
| Category | Ask | What WBBT’s public pages say |
|---|---|---|
| Subscription | What recurs, and does the price change with roster size? | The Label plan publishes a monthly and a yearly price. Label Software shows a starting price and a proposal. |
| Per release or track | Is there any charge per release or per track? | The Label plan lists unlimited releases. Check your offer for the rest. |
| Commission | What share of royalties does the provider keep? | The pricing table lists 0% for the label products. In a white-label workspace the commission your own artists pay is a setting you control, and the offer should state what applies to you. |
| Add-ons | What costs extra? | A custom domain for Label Software is an optional add-on, and further custom label names are a paid extra shown before you confirm. |
| Setup and onboarding | Is there a one-off charge? | No fixed API setup price is advertised. Ask for it in the proposal. |
| Payout charges | Who pays transfer and conversion charges? | Third-party charges can apply to withdrawals, and the withdrawal screen states them before you confirm. |
| Capacity | What limits apply to artists, releases and requests? | No fixed capacity or rate limit is published. Limits are agreed in your scope. |
| Leaving | What can you export, and what happens to live releases? | The Label plan lists that releases stay live with the free-tier commission if you cancel. Ask sales for the position on the early-access products. |
Then model a quiet month and a busy month. Count the releases you would really submit, the staff hours you would spend and the charges that follow from each, and compare the totals instead of the headline prices.
What sales needs, and what a written offer contains
For White-Label or the API, send a short brief to [email protected] and ask for a sales consultation. Include your business, artist count, catalogue size, expected releases a month, territories and stores, branding and domain needs, how artists will join, and what must work on day one against what can follow. Do not send passwords or API keys.
A useful written offer states the enabled features, the capacity that applies, the onboarding steps, how support and escalation work, how data export and account closure work, the price, and the order of events: acceptance, signing, payment, then activation. If something matters to you and it is not in the offer, ask for it to be added, because a general feature list is not a commitment.
What early access does and does not mean
White-Label and the API are applied for from your account. A public account signup does not switch either one on. The team reviews your requirements, confirms the scope and onboarding, and activates after the agreement and payment. The API also needs an eligible Label account underneath it, while White-Label is not a prerequisite for the API.
Nothing in the public material promises a launch date, an unlimited package, a rate limit or an uptime figure. Features can change while a product is in early access, so plan from the document you sign, and keep the current API documentation beside it when engineers estimate the work.
What you still owe your artists
Whichever route you take, the artist relationship is yours. Agree in writing who owns what, how income is split and what commission applies, and tell artists where to ask questions. WBBT reports royalties in monthly cycles after store reports are processed, and daily or weekly views describe already reported earnings, so explain that difference before your artists meet it on a screen.
The UK’s voluntary Code of Good Practice on Transparency in Music Streaming sets a reasonable bar for a label of any size. Among other things it says that music makers should receive a statement of accounts and any royalties due at least twice a year, and that advances and recoupable costs should be stated clearly. It is voluntary and was written for the wider industry, but it shows what artists are learning to expect. If you sign artists on terms rather than only distributing for them, record deal terms to check before signing lists the questions they should be asking you.
A four-week way to decide
- Week one: map. Write the release workflow and the three roster numbers. Decide who must log in anywhere other than your team.
- Week two: price what is public. Read the pricing page and fill in the fee table above for the Label plan and, if relevant, Label Software. Note every question you cannot answer.
- Week three: ask. If White-Label or the API is on your list, send the brief and ask for a written scope. Ask the questions from the table and the data export and closure questions as well.
- Week four: pilot on paper. Take one real release and walk it through the proposed flow, including a rejection and a correction. Name who answers the artist at each step.
- Decide, and record why. Keep a short note of the reasons and the date. Review it after your first full reporting cycle, because the monthly rhythm of statements often changes what a team needs.
If your catalogue already lives elsewhere, read switch distributors without losing streams before you move anything, and keep the old delivery live until the new one has been checked.
Frequently asked questions
Do I need White-Label to run a label with several artists?
No. The Label plan has unlimited artists and releases, roster management and a WAV export of the catalogue, and your team uploads for the roster. White-Label is for a different need: a workspace where your artists sign in under your own brand and you approve what they submit. See white-label music distribution for labels before you decide.
Is the API a cheaper way to get a white-label product?
No, they are different products. The API connects your own application to the release workflow, so you build and run the interface yourself. It also needs an eligible Label account and an accepted, signed and paid API offer. The developer guide explains what the integration involves.
Which of these have a public price?
Two. The pricing page publishes the Label plan and a starting price for Label Software. White-Label shows a starting price on request, and the API is a custom quote. Nothing here is a fixed price for a fixed capacity, and a written offer is what counts.
Can I start on a Label plan and move to White-Label later?
The public pages do not promise a particular upgrade route, so ask sales how it would work for your catalogue before you plan around it. Whatever you choose, keep a register of every release with its ISRCs, UPC and original release date, because identifiers must stay the same if a catalogue moves.
Does choosing White-Label or the API change who owns my artists’ music?
No. Distribution does not by itself transfer ownership of recordings or songs. What your artists agree with you, and what you agree with WBBT, is set out in the agreements, so read both and keep copies.
How quickly can a white-label workspace or an API integration go live?
No date is promised. Both are in early access and are applied for from your account. Activation follows a review of your requirements, a written offer, acceptance, signing and payment, and onboarding is confirmed for your own setup.
Sources and next steps
These are the primary documents behind the points above. Terms and documents change, so read the current version before you act.
- UK Voluntary Code of Good Practice on Transparency in Music Streaming, GOV.UK, published by the Intellectual Property Office on 31 January 2024 (accessed 25 October 2026).
- WBBT API documentation and the OpenAPI file, for endpoints, authentication and test behaviour (accessed 25 October 2026).
- Become a PPL member, PPL, for labels that own or exclusively license recordings (accessed 25 October 2026).
Compare the WBBT plans, read the White-Label page and the Distributor API page, and check the WBBT FAQ for the white-label and API group. For the groundwork, read how to start a record label. If you will take demos from artists, how to submit a demo to a record label shows what a sender should include, which is worth reading before you write your own submission page. Ready to open an account? Submit your music.
White-Label Music Distribution →
Your brand. A distribution workspace for your team.



