Time Zone Converter (2026) - City Presets & UTC Offsets

Fixed offsets for standups and launch calls

Remote teams store "UTC-5" in their head faster than tz database names. Pick presets or type offset minutes, enter datetime, read converted clock in the accent card.

Defaults: now as datetime, New York (-300) to Tokyo (540). UTC row shows the same instant without offset.

Copy exports from, to, and UTC lines.

Offsets vs calendar span tools

Days between two calendar dates (no clock) is the Date Difference Calculator.

Age on a birth date ignores clock and zone: Age Calculator.

Cron schedules in local wall time need the Cron Expression Generator plus manual DST awareness.

When presets lie (DST weeks)

New York is UTC-5 in standard time and UTC-4 when DST applies. Preset uses -300; add 60 minutes to from-offset in summer if the meeting must match Eastern wall time.

Half-hour zones (India UTC+5:30) use offset 330. Quarter-hour zones exist; type minutes directly.

Campaign launches tied to link tracking: build URL in the UTM Builder, then share meeting time from this converter in the invite body.

Frequently Asked Questions (FAQ)

How does conversion work?

Your datetime is interpreted in the "from" offset. Convert to UTC by subtracting from offset, then to "to" offset by adding that offset. Display shows local civil time in each zone label.

What are city presets?

Shortcuts that fill offset minutes: New York UTC-5 (-300), London UTC+0, Tokyo UTC+9 (540), etc. Choose Custom to type any offset, including half hours like UTC+5:30 (330 for Mumbai).

Does this handle daylight saving time?

No. Offsets are fixed. During DST, pick the current offset manually or adjust preset minutes. For legal timestamps, confirm with an IANA timezone database tool.

Why show UTC equivalent?

UTC is the shared reference for logs, cron, and API payloads. The third card shows the same instant in UTC+0 wording.

Time Zone Converter