Converters & time math
Time zone converter
Translate any moment from one city to another. Pick a source and a target, set the date and time, and read off the exact converted time — daylight saving handled for you, computed right in your browser.
How to use the time zone converter
Pick the source city
Choose the place the time is currently expressed in — the zone the meeting, deadline or departure was quoted in.
Enter the date and time
Set both. The date genuinely matters: the same pair of cities can be four, five or six hours apart depending on where in the year you land, because each side changes its clocks on its own schedule.
Pick the target city
Choose where you want the answer. The conversion resolves the source time to a real UTC instant first, then renders that instant in the target zone, which is why it stays correct across transitions.
Read the result and the offset
You get the converted local time, the date it falls on, and the offset between the two zones for that specific date — worth checking when it differs from the number you had in your head.
Converting time zones correctly
The naive way to convert a time is to add an offset, and it is wrong often enough to matter. The offset between two places is not a fixed property of the pair — it depends on the date, because each zone follows its own daylight-saving rule. New York and London are five hours apart for most of the year and four hours apart for two weeks in March, when the United States has changed its clocks and Europe has not.
The correct method is the one used here: take the local wall-clock time in the source zone, resolve it to the absolute UTC instant it refers to using that zone's rule for that date, then express that instant in the target zone using its own rule. Two conversions, each date-aware, rather than one arithmetic shortcut.
Abbreviations are a related trap. EST and EDT are different offsets, and most people write EST year-round when they mean whichever is in force. Worse, some abbreviations are outright ambiguous — CST is Central Standard Time in North America, China Standard Time and Cuba Standard Time, three different offsets. Naming a city or an IANA zone removes the ambiguity entirely.
There are two moments a year when a local time is genuinely broken. When clocks spring forward, an hour does not exist — 2:30am simply never happens that night. When they fall back, an hour happens twice, and "1:30am" is ambiguous without more information. Conversions around those boundaries deserve a second look no matter what tool you use.
When you'd reach for it
Confirming a meeting time
Turn a time someone quoted in their zone into yours, on the right date, without guessing the offset.
Booking travel
Convert departure and arrival times that are always quoted in local time at each end.
Deadlines in another country
Work out exactly when a submission cut-off expressed in a foreign zone falls for you.
Watching a live event
Find the local start time for a broadcast, launch or match announced elsewhere.
Coordinating a release
Translate a planned deployment window into every affected team's local clock.
Reading a foreign document
Resolve a timestamp in a contract, ticket or email into a time you can act on.
Questions & answers
- Does the converter account for daylight saving time?
- Yes. Each conversion resolves the real UTC instant using the source city's offset for that exact date, so spring-forward and fall-back shifts are applied automatically on both sides.
- Is my data sent anywhere?
- No. Every calculation runs locally in your browser using the built-in Intl time-zone database. Nothing is uploaded or stored on a server.
- Can I convert a future or past date?
- Yes. Set any date and time in the source city and the target time updates instantly, using the correct historical or upcoming offset for that day.