Standard UTC offsets from UTC-12 to UTC+14 with example cities, plus which markets move their clocks for daylight saving and which stay fixed.
A campaign scheduled in your own time lands at the wrong hour for half the world. This page lists standard UTC offsets with example cities, then flags the markets that shift for daylight saving so your sends stay on time all year.
Data checked: July 26, 2026. Offsets shown are standard time (Northern winter). Read the daylight saving section before you schedule.
The offsets in the table are standard time. Where daylight saving is observed, the clock moves forward one hour in that region’s summer, so the offset changes for part of the year. Northern and Southern hemisphere summers fall in opposite months, so their clock changes happen at opposite ends of the year. Schedule against a named zone, not a frozen number.
| Offset | Example locations (standard time) |
|---|---|
| UTC-12:00 | Baker Island, Howland Island |
| UTC-11:00 | Pago Pago (American Samoa), Niue |
| UTC-10:00 | Honolulu, Papeete (Tahiti) |
| UTC-09:00 | Anchorage |
| UTC-08:00 | Los Angeles, Vancouver, Tijuana |
| UTC-07:00 | Denver, Phoenix, Calgary |
| UTC-06:00 | Chicago, Mexico City, Guatemala City |
| UTC-05:00 | New York, Toronto, Bogota, Lima |
| UTC-04:00 | Santiago, Halifax, Caracas, La Paz |
| UTC-03:30 | St. John’s (Newfoundland) |
| UTC-03:00 | Sao Paulo, Buenos Aires, Montevideo |
| UTC-02:00 | Fernando de Noronha, South Georgia |
| UTC-01:00 | Azores, Cape Verde |
| UTC+00:00 | London, Dublin, Lisbon, Accra |
| UTC+01:00 | Paris, Berlin, Madrid, Lagos |
| UTC+02:00 | Cairo, Athens, Johannesburg, Kyiv |
| UTC+03:00 | Moscow, Istanbul, Riyadh, Nairobi |
| UTC+03:30 | Tehran |
| UTC+04:00 | Dubai, Baku, Tbilisi |
| UTC+04:30 | Kabul |
| UTC+05:00 | Karachi, Tashkent, Yekaterinburg |
| UTC+05:30 | Delhi, Mumbai, Colombo |
| UTC+05:45 | Kathmandu |
| UTC+06:00 | Dhaka, Almaty, Bishkek |
| UTC+06:30 | Yangon |
| UTC+07:00 | Bangkok, Jakarta, Ho Chi Minh City |
| UTC+08:00 | Shanghai, Singapore, Hong Kong, Perth, Manila |
| UTC+09:00 | Tokyo, Seoul, Pyongyang |
| UTC+09:30 | Adelaide, Darwin |
| UTC+10:00 | Sydney, Brisbane, Port Moresby |
| UTC+10:30 | Lord Howe Island |
| UTC+11:00 | Noumea, Solomon Islands |
| UTC+12:00 | Auckland, Fiji, Tuvalu |
| UTC+12:45 | Chatham Islands |
| UTC+13:00 | Nuku’alofa (Tonga), Apia (Samoa) |
| UTC+14:00 | Kiritimati (Line Islands, Kiribati) |
Whether the offset above holds all year depends on daylight saving.
| Market | Daylight saving? | Effect on schedules |
|---|---|---|
| United States (except Arizona, Hawaii) | Yes | Clocks move forward in the Northern summer |
| European Union, United Kingdom | Yes | Clocks move forward in the Northern summer |
| Australia (southern states), New Zealand | Yes | Clocks move in the Southern summer, opposite months |
| Chile, parts of South America | Yes | Southern summer shift |
| China, Japan, Korea, India | No | Same offset all year |
| Gulf states, most of Africa, Iran | No | Same offset all year |
Daylight saving. The offsets in the table are standard winter time. When a region moves its clocks forward for summer, its offset shifts by an hour. If you scheduled against a fixed offset instead of the named zone, the send drifts by an hour for part of the year.
Most of Asia, including China, Japan, Korea and India, plus the Gulf states, most of Africa and Iran. Their offset is the same all year. Within the US, Arizona and Hawaii also stay fixed.
A handful of zones sit on the half hour or quarter hour. India is UTC+05:30, Iran UTC+03:30, Afghanistan UTC+04:30, Nepal UTC+05:45 and the Chatham Islands UTC+12:45. Naive schedulers that assume whole-hour offsets get these wrong.
Store every timestamp in UTC and convert to the customer's local zone only when you display or send. That keeps records consistent and lets daylight saving be handled once, at the edge, by the named zone rather than a frozen offset.