DISTROBOLT ARTIST GUIDES
Choose streaming and download destinations for your release
Choose destinations around audience needs and the rights you can actually grant. A large store count is less useful than a verified delivery plan covering the services, territories and monetisation uses that matter for your release.
Build a destination matrix
For each requested destination, record audience relevance, streaming or download use, intended territories and any separate rights question. Add an evidence column for actual distributor availability. Distinguish a request from a confirmed delivery. A destination logo on a public page does not by itself establish eligibility for every release or account.
Separate different uses of the recording
Streaming, paid downloads, user-generated video uses and identification or claiming systems can involve different delivery and permission requirements. Do not assume that selecting a streaming store also authorises every social monetisation use. Review samples, cover material, non-exclusive licences and collaborator permissions before deciding what to request.
Confirm the available controls
Ask DistroBolt which destinations and territory settings can be selected for your specific release, and how exclusions or later changes are handled. Do not infer a DistroBolt control from another distributor’s upload form. Keep the written answer with the release brief, including any eligibility restriction. A request to exclude a destination is not proof that an earlier delivery has been removed.
Check the actual result after launch
Verify correct artist identity, playable tracks and the intended product on priority destinations. Record an unavailable territory or missing service with the relevant release reference and observed date. Escalate the specific issue through the distributor. Avoid uploading a competing duplicate just to reach one missing store. Review the destination plan again when rights, territory permissions or the release version changes.
Sources and review
Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.
Continue your release planning
- Change a release date before delivery: decision checklist
- Move a release date after stores have received it
- What must be ready before you book a release date?
Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.