Convert time between different time zones worldwide.
The Timezone Converter converts a date and time from any city or region to as many other time zones as you like, using the IANA time zone database built into your browser. Daylight saving time is applied correctly for the date you pick, so a meeting in March or November converts accurately, and each result shows the local time, the UTC offset and the zone abbreviation.
Made for everyone. Typical uses:
At 9:00 on Monday 5 October 2026 in New York (UTC-04:00) it is 14:00 in London, 18:00 in Karachi, 18:30 in Kolkata and 22:00 in Tokyo, and already 00:00 on Tuesday in Sydney. Make it 9:00 on 15 January 2027 and Karachi is ten hours ahead of New York instead of nine, because New York has moved to standard time.
It follows the time zone rules built into your browser, which are updated with your browser, and future dates use today's rules. A clock time that is skipped when clocks jump forward is flagged and moved to the next valid time. A clock time that happens twice when clocks go back is not flagged, and the tool uses one of the two, so write the offset into invitations for events near a change.
Accuracy: Conversions use well-known methods and are tested with real sample inputs. Check the output before you send or publish it.
Expert Tip
Name zones by city, not by abbreviation. CST can mean US Central, China or Cuba Standard Time, and IST can mean India, Israel or Irish Summer Time, but America/Chicago and Asia/Kolkata are unambiguous.
The Timezone Converter takes a date, a time and the time zone that clock time belongs to, and shows what the same moment is on the clocks of other places. It starts with today's date, the current time and your own time zone, and it comes with New York, London, Karachi and Tokyo already added. You can remove any of them or add more from the full list of time zones. Each row shows the local time, the date, a "+1 day" or "-1 day" marker when the date differs, the zone abbreviation and its offset from UTC. Zones are named by city, such as America/New_York or Asia/Kolkata, which is how the browser's time zone database identifies them.
Take 9:00 in the morning on Monday 5 October 2026 in New York, which is on daylight time at UTC-04:00. The converter shows these times for the same moment:
Run the same 9:00 meeting in New York in mid-winter, on 15 January 2027, when New York is on standard time at UTC-05:00. London is at UTC+00:00 and shows 14:00. Karachi shows 19:00 and Tokyo 23:00, one hour later than in October, because Pakistan and Japan do not change their clocks. Sydney is on summer time and shows 01:00 on 16 January. So New York and Karachi are nine hours apart in October and ten hours apart in January. The difference matters most in the weeks when two countries change their clocks on different dates. In 2026 the United States moved its clocks on 8 March and the United Kingdom on 29 March, so at 15:00 in London on 15 March it was only 11:00 in New York, four hours earlier. On 29 March, at the same London time, New York showed 10:00, five hours earlier.
When clocks jump forward, one hour of local time is skipped. In New York, 02:30 on 8 March 2026 never happened. If you enter it, the tool shows an amber notice and moves the time to the next valid one, 03:30 daylight time, so the other rows are based on a time that really occurred. When clocks go back in autumn, an hour happens twice. In New York, 01:30 on 1 November 2026 occurs once on daylight time and again on standard time. The tool does not warn about that case and uses one of the two, so for an event scheduled close to a change, write the offset in the invitation or choose a time outside the 1 a.m. to 3 a.m. window.
Pick the time in the zone of the person who is least flexible and let everyone else convert from it. Name zones by city instead of by abbreviation, because abbreviations are ambiguous: CST can mean US Central, China or Cuba Standard Time, and IST can mean India, Israel or Irish Summer Time. Check the date as well as the time, because the "+1 day" marker is the one most people miss when they plan a call between Asia and the Americas.
The conversions use the IANA time zone database built into your browser, and it is updated when your browser is updated. A government that changes its daylight saving rules at short notice can make an old browser show the wrong offset for future dates, and a date far in the future is converted using today's rules, because the rules for 2040 are not yet known. Nothing you enter is sent anywhere.
When a system gives you a raw number instead of a clock time, the Unix Timestamp Converter turns it into a UTC date. The Cron Parser shows when a scheduled job will next run in the zone you choose, the Days Between Dates calculator counts the days between two calendar dates, and the Date Validator checks that a date is real before you use it.
Explore more in Converters, read the guides and articles, or see how we test our tools.
Convert Unix timestamps to human-readable dates and times.
Best for reading a raw epoch timestamp from an API response or server log into an actual date
Parse and understand cron expressions with human-readable descriptions.
Best for confirming a scheduled job in a server crontab actually runs when you think it does before deploying it
Calculate the exact number of days, months, and years between any two dates.
Best for counting the days until a holiday, exam or deadline
Validate date strings for correct format, leap years, and logical validity.
Best for validating a user-submitted birthdate in a signup form before saving it