Once you hit submit on a release, it moves through a defined pipeline. Understanding each stage helps you know what's normal and what might need your attention.
1. QA review (automated, usually instant)
Your release is automatically checked against a QA checklist covering things like missing metadata, cover art dimensions, ISRC validity, and audio file integrity. If something fails, you'll see exactly which check failed on the review screen before the release can be submitted — this happens before delivery starts, not after, so you're not waiting days to find out about a fixable metadata issue.
2. Pending (typically same-day to a few days)
The release is queued and being packaged for delivery to every store you selected. This is largely automated but can take a little longer during high-volume periods (major release days across the industry, e.g. Fridays, or holiday weeks).
3. Distributing (1–14 days depending on stores)
Your release is actively being delivered to each selected store. Delivery time varies significantly by store — Apple Music is often 1–3 days, Spotify 2–5 days, while something like Vevo for official video can take 7–14 days. Not every store goes live on the same day, even for a single release; this is normal and expected, not a sign of a problem.
4. Live
The release is live on at least one store and streaming data will start appearing in your Music analytics once the platform begins reporting — usually within 24–48 hours of first going live on that specific store.
Timing recommendation
We recommend submitting at least 14 days before your target release date. This isn't just a buffer for delivery — it also leaves a window to pitch your release for Spotify editorial playlist consideration, which closes once a track is already live and can no longer be pitched retroactively.
If something looks stuck
If a release has been in "Distributing" for longer than the typical window for that store, check the release's per-store delivery notes first — sometimes a store has flagged something that needs your input. If nothing explains the delay, open a support ticket with the release name and we'll look into it.