Time Zone Converter — Compare One Moment Worldwide
Convert a date and time from one IANA zone to many others in your browser. Process: enter a local datetime, choose the source zone, tick comparison zones, then Convert. Example: 2026-06-15 14:30 in Los Angeles → New York, London, Tokyo, and UTC rows with offsets. Explains DST gaps; not a meeting export pack.
| Time zone | Local date & time | UTC offset |
|---|
How it works
Enter a local datetime and pick its IANA source zone. Tick one or more comparison zones, then Convert. The table shows each zone’s local clock and UTC offset for that same instant, computed with Intl in your browser.
Rules you should expect
Expect IANA zone rules, DST behavior, and how this differs from epoch or meeting-export tools.
- Zones follow the IANA Time Zone Database (tzdata). Offsets change when regions change DST — the table reflects rules for the date you enter, not a fixed GMT offset.
- Spring-forward gaps: if a wall-clock hour was skipped, conversion fails with a clear message. Fall-back overlaps: duplicate local times may map to one offset — double-check edge cases.
- Abbreviations (CST, IST, etc.) can mean different zones. Use full IANA names in APIs, cron, and calendar invites.
- Privacy: no upload. This page is read-only comparison — not a meeting scheduler, not an IP geolocation lookup.
Example
Fixed sample on load: 2026-06-15 14:30 in America/Los_Angeles → UTC, America/New_York, Europe/London, Asia/Tokyo with local clocks and short UTC offsets. Offsets follow IANA rules for that calendar date.
Good fits
- Remote teams: someone says “3:30 PM Pacific” — see New York, London, and Tokyo on one row set before you join.
- Ops / logs: a timestamp was logged in Chicago local time — compare UTC and your own zone without mental math.
- Travel planning: anchor a flight arrival in Dubai and read Sydney and Los Angeles side by side for handoff calls.
Frequently asked questions
Why IANA names instead of EST, PST, or GMT?
We use IANA identifiers such as America/New_York or Asia/Tokyo — the same names browsers and servers use. Abbreviations like EST or JST are ambiguous (standard vs daylight); always prefer the full IANA zone when scheduling.
What happens on daylight saving change days?
On DST start days some local hours are skipped — the converter shows an error instead of guessing. On fall-back overlap nights the same local time can occur twice; Intl picks one offset — verify critical meetings manually on those dates.
How is this different from a Unix timestamp converter?
Unix timestamp tools turn epoch seconds ↔ calendar clocks, often in UTC. This page keeps a named source zone and shows several target zones side by side for the same instant — better for “what time is it for them?”
Can I export a team meeting timezone pack here?
No. This is an instant multi-zone table for your own reference. It does not build a shareable meeting pack, attendee list, or ICS export — those would be a separate workflow.
Does my datetime get sent to a server?
Yes. Conversion uses built-in Intl.DateTimeFormat only — your datetime never leaves the browser and nothing is uploaded.
Questions or feedback
Something unclear, broken, or missing? Draft a message below — we read every note about these tools.