Time Zone Converter
Convert times between any two time zones worldwide.
About the Time Zone Converter
Convert any date and time between any two of the world's time zones instantly. The converter uses the full IANA time zone database, so every country, region, and territory is supported — and daylight saving time transitions are handled automatically based on the selected date.
How it works
Select your source date and time, choose the time zone it's in, then pick the target time zone. The converted result appears immediately. All calculations happen in your browser with no server round-trips needed.
Daylight saving time
DST rules vary by country and change year to year. The converter automatically applies the correct offset for the specific date you enter — so a summer conversion from London to New York will correctly use BST (UTC+1) and EDT (UTC−4), while a winter conversion will use GMT and EST.
UTC and time zone offsets
- UTC — the global baseline; all other zones are expressed as offsets from it
- UTC+1 (CET) — Central European Time (standard)
- UTC−5 (EST) — Eastern Standard Time (US & Canada)
- UTC+8 (CST) — China Standard Time / Singapore
- UTC+9 (JST) — Japan Standard Time
Common uses
Scheduling international calls and meetings, booking flights across time zones, coordinating remote teams, and verifying the local time of a past or future event in another country.
Daylight Saving Time and scheduling
Daylight Saving Time (DST) is one of the most common sources of scheduling bugs. Clocks in the UK move forward 1 hour in March and back in October. The US changes on different dates to the UK, creating a 3-week period each spring and autumn when the transatlantic time difference is 1 hour different from usual. Always store times in UTC in databases and convert to local time for display.
- UTC vs local time — always store in UTC; convert to local time only for display
- IANA timezone database — the authoritative source of timezone rules; used by all major programming languages
- DST transitions — clocks change at different times in different countries; the US-EU gap varies by 3 weeks each spring and autumn
- ISO 8601 with offset — 2025-06-01T14:30:00+01:00 is unambiguous; naked local times are ambiguous during DST transitions
Time zones in software development
Timezone handling is one of the most error-prone aspects of software development. Rules change (countries add, remove, or modify DST), historical data may be inaccurate, and the same city can be in different zones depending on the date. The IANA timezone database (also called the Olson database) is the authoritative source, updated several times per year.
- UTC everywhere — store all timestamps as UTC; convert to local time only at the display layer
- IANA database — always use IANA zone names (Europe/London) not fixed offsets (+00:00); offsets change with DST
- Moment.js vs date-fns vs Temporal — Moment is deprecated; date-fns or Luxon are current recommendations; the JavaScript Temporal API is the future standard
- Database storage — PostgreSQL TIMESTAMPTZ stores UTC correctly; MySQL TIMESTAMP has a 2038 limit