How to use it
- Choose the date and time. Your own time zone and the current time are filled in automatically; “Now” resets to the current time.
- Choose the time zone that the date and time belong to.
- Read the same moment in each listed zone, with its UTC offset and abbreviation. A note shows when the date there is a day earlier or later.
- Add zones by typing a city or IANA name, remove the ones you do not need, and use “Copy all” to paste the list into an invitation.
How it works
The converter uses the IANA time zone database built into your browser, the same data your operating system uses for its clock. Zones are named by region and city, for example America/New_York or Asia/Kolkata, because abbreviations like CST or IST are ambiguous (IST can mean India, Ireland or Israel Standard Time).
The offset is worked out for the specific date you enter, so a meeting in July uses summer time and one in January uses winter time. Countries change their rules from time to time; results are as current as your browser's tz data. Offsets that are not whole hours, such as UTC+05:30 in India, UTC+05:45 in Nepal or UTC+12:45 in the Chatham Islands, are handled exactly.
Two moments each year need care. When clocks spring forward, a local time such as 02:30 does not exist; the tool moves it forward by the size of the jump and says so. When clocks fall back, a time such as 01:30 happens twice; the tool uses the first one and says so. Times are formatted in the style of the language you are browsing in. Your list of extra zones is remembered in this browser only.
Examples
Scheduling a call between New York and India
9:00 on 15 January 2026 in America/New_York (EST, UTC−05:00) is 19:30 the same day in Asia/Kolkata (UTC+05:30). In July, with New York on EDT, the same 9:00 is 18:30 in India: the gap changes because only one side uses daylight saving time.
Crossing the date line
18:00 on Friday in America/Los_Angeles is 15:00 on Saturday in Pacific/Auckland during the northern winter. The Auckland row shows “tomorrow” so you do not book the wrong day.
Converting a server log time
A log entry says 2026-03-29 01:30 UTC. Choose UTC as the source and add Europe/Berlin: it shows 03:30 CEST, because Germany switched to summer time at 01:00 UTC that morning.
Frequently asked questions
Does it handle daylight saving time?
Yes. Each conversion uses the offset in force on the date you entered, in both the source and the target zones, based on your browser's time zone database.
Why are some cities shown as “GMT+5” instead of a short name?
Many zones have no widely used abbreviation in your language. The browser then shows the offset instead, and the tool always lists the exact UTC offset as well.
What is the difference between UTC and GMT?
For converting clock times they are the same: UTC±00:00. GMT is also the winter time zone of the United Kingdom, which switches to BST (UTC+01:00) in summer, so “London time” and “GMT” differ for half the year.
Why can't I find my city?
The IANA database lists one representative city per region with the same clock history, for example Europe/Berlin also covers most of Germany. Pick the city in the same country or the same offset, or type a name like Asia/Kolkata directly.
Privacy
Conversions run in your browser using its built-in time zone data. Your time zone is detected locally and not sent anywhere. The list of extra zones you add is saved only in this browser's local storage.