Time Zone Converter
See one instant across every major time zone at once, with the offset that actually applied on that date.
| Asia/Seoul | Friday, July 31, 2026 at 11:22:52 PM GMT+9 | UTC+09:00 | — |
|---|---|---|---|
| UTC | Friday, July 31, 2026 at 2:22:52 PM UTC | UTC+00:00 | −9h |
| Asia/Tokyo | Friday, July 31, 2026 at 11:22:52 PM GMT+9 | UTC+09:00 | — |
| Asia/Shanghai | Friday, July 31, 2026 at 10:22:52 PM GMT+8 | UTC+08:00 | −1h |
| Asia/Hong_Kong | Friday, July 31, 2026 at 10:22:52 PM GMT+8 | UTC+08:00 | −1h |
| Asia/Singapore | Friday, July 31, 2026 at 10:22:52 PM GMT+8 | UTC+08:00 | −1h |
| Asia/Kolkata | Friday, July 31, 2026 at 7:52:52 PM GMT+5:30 | UTC+05:30 | −3.5h |
| Asia/Dubai | Friday, July 31, 2026 at 6:22:52 PM GMT+4 | UTC+04:00 | −5h |
| Europe/London | Friday, July 31, 2026 at 3:22:52 PM GMT+1 | UTC+01:00 | −8h |
| Europe/Paris | Friday, July 31, 2026 at 4:22:52 PM GMT+2 | UTC+02:00 | −7h |
| Europe/Berlin | Friday, July 31, 2026 at 4:22:52 PM GMT+2 | UTC+02:00 | −7h |
| Europe/Madrid | Friday, July 31, 2026 at 4:22:52 PM GMT+2 | UTC+02:00 | −7h |
| Europe/Moscow | Friday, July 31, 2026 at 5:22:52 PM GMT+3 | UTC+03:00 | −6h |
| America/New_York | Friday, July 31, 2026 at 10:22:52 AM EDT | UTC-04:00 | −13h |
| America/Chicago | Friday, July 31, 2026 at 9:22:52 AM CDT | UTC-05:00 | −14h |
| America/Denver | Friday, July 31, 2026 at 8:22:52 AM MDT | UTC-06:00 | −15h |
| America/Los_Angeles | Friday, July 31, 2026 at 7:22:52 AM PDT | UTC-07:00 | −16h |
| America/Sao_Paulo | Friday, July 31, 2026 at 11:22:52 AM GMT-3 | UTC-03:00 | −12h |
| Australia/Sydney | Saturday, August 1, 2026 at 12:22:52 AM GMT+10 | UTC+10:00 | +1h |
| Pacific/Auckland | Saturday, August 1, 2026 at 2:22:52 AM GMT+12 | UTC+12:00 | +3h |
Why the offset depends on the date
A zone is not a fixed offset. New York is UTC−5 in January and UTC−4 in July, and the switch dates have moved several times over the years. Converting with today's offset therefore gives the wrong answer for a meeting last spring.
This tool resolves the offset for the specific instant you enter, using the browser's IANA time zone database — the same data the operating system uses.
Scheduling across zones
Pick a reference zone and every other row shows the difference from it, so "14:00 my time" becomes readable for everyone at once.
When you write the time down afterwards, write the UTC value too. "3pm Tuesday" is ambiguous the moment it crosses a border; "2024-06-18T06:00Z" is not.
Frequently asked questions
Why does it not use city names like EST or PST?
Abbreviations are ambiguous — IST is India, Ireland and Israel — and they do not carry daylight-saving rules. IANA identifiers like America/New_York do.
How do I convert a past or future date?
Type it in: an ISO 8601 string, a Unix timestamp, or "now". The historically correct offset for that date is applied.