Converters

Time Zone Converter

Pick a date, a time, and two time zones to convert between them — plus see that exact moment in all 20 supported cities at once. Daylight saving time is handled automatically using your browser's built-in time zone database, so conversions are correct for the specific date you choose, not just a fixed offset.

Daylight saving time is handled automatically by your browser's time-zone database for the exact date you pick — always double-check around DST switch weekends.

Why the date matters, not just the time

Time zone offsets change through the year. New York is UTC−5 in January but UTC−4 in July; London is UTC+0 in winter and UTC+1 in summer. Worse, the switch dates differ — the US changes in March and November, Europe in late March and late October — so the New York–London gap is usually 5 hours but drops to 4 for a couple of weeks each year. That's why this converter asks for a full date and computes the offset for that exact day.

Zones that skip DST or use odd offsets

Plenty of places never change their clocks: Arizona (mostly), Hawaii, Japan, China, India, and Singapore among them. India runs on a half-hour offset (UTC+5:30), and China spans five geographic zones but uses a single national time. Meanwhile southern-hemisphere zones like Sydney observe DST in the opposite season — the Sydney–New York gap swings between 14 and 16 hours across the year. Rules also change by government decree, which is why date-aware databases beat memorized offsets.

Scheduling across zones without mistakes

State the city alongside the time ('3 pm New York time'), not an abbreviation — 'CST' alone can mean Central US, China, or Cuba time. For recurring international meetings, anchor the time in one named city and let everyone else's local time float with DST changes; that's what calendar apps do internally, and it's the behavior this converter mirrors.

How to use this converter

Pick the source city and time, choose a target city, and set the date — the date is essential because the offset depends on whether daylight saving is active that day. Below the direct conversion, a table shows the same instant in all 20 supported cities, which is the fastest way to find a meeting slot that works across several regions at once.

A worked example

Schedule a call for 9:00 am in New York on July 15. Because both New York (UTC−4 in summer) and London (UTC+1 in summer) are on daylight time, the gap is 5 hours, so it's 2:00 pm in London and 6:30 pm in Mumbai (UTC+5:30, no DST). Move the same 9:00 am call to January and New York shifts to UTC−5 while London returns to UTC+0 — still 5 hours — but the Sydney gap changes, because Sydney runs DST in the opposite season.

FAQ

Does this handle daylight saving time?

Yes — conversions use your browser's IANA time zone database, which applies the correct offset for the exact date you pick, including DST switch days.

Why is the New York–London difference sometimes 4 hours instead of 5?

The US starts DST in mid-March but Europe waits until late March (and they end at different times in fall), so for a few weeks a year the usual 5-hour gap shrinks to 4.

Which zones don't observe daylight saving?

Japan, China, India, Singapore, Hawaii, and most of Arizona keep the same offset year-round, among many others. Their clocks never shift, so only your side of the conversion changes.

What happens if I pick a time that doesn't exist on a DST switch day?

During the spring-forward hour (like 2:30 am on the US switch date), clocks skip ahead — the converter resolves it to the nearest valid moment, which is standard behavior.

Is my data stored anywhere?

No. The conversion runs entirely in your browser using its built-in time zone data — nothing is sent to a server.

More free tools