Why don't broadcasters just use local time for everything?

Because a satellite feed or streaming trigger must happen at the same instant for every region. Local time changes with DST and longitude. UTC is the only clock that stays constant.

How do I convert a BBC World Service schedule to my local time?

Take the UTC time from the schedule. Add or subtract your UTC offset. In January 2026, New York is UTC-5, so 07:00 UTC becomes 02:00 EST. In July 2026, New York is UTC-4, so 07:00 UTC becomes 03:00 EDT. Your offset may change with DST; UTC does not.

Which streaming platforms use 00:00 UTC?

Netflix uses 00:00 Pacific Time. Amazon Prime Video and Disney+ also anchor to Pacific Time. Some smaller platforms use 00:00 UTC. Check the platform's help page or a release announcement, they usually state the anchor time zone.

What happens during a leap second in broadcasting?

Leap seconds are rare (27 since 1972, most recently 31 December 2016). Broadcast automation systems handle them by smearing the extra second across the minute or by inserting 23:59:60 into the timecode. Most viewers notice nothing. The IERS announces leap seconds about six months in advance.

Is UTC the same as GMT in broadcasting?

Practically, yes. The BBC World Service schedule used to say "GMT" and now says "UTC". The difference (UTC uses atomic time, GMT used solar time) does not affect scheduling. Both are UTC+0 with no DST.

UTC in Broadcasting: Scheduling for a Global Audience

Most people think TV schedules are just local. They are not. The entire global broadcasting chain—from satellite uplinks to streaming releases—runs on Coordinated Universal Time.

Why Broadcasters Use UTC

A London station schedules a show for 8:00 pm. That same show must play at the same absolute moment in Lagos, Dubai, and Singapore. If each station used its own local time to schedule the satellite feed, the coordination would collapse.

UTC gives every broadcaster a single reference clock. No daylight saving shifts. No confusion over "tonight" versus "tomorrow" when the date line is involved. A satellite engineer in Tokyo and a producer in London both read the same number.

Shortwave Radio: BBC World Service and VOA Schedules

Shortwave listeners find schedules published in UTC. The BBC World Service and Voice of America print programme times as, for example, "07:00 UTC" rather than "08:00 BST" or "02:00 EST". This is not a courtesy. It is a requirement.

A shortwave signal crosses time zones. A broadcast aimed at West Africa at 19:00 UTC is heard in Lagos at 20:00 WAT and in Accra at 19:00 GMT. The listener converts UTC to their local offset. If the schedule used British Summer Time, a listener in Nairobi would need to know that BST is UTC+1 and adjust twice (once for DST, once for their offset). UTC removes that extra step.

The BBC World Service has used UTC (and previously GMT) for its international schedules since long before digital distribution. Voice of America follows the same rule. Both organisations publish their frequency guides exclusively in UTC.

Satellite TV: Encryption Keys and UTC

Satellite uplinks are scheduled in UTC. A satellite operator books transponder time in UTC blocks. The encryption key changes, the moment a scrambled channel becomes viewable or a pay-per-view event unlocks, are triggered by UTC timestamps.

A live football match on a Middle Eastern satellite might have its encryption lifted at 18:30 UTC so that viewers from Morocco to Iraq all see the kick-off at their local time (19:30 in Cairo, 22:30 in Dubai). The key change is a UTC event, not a local one.

This matters most during DST transitions. If a European broadcaster moved its encryption key schedule to local time, the changeover would wander by an hour twice a year. Satellites do not observe DST. The uplink stays on UTC.

Live Global Events: Olympics and World Cup in UTC

The Olympic Games and the FIFA World Cup are produced using a UTC reference. The host city operates on its local time, but the international broadcast feed is timed and logged in UTC.

When the 2026 Winter Olympics run in Milan and Cortina d'Ampezzo (UTC+1 in January, UTC+2 during summer time), the production control room logs every camera cue and replay trigger on a UTC clock. The broadcast delay, the few seconds between the live event and what the viewer sees, is calculated from the UTC timestamp.

World Cup matches are scheduled with the kick-off time stated in the host nation's local time and in UTC. The global broadcast schedule is printed in UTC so that a rights-holder in Tokyo knows that "14:00 UTC" means 23:00 JST. No arithmetic involving the host's DST is needed.

Streaming Platforms: Global Release Times

Netflix, Amazon Prime, Disney+, and Apple TV all set global release times either to 00:00 UTC or 00:00 Pacific Time (PST/PDT). This choice determines when a viewer in Berlin or Brisbane gets access.

The 00:00 UTC Release Strategy

A show released at 00:00 UTC drops at:

01:00 in Paris (CET, UTC+1 in January)
02:00 in Cairo (EET, UTC+2)
05:30 in Mumbai (IST, UTC+5:30)
08:00 in Singapore (SGT, UTC+8)
11:00 in Sydney (AEDT, UTC+11 in January)

The same moment everywhere. The advantage for the platform is a single trigger. The disadvantage for a viewer in Los Angeles (16:00 PST) is that the show arrives in the afternoon, not at the stroke of twelve.

Other platforms use 00:00 Pacific Time. A show released at 00:00 PT drops at 08:00 UTC in winter (PST, UTC-8) or 07:00 UTC in summer (PDT, UTC-7). This makes the release European-friendly (08:00 in London, 09:00 in Paris) but pushes it to 13:30 in Mumbai and 16:00 in Singapore. The viewer must know the platform's chosen anchor, then convert.

Broadcast Automation and UTC Timecode

Television playout systems use timecode synchronised to UTC. A master control room in London running a playout server at UTC+0 does not change its clock when the UK switches to BST. The server stays on UTC. The local time display on the studio wall is a separate conversion.

This prevents a common error: a recorded programme scheduled to play at "01:00" local time would break during the spring-forward DST gap (02:00 becomes 03:00, the hour from 01:00 to 02:00 never exists). A UTC-based scheduler never encounters that missing hour because UTC has no DST.