Time zone converter

Convert a date and local time between time zones, including daylight saving. See the destination date, time, and UTC offset so an overnight conversion does not turn into a meeting on the wrong day.

Loading the converter…

Use the meeting date, not just today's time difference

Choose the source zone, destination zone, date, and local time. Two places can change clocks on different dates, or only one may observe daylight saving. Their time difference can therefore vary during the year.

A clock change can skip or repeat a time

When clocks move forward, some local times never occur. Choose another time if yours falls in that gap. When clocks move backward, one local time can happen twice. The converter asks you to choose the earlier or later occurrence.

Read the destination date and offset

A +1 day label means the destination is on the next calendar date. A -1 day label means the previous date. The UTC offset shows the zone's difference from UTC for that moment.

Named zones such as Europe/London carry date-specific rules. Short abbreviations can be ambiguous, while a fixed offset alone does not include daylight saving rules.

Copy conversion keeps the source and destination dates, both local times and offsets, and the UTC instant in one statement. Share that complete result when a deadline or meeting crosses midnight. This converts one occurrence. Check another date separately when a recurring event spans a clock change.

Build a time zone converter

Pass the source wall time and destination zone to the Time SDK. Use disambiguation=reject so skipped or repeated local times require a deliberate choice.

  1. Collect a source zone, destination zone, and local date/time.
  2. Reject a skipped or repeated time until the visitor chooses an intended occurrence.
  3. Display the destination date, clock time, and UTC offset.

Installation steps are included in each example. Set PARSEAPI_KEY on your server. Swift and Kotlin use an app key restricted to your app ID.

// npm install @parseapi/sdk@1.14.0
import { parseAPI } from '@parseapi/sdk';

// Set PARSEAPI_KEY on your server.
const parse = parseAPI();

const from = 'America/New_York', to = 'Europe/London';
const date = '2026-11-16', time = '09:00';
// Ask for a choice rather than silently normalizing a skipped or repeated time.
// Set this to 'earlier' or 'later' after the visitor chooses an occurrence.
const disambiguation = 'reject';
const result = await parse.time(from, {
  at: date + 'T' + time + ':00', to, disambiguation,
});
if (!result.to?.at) throw new Error('Conversion unavailable.');
console.log({
  from: { timezone: result.timezone, local: result.at, offset: result.offset },
  to: { timezone: result.to.timezone, local: result.to.at, offset: result.to.offset },
});

Time API documentation

How do I convert a time between time zones?

Choose the source and destination, then enter the source's local date and time. The result shows the destination's clock, date and UTC offset. Copy conversion keeps both sides and the exact UTC instant together.

Does the time zone converter include daylight saving?

It uses the selected date, not a fixed year-round difference. Two places can change clocks on different weekends, or only one may observe daylight saving, so the difference can vary during the year.

What if a local time happens twice or does not exist?

The converter asks you to choose the earlier or later occurrence of a repeated time. If clocks skip that local time, choose another time. It does not silently move your meeting into a different hour.

Why does the destination have a different date?

The same instant can fall on another calendar date in the destination. A +1 day label means the next date. -1 day means the previous date. Copy both dates when sharing an event.

Does UTC change for daylight saving time?

UTC does not move forward or backward for seasonal clock changes. A geographic zone's UTC offset can change according to its local rules.

Will this schedule a recurring meeting?

It converts one occurrence. For recurring invitations, use a calendar with the intended named source zone so later occurrences follow that zone's rules. Use the actual date to check another occurrence.