About the Time Zone Converter
Scheduling across regions means answering "what time is 3pm UTC in New York, London, and Tokyo". This tool takes one moment, from a date and time you enter, and shows it in a list of time zones at once. Daylight saving is handled automatically by the browser's time-zone database, so the offsets are correct for the specific date, not just the current one.
Daylight saving creates two days a year where local time is not a straight line, and both are worth remembering. On the spring-forward day an hour never happens, so a local time of 02:30 does not exist and has to be normalised to something else. On the autumn day an hour repeats, so 01:30 occurs twice and a bare local time is genuinely ambiguous until you attach an offset. Zone rules also change by political decision rather than by any pattern, which is why storing the IANA name is safer than storing a fixed offset like +05:30.
Set the zones as a comma-separated list of IANA names, such as America/New_York or Asia/Kolkata. The input can include a zone (like "3pm UTC") or be interpreted as UTC. The usual job is finding a meeting slot that is not the middle of the night for anyone: enter one candidate time and read the local hour in every office at a glance. For a single timestamp in every standard form, use the Unix Timestamp Converter; to reformat the result for a calendar invitation, the Date Format Converter.
How to use
- Enter a date and time, optionally with a zone.
- List the target zones as IANA names in the toolbar.
- Read the time in each zone.
Common questions
- Is daylight saving handled?
- Yes. The offset is computed for the specific date, so summer and winter times are correct.
- What zone names do I use?
- IANA names such as Europe/Berlin, America/Los_Angeles, Asia/Tokyo.
- What if I do not specify the input zone?
- It is interpreted as UTC unless the text includes a zone or offset.