TZ
Time Zone Converter
Convert a specific date and time between any two time zones, with full daylight saving awareness — perfect for scheduling cross-border calls.
More Time & Clocks Tools
Uses IANA time zone database via your browser's Intl API — DST-aware per date. No server requests needed.
How to Use Time Zone Converter
Select your source and target time zones from over 50 common IANA zones grouped by region, pick a date and time, and see the converted result instantly. The converter accounts for each zone's daylight saving rules automatically.
About Time Zone Converter
Time zones are one of those things that sounds simple — the Earth rotates, the sun reaches its highest point at a different moment in different longitudes, so local noon is offset from Greenwich Mean Time — until you actually need to schedule something across them, at which point daylight saving time, half-hour offsets, date-line wrapping, and the fact that not every country observes DST on the same Sunday all combine to make a manual calculation surprisingly error-prone. The standard rule of thumb — add or subtract the offset — works only if you happen to know the correct offset for both locations on that specific date, which itself changes twice a year in most of Europe and North America, sometimes on different weekends.
This converter handles that for you. You pick two IANA time zones (e.g., 'Europe/London' and 'America/Los_Angeles'), enter a date and time in the source zone, and the tool tells you what the clock reads at that same moment in the target zone, using your browser's built-in Intl.DateTimeFormat engine — the same engine that powers the date and time display in every modern operating system — to look up the correct UTC offset for each zone on the entered date, including whether daylight saving is in effect. This means the result reflects the real-world, date-specific offset, not a fixed annual average.
The time zone list is drawn from the IANA Time Zone Database (also called tzdata or the Olson database), the same canonical list used by Linux servers, cloud platforms, smartphones and every major programming language's standard library. The list shown in the dropdown includes the most commonly searched cities and regions grouped by continent, with the IANA identifier (e.g., 'America/Chicago') alongside a human-readable label that includes the city name and standard time abbreviation. You can also type to filter the list — typing 'london' will narrow the options to Europe/London and any other zone with 'London' in the label — to avoid scrolling through the full list.
All of this runs entirely in your browser. The converter uses the Intl API built into the browser's JavaScript engine — no server request, no API call to an external time zone service, no data leaving your device. The time zone database used for the offset lookup is the one bundled with your browser, which typically updates through normal browser updates every few months to reflect the latest DST rule changes (which countries do occasionally change, sometimes on short notice).
Details & Tips
How the conversion works:
1. You enter a date and time — e.g., 15 July 2026 at 14:00 — and select 'Europe/London' as the source zone.
2. The converter constructs a UTC timestamp from that input using your browser's Intl.DateTimeFormat, which knows the UTC offset for Europe/London on 15 July (BST, UTC+1, because the UK is on summer time in July).
3. It then formats that same UTC timestamp to display the local time in the target zone — e.g., 'America/New_York' — giving you 09:00 EDT (UTC−4) for the same moment.
Worked example: a meeting scheduled for 14:00 in London on 15 July.
• Source: Europe/London at 14:00 BST (UTC+1).
• UTC equivalent: 13:00 UTC.
• Target: America/New_York at 13:00 UTC → 09:00 EDT (UTC−4).
• Same moment, two different clock readings — the converter does this automatically.
Time zone list (selections from IANA):
• Africa: Cairo, Johannesburg, Lagos, Nairobi, Casablanca
• America: New York, Chicago, Denver, Los_Angeles, Anchorage, Honolulu, Mexico_City, Toronto, Vancouver, Sao_Paulo, Buenos_Aires, Santiago
• Asia: Tokyo, Shanghai, Hong_Kong, Singapore, Seoul, Bangkok, Jakarta, Manila, Kolkata, Mumbai, Dubai, Tehran, Baghdad, Jerusalem, Karachi, Kathmandu
• Atlantic: Bermuda, Azores
• Australia: Sydney, Melbourne, Brisbane, Adelaide, Perth
• Europe: London, Paris, Berlin, Rome, Madrid, Amsterdam, Brussels, Vienna, Zurich, Stockholm, Oslo, Copenhagen, Helsinki, Warsaw, Prague, Budapest, Bucharest, Athens, Istanbul, Moscow, Kyiv, Lisbon, Dublin
• Pacific: Auckland, Wellington, Fiji, Guam
Edge cases handled automatically:
• Same source and target zone → the result matches the input time exactly (plus the zone abbreviation).
• Date-line crossings: converting from Auckland (UTC+12/+13) to Honolulu (UTC−10) correctly shows the date shift (e.g., 09:00 Tuesday in Auckland is 11:00 Monday in Honolulu).
• Half-hour and quarter-hour offsets are handled correctly (e.g., India at UTC+5:30, Nepal at UTC+5:45).
• Empty date or time inputs show '—' rather than a broken conversion.
• The converter is DST-aware: it looks up the offset in effect on the specific date you enter, not a fixed annual average, so a date in July (UK summer) and a date in January (UK winter) will correctly show BST and GMT respectively.
Frequently Asked Questions
How accurate is the time zone converter?
It uses your browser's built-in Intl.DateTimeFormat API, which draws from the IANA Time Zone Database — the same canonical source used by operating systems, servers and smartphones worldwide. The result reflects the real UTC offset in effect on the specific date you enter, including daylight saving rules.
Does the converter account for daylight saving time (DST)?
Yes. It looks up the offset for each selected time zone on the specific date you enter, so it correctly applies BST instead of GMT for a UK date in July, and EST/EDT rules for US dates according to the current DST schedule. It does not assume a fixed annual offset.
What if the two time zones use different DST start and end dates?
The converter handles this automatically. Each IANA zone has its own DST transition rules encoded in the tzdata database, and the converter queries each zone independently for the date you enter — it does not assume both zones switch on the same day.
Why does the same UTC time show different dates on different days?
Time zone conversion can cross the International Date Line. For example, 09:00 on Tuesday in Auckland (UTC+12) is 11:00 on Monday in Honolulu (UTC−10) — the local clock time moves backward and the date shifts by a day. This is correct behaviour, not a bug.
What time zones are available in the dropdown?
The converter shows over 50 common IANA time zones grouped by continent, covering major cities and regions worldwide. You can type to filter the list rather than scrolling — typing "london" will show Europe/London and any other match.
Can I convert historical dates, like what time it was in another zone in 1990?
Yes, as long as the IANA time zone database in your browser includes the DST rules for that period. The tzdata database includes historical DST transitions going back decades for most zones, so a date in the 1990s or 2000s should convert correctly. Very old dates (pre-1970s in many zones) may use simplified rules.
What happens if I leave the date or time field empty?
The converter shows "—" for the result when either field is empty, rather than attempting a partial or default conversion that could be misleading. Fill in both fields to see the converted time.
Does this tool need an internet connection to work?
No. The conversion runs entirely in your browser using the built-in Intl API — no server request, no external time zone API call. Once the page loads, the converter works offline.
Is my selected date or time sent to a server?
No. The conversion runs entirely in JavaScript in your browser — the date, time and time zone selections are never transmitted, logged, or stored anywhere.
What is the difference between UTC offset and time zone?
A UTC offset (like UTC+2) says how far ahead of Greenwich a clock is at a particular moment. A time zone (like Europe/Bucharest) is a geographic region that may have different offsets at different times of year — Bucharest is UTC+2 in standard time (EET) and UTC+3 in summer (EEST). This converter uses full IANA time zones, not fixed offsets, so it applies the correct offset for the specific date you enter.
Why does India show as UTC+5:30 instead of a whole-hour offset?
Several countries use half-hour or quarter-hour offsets — India (UTC+5:30), Iran (UTC+3:30), Nepal (UTC+5:45), parts of Australia (UTC+9:30 in Adelaide) — typically because they chose an offset based on their actual geographic longitude rather than rounding to the nearest hour. The converter handles these fractional offsets correctly.
Part of These Collections
Also Available As
time zone converter, timezone converter, convert time zones, international time converter, dst converter, world time converter
Explore More Tools
View all toolsFound a Problem?
Let us know if something with Time Zone Converter isn't working as expected.
Something went wrong. Please try again.
Thanks — we'll take a look.