Releasing for the diaspora

When stores go live

Stores release by country. Spotify's help describes the two ways a release can be set: at 12:00 am local time in each country, or at one moment worldwide, its example being 12:00 am UTC. Which one you get depends on what your distributor offers and what you choose.

Local midnight is what happens unless you choose otherwise. DistroKid puts it simply: a single that goes live at midnight in London reaches New York about five hours later. For a Punjabi release, the song opens first where the clock is furthest ahead. On a Friday between November and mid-March, midnight in Melbourne is 6:30 pm on Thursday in Punjab. Midnight in Brampton is 10:30 am on Friday in Punjab, and midnight in Surrey is 12:30 pm. Eighteen hours pass between midnight in Melbourne and midnight in Surrey.

One detail the help pages don't settle is how a store handles a country with several time zones, such as Canada or Australia. Spotify's help says "local time in each country". DistroKid says its own global-release option sets each country's time from that country's easternmost time zone. So don't promise fans in Surrey a minute you haven't checked. Open the store there, or ask someone there, and post the link once it's live.

One global time is the other option. Some distributors let you pick a release time that every supporting store honours at the same moment. Amuse's help lists the stores that support it, among them Spotify, Apple Music, YouTube Music, Amazon and Facebook/Instagram, and says stores that don't fall back to midnight in each local time zone, which can mean a later date. Ask your distributor which DSPs honour its timed release before you build a plan around it.

For a song whose audience is split between Punjab and the diaspora, I prefer one global time, chosen so it lands at a sensible hour in the two places that matter most for that song. A fan in Brampton shouldn't see a reel about a song hours before they can play it.

Two side effects to know about. Spotify for Artists shows the earliest date the release is live anywhere, so a release set for 12:00 am UTC on 1 January appears as 31 December in western time zones. And Spotify counts its stats in UTC days. A song that goes live at midnight IST has only five and a half hours in its first "day", so its first-day number will look small. Judge it on the second.

IST against Brampton, Surrey, Southall, Melbourne and Dubai

India doesn't change its clocks: IST is UTC+5:30 all year. Of the five cities, three change their clocks, each on a different date, and Surrey stopped this year.

Three things catch people out. British Columbia adopted permanent daylight time. Clocks went forward on 8 March 2026 and stay there; they won't go back on 1 November. Any chart that puts Surrey 13 hours 30 minutes behind Punjab in winter is now wrong, and Brampton and Surrey are two hours apart in winter, not three.

The UK and North America change on different weekends. From 25 October to 1 November 2026, London has gone back and Brampton hasn't, so they're four hours apart instead of five. The same happens from 14 to 28 March 2027.

Melbourne runs the other way. Its clocks go forward in October and back in April, so from November to March it is five and a half hours ahead of Punjab while London and Brampton are at their furthest behind.

Premiering for two audiences

A YouTube Premiere is one moment for everyone. YouTube creates a public watch page, viewers set reminders, and YouTube notifies them about 30 minutes before and again when it starts. The chat runs live, and afterwards the video stays on the channel as a regular upload. You can't hold it at 8 pm in every city.

So I choose the two audiences a premiere is for. YouTube Studio's Audience tab has a report called When your viewers are on YouTube, covering the last 28 days, and YouTube suggests it for choosing a Premiere time. Top geographies shows where the channel's watch time comes from, and Spotify for Artists shows top countries and top cities. Between them you'll know whether this artist's second audience is in Brampton or in Southall.

Evening in Punjab works for the UK and Dubai, and lands at breakfast or office hours in Canada. Early morning in Punjab catches Canada's evening and Melbourne's afternoon, and it's the middle of the night in Southall. No hour works for all six.

The audience the premiere doesn't suit gets its own moment: the artist live on Instagram in their evening, a reel or a Short posted for their prime time, a community post when they wake up. A premiere is one event. A release has room for several.

Creators across time zones

Creator posts have the same problem on a smaller scale. A creator in Surrey who posts at "release time" in IST is posting before lunch on a working day.

• Brief in their time, with IST alongside. "Post between 7 and 9 pm your time on Friday (7:30 to 9:30 am Saturday, IST)" leaves nothing to convert and nothing to get wrong.
• Check the sound where they are. Ask each creator to find the song in their own Instagram app before their window opens. If it isn't there yet, they wait.
• One sound page, in every country. Every creator uses the same sound, so the count builds in one place. One sound page, and why it matters explains why.
• Plan diaspora waves for their evening. A wave timed for Friday night in Brampton is a different booking from one timed for Friday night in Punjab. Schedule them separately.
• Follow the disclosure rules where the creator lives. India's ASCI lists Instagram's Paid Partnership label among acceptable disclosures, and says platform tools should supplement the creator's own label. The UK has the ASA's influencers' guide; Canada has Ad Standards' disclosure guidelines. Our brief asks every paid creator to use the paid partnership label and a clear label of their own.