How it works
Pick the date and time as they read on a clock in the first time zone, then the zone you want to convert to. The converter shows the same moment in the second zone, whether it falls on the previous or next day, the exact time difference and both UTC offsets. The hour-by-hour table lines up the whole day so you can find a time that suits both places.
Seoul 09:00 (UTC+9) = New York 19:00 the day before (UTC−5)
Daylight saving time
The gap between two cities is not fixed. When one side switches to daylight saving time and the other does not, the difference changes by an hour — Seoul and New York are 14 hours apart in winter but 13 in summer. Every conversion uses the rules in force on the date you pick. If a time does not exist because clocks jump forward, it is moved to the next valid time and flagged.
Tips
- Shaded rows in the table are between 9:00 and 18:00 in both places — handy for scheduling calls.
- Use Swap to flip the direction in one tap.
- The time zone list and its rules come from your browser, so they stay up to date.
Standards and sources
- Time zones and daylight saving rules from the IANA Time Zone Database
- Offsets written relative to Coordinated Universal Time (UTC), ITU-R TF.460
Last reviewed October 12, 2026
Frequently asked questions
How do I convert a time to another time zone?
Enter the date and time as they read in the first zone, choose the zone you want, and the converted time appears at once with the date it falls on.
Does it handle daylight saving time?
Yes. Each conversion uses the daylight saving rules in force on the date you pick, so the difference can be one hour less in summer.
Why does the result show a different date?
Large time differences can push the time into the previous or next day. The result marks this as previous day or next day.
How do I find a good meeting time?
Check the hour-by-hour table. Shaded rows fall between 9:00 and 18:00 in both places.
Is my data sent anywhere?
No. All conversions run in your browser using its built-in time zone database.