Time zone table for developers — one instant in 61 zones

How to use Timezone Dev

1. Set Date and time. It starts at the current time.
2. Choose the zone that time belongs to in …in time zone. A server log in UTC stays on UTC; a meeting set in Mumbai uses India (Kolkata).
3. Optionally type in Filter to narrow the rows: a region such as Asia, a city, an offset such as +05:30, or next day. Every word must appear somewhere in the row.
4. Read the table. The UTC time is shown on top, and the rows can be downloaded as timezones.csv.

What it does and when to use it

Developers deal with time zones at awkward moments: reading a stack trace stamped in UTC, choosing a release window that avoids business hours in three regions, or setting a cron job that must fire at 09:00 in Sydney on a UTC server. This page answers “what time is it there?” for many places at once, with IANA names such as America/Sao_Paulo that you can paste into code or a TZ variable.

When you have a timestamp rather than a wall time, start with the Unix timestamp converter. To write a cron line once you know the UTC hour, use the Cron Generator.

How it works

Your input is read as a wall-clock time in the chosen zone and turned into one UTC instant. For each zone, the browser’s Intl.DateTimeFormat gives the local date and time at that instant. The offset is the difference between that local time and UTC. Rows are sorted from the most negative offset (Honolulu, UTC−10) to the most positive (Kiritimati, UTC+14).

Worked examples

Odd offsets. Noon UTC on 15 January 2026:

Kathmandu | Asia/Kathmandu | 2026-01-15 17:45 Thu | UTC+05:45 | same day
Auckland  | Pacific/Auckland | 2026-01-16 01:00 Fri | UTC+13:00 | next day

Kathmandu sits on a 45-minute offset, and Auckland is already on Friday.

The DST mismatch week. 15:00 in New York on 30 March 2026, filtered by europe. The UTC line reads 2026-03-30 19:00, and London shows 20:00 Mon | UTC+01:00. The US changed its clocks on 8 March and Europe on 29 March, so the usual five-hour gap was only four hours in between.

Who has crossed midnight? 23:00 UTC filtered by +05: returns three rows, all marked next day, including India at 2026-10-09 04:30 Fri.

Limits and tips

• In the autumn overlap, a repeated hour such as 01:30 in New York is read as the first one (daylight time).
• Offsets are only as current as your browser’s time zone data; very old browsers may miss recent rule changes.
• Store instants in UTC and convert only for display. For differences between two moments, see Timestamp Diff; for display formats, see Date Format Calc.
• For other places, try the World Clock.