Timezone Converter
Choose a moment in your own timezone and see what the clock reads at that same instant anywhere else in the world. Add as many cities as you need before scheduling a call.
Read as wall-clock time in your own timezone, then shown as the same instant elsewhere.
No timezones to compare
Pick a zone from the dropdown and press Add — or add your own timezone — and the same instant appears in every zone you choose.
How to Use
- Set the date and time. It is read as wall-clock time in your own device timezone, which is named beneath the field.
- Pick a timezone from the dropdown and press Add. The list comes from your browser's own IANA timezone database, so every zone your system knows about is available.
- Each row shows the same instant rendered in that zone, including the UTC offset that applies on that date.
- Remove any row you do not need, or copy the whole list to paste into a meeting invitation.
Features
- Full IANA zone list where the browser supports it, with a curated fallback list where it does not
- Daylight saving applied automatically for the specific date you choose
- Correct handling of half-hour and quarter-hour zones such as Kolkata, Adelaide, and Kathmandu
- Unlimited comparison rows, each with the UTC offset shown
- One-click copy of every converted time, and the underlying ISO instant for reference
Why Adding Hours Is the Wrong Way to Convert Timezones
The intuitive approach — "New York is five hours behind London, so subtract five" — fails several times a year. The offset between two places is not a constant. It depends on the date, because countries enter and leave daylight saving on different weekends. In the two weeks each March when the United States has sprung forward but Europe has not, London is four hours ahead of New York rather than five. Anyone who has joined a transatlantic call an hour early in late March has met this problem in person.
This converter never adds or subtracts an offset. It builds a single point in time — one instant, internally a Unix timestamp — and then asks the browser to render that same instant according to the rules of each named zone you selected. Those rules come from the IANA timezone database that ships with your operating system and browser, the same dataset that governs your system clock. It knows that Arizona does not observe daylight saving while the rest of Mountain Time does, that India sits at UTC+5:30 and Nepal at UTC+5:45, that Lord Howe Island shifts by thirty minutes rather than an hour, and that the southern hemisphere runs its transitions in the opposite season.
This is also why the tool uses region-and-city identifiers such as Europe/Paris rather than abbreviations such as CET. Abbreviations are ambiguous — CST is claimed by Central Standard Time in North America, China Standard Time, and Cuba Standard Time, three zones hours apart — and they cannot express a daylight saving rule on their own. One honest caveat about this page: the time you type is interpreted in your own device's timezone, not in a source zone you pick. If you want to start from a meeting time that was quoted to you in another city, convert that city's clock reading to your own first, or simply add both zones to the list and read across the row.
Frequently Asked Questions
Which timezone is my input read in?
Your device's own timezone, which is named under the date field. Every row below shows that same instant expressed elsewhere.
Does it handle daylight saving?
Yes, per date. Because the conversion is performed by the browser's timezone database rather than by fixed arithmetic, choosing a date in July and one in January will correctly produce different offsets for any zone that observes it.
Why are the timezones named after cities?
Because IANA identifiers such as America/New_York encode the full history of a region's rules, while abbreviations like EST or CST are ambiguous and cannot express when daylight saving starts and ends.
Why does my browser show a shorter list of zones?
The full list comes from an API that older browsers do not implement. When it is unavailable, the tool falls back to a curated list of around twenty major zones so it still works.
Is anything sent to a server?
No. The timezone rules already live in your browser, so the entire conversion happens locally and no meeting time you enter leaves your device.