How to Set Up Your DistroKid Account the Right Way - Jack Righteous

How to Set Up Your DistroKid Account in 2026: Plans, Payments, Splits & AI Rights

Gary Whittaker
DistroKid Account Setup · Before Your First Upload

Set up the DistroKid account before you set up the release.

This page is for account-level decisions: which plan controls you need, how many artist identities the account must support, whether paid extras solve a real problem, how payments and splits will work, and what rights records should exist before you upload.

If you already have the account and need help with artist-page mapping, metadata, streaming profiles or HyperFollow, use the separate release-setup guide. If those decisions are already made and you are ready to submit the release, go directly to the upload workflow.

Set Up the AccountRelease Setup & Profile MappingUpload Workflow
First decision

Do not choose a DistroKid plan from an old pricing table

DistroKid changes plan features, optional extras and pricing over time. Decide what the account needs to do first, then compare the current plans on DistroKid and choose the smallest one that supports those needs.

Account question, not release question: how many artist or project identities must this account support, and what controls do you need before the first release is created?

Compare DistroKid's current plan features →

Account requirements

Define the job before you pay for the plan

  1. Count the artist identities. Decide whether this account is for one artist/project or several. That decision can affect which account tier makes sense.
  2. Decide whether future release scheduling matters. If you run campaigns around exact release dates, verify that the current plan includes the scheduling controls you need.
  3. Identify any account-level controls you actually need. Do not pay for features because they sound professional; connect each feature to a release or operating requirement.
  4. Decide whether HyperFollow data matters to your campaign. Treat this as an account/tool decision here; the actual HyperFollow release workflow belongs in the release-setup guide.
  5. Decide how collaborators will be paid. Know whether you expect to use DistroKid's split tools and make sure the underlying ownership/revenue agreement exists outside the platform.
  6. Separate distributor money from publishing money. A distributor account does not automatically solve songwriter, publishing-administration or collection-society decisions.
Keep identity work narrow here

The account needs to know who you are releasing as. The release guide handles the rest.

Before you create releases, settle the exact artist or project name well enough to know which identity belongs in this account. If you already have music on Spotify, Apple Music or other services, the detailed job of matching the next release to the correct artist pages belongs in the DistroKid Setup Guide 2026.

Keep a basic account record with the artist/project name, the identities the plan is expected to support, the person responsible for the account, and any collaborator relationships that affect payments or release administration.

Optional extras

Distribution and paid add-ons are separate choices

Sending a release to supported social or streaming destinations is not the same thing as purchasing an optional DistroKid extra. Evaluate every add-on against a defined release or catalogue need.

Social-media identification / monetization

Use it only when the current eligibility, fee structure and claim behavior fit your rights and campaign needs. Check the live terms before enabling it.

Leave a Legacy

Consider it only if its current catalogue-retention terms solve a real problem for the release.

Other Album Extras

Review them one by one. An optional checkbox is not automatically a best practice.

Review current DistroKid Album Extras →

Payments & collaborators

Set up the money path before you expect money to move

Complete the payment, tax and identity information DistroKid currently requires before you expect to withdraw earnings. Withdrawal methods, fees and tax treatment can vary, so use the live account information rather than an old minimum-withdrawal claim.

If collaborators share revenue, agree on credits, ownership and splits before the release. DistroKid's split tools can automate eligible revenue allocation, but the platform setting is not a substitute for a written understanding of who owns what and how income is divided.

Rights boundary

Distributor royalties and publishing royalties are not the same system

DistroKid distributes sound recordings and reports money allocated to those releases. Songwriting and composition royalties can involve separate organizations, administrators and territorial rules.

Do not register everywhere by default. The correct setup depends on where you live, what rights you control, whether a publisher or administrator already represents you, and which collection organizations apply to your territory.

Practical rule: use this page to recognize the boundary. Handle the actual publishing/collection setup as its own rights decision rather than treating the distributor account as the answer to every royalty question.
AI rights record

Document the source of the release before the upload form asks questions

For AI-generated or AI-assisted work, keep a record of the tools used, generated elements, human contributions, collaborators, licensed material and any permissions that affect distribution. DistroKid's current AI guidance requires the uploader to have the legal right to distribute the material and places limits around infringement, impersonation and spam.

AI Credits and other disclosure choices belong to the release itself, but the account should already have a documentation habit before the first upload.

Read DistroKid's current AI-upload guidance →

Account ready

Do not repeat the same setup work on three different pages

Once the account decisions above are made, stop configuring the account and move to the next job. The JR DistroKid road now separates those jobs deliberately:

1 · Account

This guide

Plan requirements, artist capacity, optional extras, payments, splits and rights boundaries.

2 · Release setup

Metadata, mapping & profiles

Prepare the release identity, map the correct artist pages, verify destination profiles and configure HyperFollow.

Open Release Setup →

3 · Upload

Submission workflow

Prepare the final package, enter metadata and AI Credits, select destinations and submit the release.

Open Upload Guide →

After delivery

The account is infrastructure. The campaign still needs a job.

After the release is delivered and verified, choose where discovery starts, where the campaign gets support and where interested people should go next.

Use AI Music Discovery in 2026 to choose the discovery environment, then use the Free Creator Campaign Builder to assign one PRIMARY platform, one SECONDARY platform and one OWNED destination.

Before you leave this page

DistroKid account setup is complete when the operating decisions are clear.

  • The account supports the number of artist identities you actually need.
  • The plan provides the release controls you intend to use.
  • Optional extras have a defined purpose.
  • Payment and tax setup is understood.
  • Collaborator splits are agreed outside the platform as well as configured inside it.
  • Publishing rights are not being confused with distributor revenue.
  • AI and third-party contributions have a basic rights record.
Next: Set Up the Release →Already Ready? Go to Upload →
Referral note

If DistroKid fits the release route

If you decide DistroKid fits, I may receive a referral benefit if you use an eligible referral link. Referral offers and discounts can change, so this guide does not hard-code an old percentage.

Check the current DistroKid referral checkout offer →

Practical creator education only; not legal, tax or financial advice. DistroKid and applicable rights-organization terms control. Account-role and routing structure updated September 7, 2026.

Back to blog

Leave a comment

Please note, comments need to be approved before they are published.