What this does
Pick one moment in time and see the wall-clock reading for it in several places at once. Each row is a zone you choose, showing the local date and time on a 24-hour clock plus that zone's UTC offset at that instant. It is the tool for "when we say 3pm, what is that for everyone on the call?" — and for the reverse, reading a timestamp someone quoted from a city you don't live in. The conversion runs in your browser, so it works with the network off and no meeting details are sent anywhere.
How do I compare a meeting time across zones?
Set the moment once, then add a row per participant:
- Set the moment in the Source moment field, or press Use now to load the current time.
- Change any row's dropdown to the zone you care about. Rows update immediately.
- Press + Add zone for another row — it starts on UTC, so pick from its dropdown — or the × button to drop a row you no longer need.
Which time zone is the input in?
Your own. The source moment is read in your browser's local zone, so if you type 15:00 you are describing 3pm where you are sitting, and every row answers what that same instant looks like elsewhere. If you want to start from a zone you are not in, add UTC as a row first and use it as your anchor, or use one of the fixed-pair pages such as PST to EST, which read the time in the source zone instead.
Does it handle daylight saving?
Yes, and it is the main reason to use this rather than mental arithmetic. Offsets come from the IANA time zone database in your browser, evaluated for the date you entered rather than for today: a June date puts New York at UTC−4 and a December date at UTC−5, while zones with no daylight saving at all, like Kolkata and Dubai, stay put. It also covers the weeks when two countries disagree — Britain changes on the last Sundays of March and October, the US on the second Sunday of March and the first of November, so London and New York spend a few weeks a year four hours apart instead of five.
Which zones can I pick from?
A shortlist of 22 IANA zones: UTC; Los Angeles, Denver, Chicago, New York and São Paulo; London, Paris, Berlin and Athens; Cairo and Johannesburg; Dubai, Karachi, Kolkata, Bangkok, Singapore, Hong Kong, Shanghai and Tokyo; then Sydney and Auckland. Cities in the same zone share its rules, so Europe/Paris also covers Madrid, Rome and Amsterdam.
Why does an offset show as UTC+05:30?
Because not every zone is a whole number of hours from UTC. India runs at UTC+5:30, parts of Australia use half hours, and Nepal uses a quarter. The offset column prints hours and minutes rather than rounding, so you can see at a glance why a call lands at 6:30 for one participant.
What if I need a single fixed pair?
For a conversion you do over and over, the dedicated pages are quicker: UTC to EST, GMT to EST, IST to EST, UTC to IST, PST to EST and EST to PST. If you are starting from an epoch number instead of a clock reading, convert it with the timestamp tool first.