How to use
- Pick the date and time, or tap Now.
- Choose the From and To time zones. On your first visit, your own zone is already selected.
- Read the converted time, both UTC offsets and whether daylight saving time applies.
- Use swap or a popular pair to switch quickly.
How the conversion works
- The time you enter becomes one exact moment in UTC, using the From zone’s rules for that date.
- That moment is shown in the To zone, using its rules for the same date.
The rules come from the IANA time zone database built into your browser. It records each zone’s offsets and daylight saving changes, past and planned.
Examples
- 9:00 AM on 21 October 2026, New York → London: 2:00 PM. New York is UTC−4 and London is UTC+1.
- The same time on 28 October 2026: 1:00 PM. The UK is back on GMT, but the US is still on daylight time.
- 9:00 AM New York → India: 6:30 PM on 21 October, but 7:30 PM on 1 December 2026.
2026 clock changes
| Place | Clocks go forward | Clocks go back |
|---|---|---|
| United States | 8 March, 2:00 AM | 1 November, 2:00 AM |
| United Kingdom | 29 March, 1:00 AM | 25 October, 2:00 AM |
| European Union | 29 March | 25 October |
| India | No change (UTC+5:30) | No change |
Times that are skipped or happen twice
When clocks go forward, an hour is skipped. A time in that gap, such as 2:30 AM on 8 March 2026 in New York, is read with the offset from before the change, so it becomes 3:30 AM EDT.
When clocks go back, an hour repeats. 1:30 AM on 1 November 2026 in New York happens twice, and the calculator uses the first one (EDT, UTC−4). Both rules come from RFC 5545, the iCalendar standard.
Working with server logs? The Unix timestamp converter turns epoch seconds into dates in UTC and in your own zone.