Time Zone Converter
Pick a date, a time, and a source city, then add target cities to see the converted local time in each one.
Conversions use your browser’s built-in IANA time zone data and are DST-aware for the selected date.
How it works
- Choose the date and time you want to convert, then search for the source city or time zone it applies to.
- Add one or more target zones — each appears instantly with its local date, time, and a +1d or -1d marker when the day changes.
- Check the meeting-hours row to see which targets land inside 9:00–18:00, then press Copy summary to share the result.
Frequently asked questions
- Does the converter account for daylight saving time?
- Yes. Conversions use your browser’s built-in IANA time zone database through the Intl API, which knows the exact DST rules for every listed zone. That means a 15:00 meeting in New York converts differently in January than in July, and the tool handles it automatically for the specific date you pick.
- Why does a converted time show +1d or -1d next to it?
- The marker means the converted time falls on the previous or next calendar day relative to your source date. For example, 20:00 Monday in Los Angeles is already 13:00 Tuesday in Sydney, so Sydney shows +1d. It is an easy detail to miss when scheduling calls, which is why it is displayed explicitly.
- Is my data uploaded anywhere when I convert times?
- No. Everything runs locally in your browser using JavaScript’s Intl API — there are no network requests and nothing is stored on a server. You can even load the page, go offline, and keep converting times.
- How do I find a good meeting time across several time zones?
- Add every participant’s city as a target zone, then adjust the source time until the meeting-hours row shows all or most targets inside 9:00–18:00. Because results update live as you change the time, you can sweep through the day in a few seconds and spot the overlap window.
- Which time zones are available and what if my city is not listed?
- The list covers about 40 major IANA zones spanning every UTC offset in common use, labeled with well-known cities. If your exact city is missing, pick any listed city in the same zone — for example, choose New York for Boston or Berlin for Prague — and the converted result will be identical.
About this tool
This time zone converter answers a precise question: given a specific date and time in one city, what is the local date and time in other cities? Unlike a world clock, which only shows the current moment, it lets you plan ahead — a product launch next Tuesday at 10:00 in London, a call on the first Monday of March, a deadline set in another office’s local time. You choose the moment, the source zone, and as many target zones as you need, and every result updates live as you type.
All calculations happen in your browser using the Intl API and the IANA time zone database that ships with it. Nothing is sent to a server, which keeps the tool fast and private. The conversion is DST-aware for the exact date you select: the tool resolves your chosen wall-clock time in the source zone to an absolute instant, then formats that instant in each target zone, so daylight saving transitions, half-hour offsets like India’s UTC+5:30, and 45-minute offsets like Nepal’s are all handled correctly.
Each target row shows the weekday, date, time, and the zone’s current abbreviation, plus a +1d or -1d marker when the converted time crosses midnight into another calendar day — the single most common source of scheduling mistakes across large longitude gaps. A separate meeting-hours row tells you at a glance which targets fall inside a 9:00–18:00 working day.
Practical tip: when coordinating between three or more continents, fix the zone with the least flexibility as your source, add the others as targets, and nudge the source time in 30-minute steps until the overlap looks acceptable. Then use the Copy summary button to paste a clean, plain-text conversion table into an email or chat message.