Time zone conversion: use the date as well as the city

To convert a meeting time, use the date, local time and source city. “15:00 in Berlin” becomes 09:00 in New York on 2 March 2026, but 10:00 on 16 March. The cities change their clocks on different dates.

Remembering a six-hour difference works for part of the year. Converting the date of the actual event is more reliable than reusing today’s offset.

A worked meeting across the spring clock changes

For a meeting fixed at 15:00 Berlin time, the 2026 conversions are:

Meeting date	Berlin	UTC	New York
2 March	15:00	14:00	09:00
16 March	15:00	14:00	10:00
30 March	15:00	13:00	09:00

New York changes to daylight time on 8 March 2026; Berlin changes on 29 March. During the gap, their clocks are five hours apart rather than six. There is another mismatch in autumn, between Berlin’s 25 October change and New York’s 1 November change.

These are dated examples, not a permanent promise about future government rules. Check recurring meetings around the transitions that apply to their locations.

An offset identifies a moment only with a date and time

2026-07-01T14:30+02:00 identifies the same moment as 2026-07-01T12:30Z. The Z means UTC. The offset tells you how the local clock reading differs from UTC at that moment.

14:30+02:00 without a date is only a time of day, not a unique event. And a fixed +02:00 offset does not say what Berlin’s offset will be in winter.

For a one-off log entry, a UTC timestamp or timestamp with an explicit offset is useful. For an event that must stay at a local hour each week, retain the named zone and the local-time rule too.

Choose a place name rather than an abbreviation

Names such as Europe/Berlin and America/New_York identify rules in the IANA time zone database. Abbreviations such as CST can refer to different places and are easy to misinterpret.

The IANA database is updated to reflect changes in offsets, boundaries and daylight-saving rules. Its historical coverage has limits; it is not a complete record of every local clock ever used.

The time zone converter uses the browser’s time zone data. Its named zones allow date-specific conversion, but the data available depends on the browser and operating system being up to date.

Some local times are missing or occur twice

In New York on 8 March 2026, clocks jump from 02:00 to 03:00. There is no local 02:30 that morning. A tool must reject it or apply a documented adjustment; an ordinary offset calculation cannot make that time exist.

On 1 November 2026, the local time 01:30 occurs twice:

• 01:30 at UTC−04:00 is 05:30 UTC;
• 01:30 at UTC−05:00 is 06:30 UTC.

A booking or log entry needs the offset or another way to choose between them. The local converter currently does not warn about these ambiguous or nonexistent inputs. It can select one occurrence or return a different local time for a gap. For a transition-hour event, confirm the intended instant separately and convert from UTC.

Read the date on the result, not just the hour

Offsets are not limited to whole hours. India uses UTC+05:30, while Nepal uses UTC+05:45. A conversion can also move to the previous or next date: 23:30 UTC on 2 October is 08:30 in Tokyo on 3 October.

This matters for overnight travel, deadlines and a call described as “Friday morning”. Include the converted date and weekday when sending the time to someone else.

What the local converter currently shows

In the converter, choose the reference zone and add destination zones to compare their current clocks, dates and offsets. The current interface starts in live-clock mode, disables the date/time field and has no separate control for leaving that mode. Its on-screen results should therefore not be treated as a preview of a future appointment.

For a future meeting, enter the event in a calendar with the intended named source zone and check the destination’s full date and time there. Check an occurrence on each side of an upcoming clock change, rather than typing a fixed hour independently for each attendee.

A weekly 15:00 Berlin meeting and a weekly 13:00 UTC meeting are different recurrence rules. Decide which one should remain fixed before sharing it.

Last reviewed 2 October 2026.