Timezone Conversion Basics
Timezone conversion maps an instant in time between regional offsets and names, accounting for daylight saving rules.
Quick answer
Use IANA timezone names (America/New_York) not fixed UTC offsets alone—DST shifts offsets seasonally. Convert by instant: same moment displays different local clocks in Tokyo vs London. UTC is reference; local = UTC plus offset. Tools apply Olson timezone database rules automatically.
Overview
Global teams scheduling standups, webinar launches, and flight connections navigate timezone math daily. Saying '3 PM EST' without date fails across DST boundaries—March and November shift US Eastern offset between EST and EDT. Fixed offset +5:30 works for India (no DST) year-round; US cities need named zones. Calendar apps store UTC instants internally; UI converts for viewer locale. Manual offset arithmetic errors spike on DST transition Sundays when local hour repeats or skips—always convert concrete UTC instant or use timezone-aware library rather than memorized winter offset alone.
IANA names vs abbreviations
Prefer America/Chicago over CST abbreviation—CST also means China Standard Time. IANA database encodes historical DST rule changes governments announce sporadically.
UTC, Etc/GMT, and Z suffix in ISO strings interchangeably mark reference timeline for storage.
Daylight saving transitions
Spring forward loses local hour; fall back repeats hour—scheduling '2:30 AM' on fall back day may be ambiguous. Use UTC for cron jobs spanning DST.
Southern hemisphere DST opposite seasons—Sydney vs New York offset difference varies through year not constant.
Reliable conversion workflow
Step one: identify instant (UTC timestamp or complete ISO string with offset). Step two: format in target zone for display. Never add fixed 5 hours without checking DST on that calendar date.
Meeting invite should include UTC or dual cities: '15:00 UTC / 10:00 CT (Chicago)'.
ISO 8601 offsets in strings
2026-05-23T14:30:00-05:00 embeds offset explicitly—parser converts to instant without guessing zone name. Z means UTC.
Floating local time without offset ('2026-05-23T14:30:00') ambiguous—avoid in API contracts.
Common scheduling pitfalls
Assuming all US states observe DST—Arizona mostly exempt. Assuming global DST same dates—EU US differ.
Server cron in UTC misaligned with 'local midnight' job meaning—document which timezone defines business day cutoffs for analytics.
Examples
NYC to London meeting
10:00 America/New_York on 2026-06-15 → 15:00 Europe/London same instant (both on BST/EDT appropriately).
DST gap
US spring forward 2 AM → 3 AM—2:30 AM local does not exist that day; libraries shift or reject.
Common mistakes and edge cases
- Using fixed UTC-5 for New York year-round.
- Conflicting CST abbreviations across countries.
- Storing local time strings without offset in database.
- Scheduling recurring local time through DST without UTC anchor.
Related resources
Related tools
Last reviewed: 2026-05-23