What this time zone converter does
This tool takes a specific time in one city and tells you what time it is in another. You type the date and time as they appear on the clock in the source zone, choose a target zone, and instantly get the matching local time, the gap between the two zones, and a flag when the answer lands on a different calendar day.
It’s built for the everyday puzzles of remote work and long-distance life: booking a call that works for both New York and Tokyo, catching a product launch announced in Pacific time, scheduling a message so it arrives during business hours, or phoning family overseas without waking them at 3 a.m. Everything runs in your browser — no time ever leaves your device.
How to use it
- Enter the date and time in the source zone. It defaults to today at 12:00.
- Pick the source zone: the city where the event happens at that clock time.
- Pick the target zone: the city you want the local time for.
- Read the dark card: the destination time, its offset from UTC, and a Next day or Previous day tag when the date shifts.
- The Swap zones button flips source and target in one click.
How it works (and why daylight saving matters)
The method has two steps. First, the time you type is read as a wall-clock time in the source zone and converted to a single universal instant (UTC) using that zone’s real offset on that date. Then the same instant is re-expressed as wall-clock time in the target zone. The gap is simply:
difference = target_offset − source_offset
The catch is that offsets aren’t fixed. Many regions push their clocks forward in summer (daylight saving time, or DST), so the gap between two cities changes depending on the date. The converter reads your operating system’s time-zone database, which already knows these rules, so DST is handled for you.
| City | Offset in July | Offset in January | Observes DST? |
|---|---|---|---|
| New York | UTC−04:00 | UTC−05:00 | Yes |
| Los Angeles | UTC−07:00 | UTC−08:00 | Yes |
| Bogotá | UTC−05:00 | UTC−05:00 | No |
| London | UTC+01:00 | UTC+00:00 | Yes |
| Madrid | UTC+02:00 | UTC+01:00 | Yes |
| Tokyo | UTC+09:00 | UTC+09:00 | No |
| Sydney | UTC+10:00 | UTC+11:00 | Yes (reversed) |
Worked example
You’re on a team where the New York office wants a stand-up at 9:00 a.m. on July 9, 2026, and you need the time for a teammate in Tokyo.
- In July, New York runs on Eastern Daylight Time: UTC−04:00. Tokyo stays on UTC+09:00 all year.
- 9:00 a.m. in New York is 13:00 UTC (9:00 + 4 h).
- Add Tokyo’s 9 hours to 13:00 UTC: 22:00 (10 p.m.) on the same day, July 9.
- The gap is 13 hours, with Tokyo ahead. Late evening for your teammate — worth nudging the meeting earlier.
Run the same numbers in January and New York falls back to UTC−05:00, so the gap widens to 14 hours and Tokyo would read 23:00. That one-hour swing is daylight saving at work: Japan never changes its clocks, but New York does.
Frequently asked questions
Does it account for daylight saving time?
Yes. Each conversion looks up the offset that is valid on the exact date you enter, straight from the system’s time-zone data. That’s why New York to Tokyo is 13 hours apart in July but 14 hours in January — you never have to adjust anything by hand.
Why does the result show a different day?
When two zones are far apart, adding or subtracting the offset can cross midnight. 11:00 p.m. in Los Angeles is 8:00 a.m. the next day in Madrid, for instance. The Next day or Previous day tag warns you so you don’t book the meeting on the wrong date.
What is UTC, and how is it different from GMT?
UTC (Coordinated Universal Time) is the world reference that every zone is defined against as an offset (UTC−4, UTC+9, and so on). In everyday use it matches GMT, though GMT is a historical zone and UTC is a technical standard kept by atomic clocks. For converting clock times you can treat them as the same.
Why is Southern Hemisphere daylight saving reversed?
Because the seasons are flipped. Sydney’s summer is in January, so its clocks read UTC+11 in January and UTC+10 in July — the opposite pattern to Europe and North America. The converter handles it automatically, since it only cares about the real date.
Can I rely on this for a flight or an important meeting?
It’s great for planning, but always confirm against official sources. Airlines publish every departure and arrival in the airport’s own local time, and some governments change their DST rules from one year to the next. Treat this as a fast guide, not a legal record.