Timezone Converter

Compare city times instantly to plan meetings across zones

Reference time

UTC

Fri, Jun 12, 2026, 10:38 PM

UTC+0.0

UTC

Fri, Jun 12, 2026, 10:38 PM

UTC+0.0

America/New_York

Fri, Jun 12, 2026, 06:38 PM

UTC-4.0

Europe/London

Fri, Jun 12, 2026, 11:38 PM

UTC+1.0

Asia/Tokyo

Sat, Jun 13, 2026, 07:38 AM

UTC+9.0

How it works

Timezone Converter — Compare city times instantly to plan meetings across zones. All processing happens in your browser — no upload, no signup, no email required. Free forever.

Last updated: 2026-05-06

Editor's note

The DST hour-shift week is where most converters fail in spectacular ways — a meeting that was at 14:00 last week silently slides to 13:00 or 15:00 and nobody notices until somebody joins an empty call. We use the IANA time zone database, which means "America/New_York" follows the actual rule change in spring and autumn, not a hardcoded UTC offset. The same week is where we got the most user reports on our previous version, and IANA is the only sustainable answer.

We translate the city labels in the UI but never the IANA IDs underneath, on purpose. Localizing "Europe/Istanbul" to a translated zone name would be friendly until someone copies the value into a calendar invite or a cron expression, where it has to be the IANA string verbatim. The source of truth and the friendly label are two different things, and we keep them visibly different so power users can copy the right one.

About Timezone Converter

Scheduling meetings across continents, watching a livestream that publishes local times, or coordinating with a remote teammate all hinge on one infuriating question: "what time is that for me?" The timezone converter answers it for as many cities as you want at once. Pick a reference time and a list of zones; each zone shows the equivalent local moment, with daylight-saving offsets applied automatically using the browser's IANA timezone database — the same database your operating system relies on for its own clocks.

Behind the scenes, every entry points to an IANA zone name like Europe/Istanbul, America/New_York, or Asia/Tokyo. Those names encode the full DST history and rules for that locale, so when you set a reference time of 14:00 on a date that lies inside European summer time, London shows BST (UTC+1) instead of GMT (UTC+0), and the conversion to New York shifts by 4 hours instead of 5. Move the reference time across a DST boundary and the offsets re-evaluate live.

A typical use case: you are in Istanbul (UTC+3 year-round) and need to find a 30-minute slot that works for colleagues in London, San Francisco, and Singapore. Add all four zones, scrub the reference time, and look for an hour where every city sits inside a tolerable working window. The list updates instantly so you can find the overlap without doing arithmetic in your head.

How to use Timezone Converter

Set the Reference time using the date and time inputs at the top, or click Now to snap to the current moment.
Click Add zone and search for a city or IANA zone name ("Tokyo", "Asia/Tokyo", "London").
Repeat for every additional zone you want to compare — there is no hard limit.
Read each row to see the equivalent local time, day of week, and date in that zone.
Click the X next to a zone to remove it; click Now again any time to reset the reference to the present.

Common use cases

Scheduling a recurring sync between teams in San Francisco, Istanbul, and Bangalore.
Confirming the local airing time of a US sports broadcast or game launch in your country.
Coordinating a video interview with a candidate in another hemisphere where DST runs in reverse.
Planning a phone call to family abroad without waking them up at 3 a.m.
Verifying contract deadlines that specify a city — "by 17:00 New York time on the 15th" — from your own timezone.

Tips & common mistakes

DST changes happen on different weekends in different countries — Europe ends summer time the last Sunday of October, the US the first Sunday of November. Pick the actual meeting date as your reference, not just today's date.
Some regions opted out of DST entirely (Arizona, most of Australia's tropical north, all of Türkiye since 2016). The IANA database knows the rules, so a 'flat' zone simply does not shift.
If you only see UTC offsets in your output, double-check that you searched for a city zone (Asia/Singapore) rather than a deprecated three-letter abbreviation (SGT).
Save your zone list as a browser bookmark if you reuse the same set of cities — the tool keeps the zones in the URL fragment so the bookmark restores them.

Frequently asked questions

Are zones automatic for daylight saving time?

Yes. We use the browser's IANA timezone database, so DST transitions (e.g. summer time) are handled correctly for every zone.

How accurate is the displayed offset?

It's exact for the reference time you set. Offsets change across DST boundaries — moving the reference forward an hour may shift a zone from UTC+1 to UTC+2.

Where are the zone names from?

We list IANA zone names (like 'Europe/London' or 'Asia/Tokyo'). The browser's Intl.supportedValuesOf returns its full set on modern devices.

Why are some country names missing from the search?

We list IANA zones, which are city-based rather than country-based, because many countries (Russia, the US, Australia) span multiple zones. Search by capital or major city instead — Asia/Riyadh for Saudi Arabia, Europe/Berlin for Germany.

What happens if I pick a date during a DST 'spring forward' gap?

The hour 02:00–03:00 on the spring-forward date does not exist locally. The browser snaps the reference to the next valid moment, so the displayed local time may be one hour later than what you typed for the affected zone.

Can I see UTC explicitly?

Add the IANA zone 'UTC' or 'Etc/UTC' from the search box. It never shifts and is useful as a stable anchor when several zones are in flux around a DST boundary.