Convert wall-clock time between two places
Enter the date and clock time as people use it in the source location, then choose the source and destination zones. The converter first identifies the exact instant represented by the source time and then renders that instant under the destination zone's IANA rules.
Worked example: Beijing to New York
For 2026-10-12 18:00 in Asia/Shanghai, the result in America/New_York is 2026-10-12 06:00. Shanghai uses UTC+08:00. New York uses UTC-04:00 on that date because daylight saving is active. In winter, New York normally uses UTC-05:00, so the difference can change.
Why named time zones matter
A fixed offset such as UTC-05:00 cannot describe daylight-saving transitions or historical rule changes. Named zones such as America/New_York and Europe/London carry those rules. If the source clock skips a time in spring or repeats one in autumn, this tool reports the problem instead of silently guessing.
Before scheduling across regions
- Confirm the date as well as the clock time; the destination may be on another calendar day.
- Use the city or IANA zone rather than a remembered offset when future daylight-saving rules matter.
- Put the time zone in invitations and deadlines so recipients know which local clock the time belongs to.
How to use this tool
The source field starts with the current time in the zone detected from your browser. Click in the text field to edit any character, or replace it with YYYY-MM-DD HH:mm. Choose the source and destination zones; leaving the field or pressing Convert updates the result. Use current time resets the value in the selected source zone.
Worked input and output
| Input or setting | Expected result |
|---|---|
2026-10-13 09:26 · Asia/Shanghai → America/Los_Angeles | 2026-10-12 18:26 · UTC−07:00 |
2026-10-12 18:00 · Asia/Shanghai → America/New_York | 2026-10-12 06:00 · UTC−04:00 |
2026-01-12 18:00 · Asia/Shanghai → America/New_York | 2026-01-12 05:00 · UTC−05:00 |
Checks before using the result
The destination includes the calendar day and its date-specific UTC offset. Swap uses the converted destination wall time as the new source. Missing spring times are rejected; repeated autumn times offer both offsets. Browser zone detection uses the device setting, not IP geolocation. If that setting is wrong, choose the correct zone manually. See PST versus PDT for a common offset mistake.