Time Zone Converter
Enter a date and time, choose the time zone it is in and see what the clock shows in as many other zones as you like, with each zone's offset from UTC and whether it is the previous or next day. Daylight saving is handled by the rules of each place on that exact date, and the two awkward cases are not hidden: a time that does not exist because the clocks skipped it, and a time that happens twice because the clocks went back. Everything runs in your browser.
Your browser's own time zone database is used, so very recent rule changes can be missing in an old browser.
Related Tools
[4 suggestions]Unix Timestamp & Epoch Converter
Convert Unix epoch timestamps to UTC and local dates, or convert human dates to Unix timestamps with auto-detection.
Developer & WebDays Between Dates Calculator
Count the days between two dates, with weeks, years, months and days, and the weekdays from Monday to Friday. Option to count the end date.
Student ToolsAge Calculator
Work out an exact age in years, months and days from a date of birth, with the next birthday and the age in months, weeks and days.
Student ToolsCron Expression Generator and Explainer
Paste a cron expression to read it in plain English, check each field and see the next ten run times.
Developer & WebAbout the Time Zone Converter
The time zone converter reads the date and time you type as a wall-clock time in the zone you pick, works out which moment that is, and shows what the clock reads in each other zone at that moment. It uses the time zone database built into your browser, which knows the daylight saving rules of every place for every year, so New York is UTC-05:00 in January and UTC-04:00 in July without you having to know. Two cases need care. When the clocks spring forward, a time such as 2:30 on 8 March 2026 in New York never happens, so the tool says so and uses the offset before the jump, as Python's zoneinfo does. When the clocks fall back, a time such as 1:30 on 1 November 2026 happens twice, so the tool lets you choose the first or the second. Zones with offsets such as UTC+05:30 in India, UTC+05:45 in Nepal and UTC+12:45 on the Chatham Islands are handled too. Input is read strictly: a date as year-month-day, a time as 24-hour hours:minutes, and impossible dates such as 29 February 2026 are reported. The results were compared with Python's zoneinfo on about 50,000 date-and-time and zone pairs in 56 zones between 2000 and 2035, with half of the cases within a day of a daylight saving change, including all the gaps and repeated hours, and match. Time zone rules change, so an old browser can lack a recent change. Everything runs in your browser and nothing is uploaded.
How do I convert a time from one time zone to another?▾
Find both zones' offsets from UTC on that date, subtract the first and add the second. For example, 09:00 in New York in July is UTC-04:00, so it is 13:00 UTC, and Tokyo at UTC+09:00 reads 22:00. The tool does it for you and knows the daylight saving rules for the date.
Why does a time sometimes not exist?▾
When the clocks spring forward, an hour is skipped. In New York on 8 March 2026 the clocks jump from 02:00 to 03:00, so 02:30 never happens. The tool flags it and uses the offset before the jump.
Why does a time sometimes happen twice?▾
When the clocks fall back, an hour is repeated. In New York on 1 November 2026 the hour from 01:00 to 02:00 happens twice, so you can choose the first or second 01:30 in the tool.
Which time zone database does it use?▾
The one built into your browser, which follows the IANA time zone database. Rules change from time to time, for example Morocco moving to permanent UTC+00 in September 2026, so an old browser can be missing a recent change.
Is my data uploaded?▾
No. The conversion runs in your browser, and what you type is not sent anywhere or stored.