Time Zone Converter
Convert a date and time across time zones, with correct daylight-saving handling — including wall-clock times that do not exist on that date.
About this tool
Converting a time across zones is arithmetic — until daylight saving gets involved. Twice a year, in every zone that observes it, the mapping between wall-clock time and real time stops being one-to-one: one hour is skipped on the way in, and repeated on the way out.
That is where most converters quietly give you a wrong answer. If you ask what 02:30 on the transition date is in another zone, and 02:30 never happened, a naive converter still returns a number. This one tells you the time does not exist, shows you the closest real moment instead, and flags the case where a time happens twice.
Everything is computed in your browser using the time zone data built into your system, so results follow IANA updates rather than a table frozen into this page.
How DST is recognised without a built-in rule table
Summer time is inferred from the offsets themselves: the smaller of a zone’s January and July offsets is its standard time, and any instant whose offset is larger is flagged as daylight saving. No transition dates are hard-coded, so the badge follows the system’s zone data.
A rule table is a liability. Transition dates are set by governments and change with a few months’ notice; a table baked into a page is wrong the moment it is written. So this tool never asks when the clocks change. It asks what a zone’s offset is in the coldest and the warmest month of the year.
The smaller of the two numbers is standard time, because daylight saving only ever pushes the clock forward. That reasoning holds north and south of the equator alike — a southern-hemisphere zone simply has its larger offset in January instead of July — so one rule covers every zone in the list.
Take London: UTC+00:00 in January, UTC+01:00 in July. Standard time is therefore +00:00, and any instant reading +01:00 wears the DST badge. When a government changes its rules, your browser’s updated zone data flows straight through and the badge is right again.
How the tool spots a wall-clock time that happens twice
It converts your time, then converts the instant one hour earlier. If both land on the same wall clock, the clock must have been set back in between — so that reading happens twice, and the earlier occurrence is shown.
The two daylight-saving failures look alike and are not. A time that does not exist is caught during the conversion itself: the wall-to-instant step reports that the clock skipped over it. A time that happens twice leaves no such trace — both of its instants are perfectly valid, so nothing in the conversion complains.
Repetition is found by comparison instead. The tool converts your time to an instant, shifts that instant back one hour, and asks what the wall clock reads then. If it still reads the same hour and minute, the hour was repeated, and a warning says so.
By then the tool has already committed to one of the two instants — the earlier — and every row in the table is built from it. That is why the notice is a warning and not a question: the conversion is complete and consistent, it just may not be the occurrence you had in mind.
Why the weekday is recomputed instead of read from the data
A time you type and a time the tool computes arrive in different shapes, and only one of them carries a weekday. Rather than trust a field that may be empty, the day of the week is derived from the year, month and day themselves.
There are two ways a date enters this tool: you can type one into the picker, or it can come from the clock. The computed kind arrives with the weekday already attached; the typed kind is built from five digits and has no weekday at all.
Reading a missing weekday does not fail loudly. It leaves a small gap — an empty pair of brackets here, a stray comma there — that is easy to dismiss as a styling glitch. So the tool ignores the attached value entirely and works the weekday out from the date, which gives the same answer either way.
The upshot is that both paths render an identical line, and no caller has to remember to fill the field in. A date and its weekday cannot disagree, because the second is always calculated from the first.
Which CST? Why time-zone abbreviations are not identifiers
CST alone can mean China Standard Time (UTC+8), North American Central Standard Time (UTC−6), or Cuba Standard Time (UTC−5) — up to thirteen hours apart. IST has three meanings too, and BST has two. "3pm CST" in an email is genuinely ambiguous.
Time-zone abbreviations were never designed to identify a zone uniquely. They are local shorthand, and different places arriving at the same letters is entirely natural: CST is UTC+8 in China, UTC−6 in the American Midwest, and UTC−5 in Cuba. The spread reaches thirteen hours — enough for "three tomorrow afternoon" to name two different moments. IST likewise covers India (UTC+5:30), Ireland (UTC+1) and Israel (UTC+2); BST covers British Summer Time (UTC+1) and Bangladesh Standard Time (UTC+6).
This is exactly why the IANA database names zones by region and place: Asia/Shanghai, America/Chicago, Australia/Sydney. That form binds the where to the when, so two zones cannot collide on a name; and it follows local law, so when a country changes its daylight-saving rules the database is updated rather than renamed. The zones this tool lists are those IANA names, not abbreviations.
In practice: when scheduling across zones, write the UTC offset ("3pm UTC+8") or name the city ("3pm Shanghai time") instead of an abbreviation. If you receive one, ask which region it means — in distributed work that one question costs less than rescheduling afterwards.
Frequently asked questions
What happens during a daylight-saving transition?
Two things can go wrong, and both are handled. When clocks jump forward, some wall-clock times do not exist on that date — the tool says so instead of returning a fabricated time. When clocks go back, some times occur twice — the tool tells you and shows the earlier occurrence.
Do you show the standard time offset or the current one?
The offset shown is the one actually in effect at the moment being converted, which is why the same zone can read UTC+01:00 in January and UTC+02:00 in July. Rows in daylight saving are marked with a DST badge.
Which time zone list is used?
The full IANA database available to your browser, which is what the time zones in operating systems, servers and libraries are named after. That is why you will see names like America/New_York rather than abbreviations such as EST.
Can I plan a meeting across several zones?
Yes. Pick the date and time in the organizer's zone, add the attendees' zones, and the difference column shows each one relative to the organizer. Daylight-saving-aware, so it stays correct for meetings booked weeks ahead.
Is my input sent to a server?
No. There is no server involved — the conversion is done in the page, and the zones you list are stored only in your own browser.
Related tools
Convert between Unix timestamps and readable dates in any time zone. Seconds or milliseconds are detected for you — and nothing you type leaves your browser.
Paste any cron expression to see what it means in plain English and exactly when it will run next — in your own time zone, DST included.
Current weather and a 7-day forecast for any city. No account, no API key — data straight from Open-Meteo.
Validate any phone number against the official numbering plans, see whether it is real or just plausible, and get E.164, international, national and RFC3966 formats side by side.