- Home
- Time Zones & Meetings
- Time Zone Converter
Time Zone Converter
Pick a source zone, date, and time, plus a target zone. The conversion uses whichever offset actually applies on that date in each zone, not a fixed year-round number.
Want to learn more?
Worked example
15:00 UTC on July 15, 2027, renders as 11:00 in America/New_York, since that zone sits at a summer offset of UTC minus 4 hours during daylight saving time. The exact same 15:00 UTC on January 15, 2027, renders as 10:00 instead, a full hour earlier on the clock, because the zone has shifted back to its winter offset of UTC minus 5 hours by then. The underlying UTC instant in both cases is genuinely equivalent to a fixed point on the universal timeline. Only the local wall clock reading changes, which is exactly why converting through a real IANA zone rather than a fixed offset number is necessary for any date that might fall on either side of a daylight saving transition.
Common mistakes
- Applying a single fixed offset year round for a zone that actually observes daylight saving time. The real offset depends on the specific date being converted, not a constant number.
- Assuming a converted result stays valid for a different date. A time zone conversion is only accurate for the exact date and time it was computed for.
Limitations
This converts one specific instant from one zone to another. It does not track a recurring event across zones over time. See the Multi-Timezone Event Planner or the Recurring Date Generator for that kind of repeating schedule instead.
Frequently asked questions
- What if the entered local time doesn't exist, such as during a spring-forward gap?
- The result flags it explicitly and resolves it using the standard forward-shifted convention, rather than silently guessing at a real instant.
- Why does the same UTC instant convert to a different local hour in winter and summer?
- Because a time zone that observes daylight saving time uses a different UTC offset depending on the date, not a single fixed offset year round.