Time Zone Converter

Convert any date and time between all IANA time zones with automatic daylight saving handling — compare several destinations at once and line them up on a 24-hour timeline.

Convert between time zones
Pick a date and time, choose the source zone (your browser zone is preselected), and add as many destination zones as you need. Results update instantly and your zones are remembered for next time.

Defaults to your browser time zone; DST is handled automatically.

Time zone timeline
See a full day across all selected zones. Click any hour to align every zone to that moment.
Click an hour cell to align all zones.
UTC
New York
☀️ Work hours (08–18) 🌆 Evening (18–23) 🛏️ Night

About time zone conversion

Time zones keep civil clocks broadly aligned with daylight around the world. Coordinated Universal Time (UTC) is the shared reference from which every local offset is measured: a location at UTC plus nine is nine clock hours ahead of UTC, and one at UTC minus five is five hours behind. Converting between two places is therefore a two-step calculation — take the source wall-clock time back to UTC, then apply the destination offset. The hard part is that offsets are not constant. Dozens of regions observe daylight saving time (DST), moving their clocks forward in spring and back in autumn on dates that differ by country and sometimes by year. New York is UTC-05:00 in January but UTC-04:00 in July; London swings between UTC+00:00 and UTC+01:00; most of Asia never shifts at all. This converter uses the full IANA time zone database built into your browser, so every conversion is computed for the exact instant you enter — the correct standard or daylight offset is applied automatically, including on the transition days themselves. Because meetings rarely involve just two places, you can add any number of destination zones and read them side by side, with a +1 or -1 badge whenever a zone lands on a different calendar date. The timeline view goes one step further: it lays a full 24-hour day of every selected zone on one grid, colour-coded into working hours, evening, and night, so overlapping windows for a call across three or more regions stand out at a glance. Click any hour to pin that moment across all zones, and step the date forward or back to see how DST changes the alignment from one week to the next. All calculations run entirely in your browser using the same zone rules your operating system relies on, so results stay correct even as governments revise DST legislation over the years. Your source and destination selections are stored locally in your browser, so the tool reopens exactly as you left it.

Time zone conversion examples

These examples include same-day and date-crossing conversions with explicit offsets.

SourceDestinationExplanation
2026-01-15 14:30 UTC2026-01-15 23:30 TokyoTokyo standard time is nine hours ahead of UTC.
2026-01-15 08:00 Tokyo2026-01-14 15:00 Los AngelesThe 17-hour standard-offset difference crosses to the previous date.
2026-07-15 08:00 Tokyo2026-07-14 16:00 Los AngelesIn July Los Angeles observes PDT (UTC-07:00), one hour later than its winter time — applied automatically.
2026-03-10 12:00 London2026-03-10 17:30 DelhiDelhi is five hours and thirty minutes ahead of UTC.
2026-06-01 22:00 Paris2026-06-02 06:00 SydneyParis is on CEST (UTC+02:00) in June while Sydney is in southern winter (UTC+10:00), so the gap is eight hours and the result crosses midnight.

How to convert a time zone

  1. Check the source zone — it defaults to your browser's time zone. To change it, open the picker and browse by region or just type a city name.
  2. Enter the date and 24-hour time at the source location, or press Now for the current moment.
  3. Add destination zones with Add time zone; each row converts instantly and shows its live UTC offset, with a +1/-1 badge when the date differs.
  4. Scroll to the timeline to see the whole day across every zone, colour-coded by working hours, evening, and night.
  5. Click an hour cell to align all zones to that moment, and use the date controls to check other days — daylight saving changes are applied automatically.

Time zone converter FAQ

Does this converter apply daylight saving time?

Yes, automatically. Offsets are computed from the IANA time zone database for the exact instant being converted, so summer and winter times — and the transition days themselves — are always correct. No manual DST checking is needed.

What does UTC mean?

Coordinated Universal Time is the global reference clock. Every time zone is defined as an offset from UTC, such as UTC+09:00 for Tokyo or UTC-08:00 for Los Angeles in winter. UTC itself never observes daylight saving.

Why can the converted date be different?

Large offsets push the result across midnight. When it is Friday morning in Los Angeles it is already Friday evening in Tokyo, and a late-evening time can land on the next calendar day. The +1 and -1 badges flag exactly this.

How do I find a time that works across three or more zones?

Add every zone you care about, then use the timeline: green cells mark 08:00-18:00 working hours in each zone, amber marks evening. A column that is green (or at least amber) in every row is your meeting window; click it to read the exact local times.

Are my selected zones saved?

Yes. The source zone and all destination zones are stored in your browser's local storage and restored on your next visit. Nothing is sent to any server — all conversion happens locally.

Why do some zones have 30- or 45-minute offsets?

Offsets are political, not purely geographic. India (UTC+05:30), Iran, and parts of Australia use half-hour offsets, and Nepal uses UTC+05:45, typically to centre the clock on the region's solar time within a single national zone.