Time Zone Converter

One timestamp, all major time zones at once. Powered by your browser's Intl engine.

Source timeSource zone

Converted to popular time zones

UTC

UTC+00:00

2026-05-25 | 19:19:00

America/New_York

UTC-04:00

2026-05-25 | 15:19:00

America/Los_Angeles

UTC-07:00

2026-05-25 | 12:19:00

America/Chicago

UTC-05:00

2026-05-25 | 14:19:00

America/Sao_Paulo

UTC-03:00

2026-05-25 | 16:19:00

Europe/London

UTC+01:00

2026-05-25 | 20:19:00

Europe/Paris

UTC+02:00

2026-05-25 | 21:19:00

Europe/Berlin

UTC+02:00

2026-05-25 | 21:19:00

Europe/Moscow

UTC+03:00

2026-05-25 | 22:19:00

Africa/Cairo

UTC+03:00

2026-05-25 | 22:19:00

Asia/Dubai

UTC+04:00

2026-05-25 | 23:19:00

Asia/Kolkata

UTC+05:30

2026-05-26 | 00:49:00

Asia/Shanghai

UTC+08:00

2026-05-26 | 03:19:00

Asia/Singapore

UTC+08:00

2026-05-26 | 03:19:00

Asia/Seoul

UTC+09:00

2026-05-26 | 04:19:00

Asia/Tokyo

UTC+09:00

2026-05-26 | 04:19:00

Australia/Sydney

UTC+10:00

2026-05-26 | 05:19:00

Pacific/Auckland

UTC+12:00

2026-05-26 | 07:19:00

Want the background behind this tool? Cron Expressions Explained: A Complete Scheduling Guide

You need to schedule a meeting that works for teammates in Seoul, San Francisco, and Berlin. Or you are reading server logs in UTC and trying to map an incident back to the moment your customer experienced it. Or you are planning a product launch and want every region to see the announcement at 09:00 local. This converter maps one moment in one zone to every major zone worldwide at once, using your browser's Intl engine for accuracy that tracks daylight saving rules and political offset changes.

The conversion happens entirely in the browser via the Intl.DateTimeFormatAPI, which reads zone data from your operating system's ICU/tzdata. No timestamps leave the tab — useful when the meeting topic or the incident timestamp is itself sensitive.

How to use it

Pick a source date and time. The format follows your locale — use the picker to avoid ambiguity.
Choose the source time zone. Pick by IANA name (America/New_York) rather than abbreviation (EST) — abbreviations are ambiguous (CST means three different things in the world).
Read the converted time across popular zones at once. DST-aware: the displayed offsets reflect whether DST is active on the chosen date.
Iterate — slide the date forward or backward to find a time that works for everyone, or to confirm an upcoming DST transition does not move the meeting.

Examples

Schedule a Seoul standup across the US west coast

Your team meets at 10:00 KST. The converter surfaces the exact local time for teammates in San Francisco, New York, and UTC.

Input

source: 2024-09-10 10:00
zone:   Asia/Seoul (KST, +09:00)

Output

Asia/Seoul          2024-09-10  10:00
UTC                 2024-09-10  01:00
America/New_York    2024-09-09  21:00 (EDT)
America/Los_Angeles 2024-09-09  18:00 (PDT)
Europe/London       2024-09-10  02:00 (BST)

Correlate a UTC log timestamp back to local time

Server logs are stored in UTC. Paste a timestamp from an incident and read it in the operator's local zone — DST offsets applied automatically.

Input

source: 2024-03-15 23:45
zone:   UTC

Output

UTC                 2024-03-15  23:45
Asia/Seoul          2024-03-16  08:45 (KST)
America/Los_Angeles 2024-03-15  16:45 (PDT)
Europe/Berlin       2024-03-16  00:45 (CET)

Common time zones at a glance

IANA name	City	Standard	DST
`UTC`	(reference)	+00:00	No
`America/Los_Angeles`	San Francisco / LA	PST −08:00	PDT −07:00 (Mar-Nov)
`America/New_York`	New York / Toronto	EST −05:00	EDT −04:00 (Mar-Nov)
`America/Sao_Paulo`	São Paulo	BRT −03:00	No (dropped 2019)
`Europe/London`	London / Dublin	GMT +00:00	BST +01:00 (Mar-Oct)
`Europe/Berlin`	Berlin / Paris / Madrid	CET +01:00	CEST +02:00 (Mar-Oct)
`Africa/Johannesburg`	Johannesburg	SAST +02:00	No
`Asia/Dubai`	Dubai	GST +04:00	No
`Asia/Kolkata`	Mumbai / Bangalore	IST +05:30	No
`Asia/Singapore`	Singapore / KL	SGT +08:00	No
`Asia/Shanghai`	Beijing / Shanghai	CST +08:00	No
`Asia/Tokyo`	Tokyo	JST +09:00	No
`Asia/Seoul`	Seoul	KST +09:00	No
`Australia/Sydney`	Sydney	AEST +10:00	AEDT +11:00 (Oct-Apr)
`Pacific/Auckland`	Auckland	NZST +12:00	NZDT +13:00 (Sep-Apr)

About the IANA time zone database

The names you see (Asia/Seoul, America/New_York) come from the IANA Time Zone Database (tzdata) — the canonical source consulted by Linux, macOS, Windows, Java, .NET, Python, and every modern browser. Each zone encodes its full history of UTC offsets, daylight saving rules, and political changes. That is why America/Los_Angeles is preferred over the ambiguous PST: PST/PDT switch twice a year, and a fixed offset would be wrong half the year. The database releases multiple times per year (current as of 2026: tzdata 2025b) — your OS and browser update on their own cadence, and lagging tzdata is the #1 cause of incorrect conversions in the weeks following a country's DST policy change.

UTC vs. GMT vs. Zulu — what they mean

UTC — Coordinated Universal Time. An atomic time scale with occasional leap seconds. The reference for all software timestamps. No DST.
GMT — Greenwich Mean Time. A solar time scale based on the mean position of the sun over Greenwich. Functionally identical to UTC for most software purposes (both are offset 0, no DST), but legally distinct in the UK where GMT is the winter standard time and BST is summer.
Zulu (Z) — Military shorthand for UTC. Z in an ISO 8601 timestamp (2024-01-15T10:30:00Z) means the same as +00:00.
Use UTC for new systems. Store, log, and exchange in UTC. Convert to a named zone only at the presentation layer.

ISO 8601 offset notation

ISO 8601 timestamps include an explicit offset from UTC. Forms you will see:

2024-01-15T10:30:00Z — UTC, Zulu form.
2024-01-15T10:30:00+00:00 — UTC, explicit offset.
2024-01-15T19:30:00+09:00 — Seoul (KST). Same instant as the two above.
2024-01-15T05:30:00-05:00 — New York (EST). Same instant.
2024-01-15T10:30:00 — local time, no offset. Avoid — this loses information and is impossible to convert without out-of-band context.

Always include the offset. APIs that drop it produce subtle bugs when clients and servers are in different zones.

Daylight saving time pitfalls

Spring forward gap. On the day clocks jump from 02:00 to 03:00 (most of US/Europe), wall-clock times like 02:30 do not exist. Most libraries silently round forward to 03:30 — verify if your scheduling logic depends on the exact slot.
Fall back ambiguity. When clocks roll from 02:00 back to 01:00, the 01:30 slot occurs twice. Storing only the wall-clock time loses the disambiguation; store UTC plus zone, or carry an explicit offset.
DST schedules drift politically.Brazil dropped DST in 2019. Egypt re-adopted it in 2023. Iran abolished it in 2022. Chile delayed its start in 2022. Australia's Lord Howe Island has a 30-minute offset shift. Always rely on an up-to-date tzdata — never hard-code offsets.
Northern vs. southern hemisphere.Sydney is in DST when New York is not, and vice versa. A weekly meeting between them moves by an hour twice a year on each side's transition (and twice more on the other side's). Confirm the next two meetings whenever a transition is near.
The US vs. EU transition gap. The US transitions on the 2nd Sunday of March; the EU transitions on the last Sunday of March. For two weeks, the New York-to-London offset is 4 hours instead of the usual 5. Calendar invitations across the Atlantic get this wrong all the time.

Common use cases

Scheduling meetings with distributed teams
Planning product launches across markets (announcement at 09:00 local)
Correlating logs from multi-region infrastructure (server in UTC, ops in local)
Translating customer event timestamps before raising support tickets
Picking a deployment window that avoids every team's working hours
Sanity-checking cron schedules that fire across DST transitions
Booking flights and calls with international clients

Troubleshooting

The converter shows an offset different from my watch.Your operating system's ICU/tzdata version may lag behind the latest IANA release. Update the OS (or browser on platforms where it bundles tzdata, like Firefox); if a country recently changed DST, the database may not have caught up.
The same time appears twice on the same day. You are looking at a fall-back DST day. The 01:30 hour really does occur twice; choose between the pre-DST (still summer) and post-DST (winter) instant.
The converter rejects a time. You picked a time in the spring-forward gap. 02:30 on the transition day does not exist; pick 01:30 or 03:30 instead.
Conversions look right but log timestamps still disagree.Logs may be in the server's local zone, not UTC. Run timedatectl on the server to confirm. Force logs to UTC via TZ=UTC in the systemd unit.

Frequently asked questions

Q: Why does the converter show a different result than my watch?

Your operating system's ICU/tzdata version may lag behind the latest IANA release. Browsers update on roughly the same cadence as the OS. If a country recently changed DST policy (Egypt 2023, Iran 2022, Chile 2022) double-check from a live source for the next few weeks until your system picks up the new database.

Q: Should I store local time or UTC in my database?

UTC. Always. Convert at the edge — when you render to a user, when you write to a localized report. Storing wall-clock time loses information whenever DST or zone rules change, and joins across users in different zones become impossible. The only exception is when the time is intrinsically local (a calendar event "9 AM in New York" that moves with DST), in which case store the IANA zone alongside the local time and resolve to UTC on read.

Q: What is the difference between `UTC` and `GMT`?

For most software purposes they are interchangeable — both have a 0 offset and no DST. Strictly, UTC is an atomic time scale with leap seconds; GMT is a solar time scale. The UK uses GMT in winter and BST in summer, so "GMT" alone is ambiguous between January and August in London. Use UTC for new systems.

Q: Why do some zones show offsets like +05:30 or +05:45?

Several countries adopted non-hour offsets — India is +05:30, Nepal is +05:45, Newfoundland is −03:30, Lord Howe Island has a 30-minute DST shift. Designs that assume integer-hour offsets break in those regions; rely on IANA names and the standard library's conversion functions instead of arithmetic on hour counts.

Q: How does the converter handle the DST transition day?

The browser's Intl engine handles it transparently. On spring forward, the missing hour is skipped — picking 02:30 may roll forward to 03:30 silently. On fall back, the repeated hour is shown once by default; if your scheduling depends on knowing which 01:30 you meant, store the offset (-04:00 vs. -05:00) alongside the time.

Q: Can I use this for a fixed-offset zone like "UTC+5"?

The IANA database includes fixed-offset zones (Etc/GMT+5 for UTC−05:00 — note the sign is inverted by historical convention). Fixed offsets are useful for ships at sea or short-lived tasks, but for human-facing dates pick the location-named zone instead — it carries DST and political-change history, so the offset stays correct over years.

Related guides

Cron Expressions Explained: A Complete Scheduling Guide

Cron looks easy until you need "every 15 minutes only on weekdays" and stop trusting your own math. The five fields with examples for Linux crontab, GitHub Actions, and Kubernetes CronJob.

API Testing with HTTP Headers: A Hands-On Guide for Developers

Most API bugs live in the headers. Authentication, CORS preflight, cache-control, content negotiation, and the X-Request-ID pattern that makes distributed tracing actually work.

Related Tools

Crontab Generator

Build cron expressions visually with presets and human-readable descriptions.

Cron Expression Parser

Decode cron expressions to plain English and preview the next 10 run times.

Word Counter

Count words, characters, sentences, paragraphs, lines, and bytes with reading time.

HTTP Status Codes

Complete reference of HTTP response status codes organized by category.

Docker Run to Compose

Convert docker run commands to docker-compose.yml format.

Date Math Without Bugs: Diffs, Business Days, and JavaScript Date Lies9 min read

Time Zone Converter

One timestamp, all major time zones at once. Powered by your browser's Intl engine.

Source timeSource zone

Converted to popular time zones

UTC

UTC+00:00

2026-05-25 | 19:19:00

America/New_York

UTC-04:00

2026-05-25 | 15:19:00

America/Los_Angeles

UTC-07:00

2026-05-25 | 12:19:00

America/Chicago

UTC-05:00

2026-05-25 | 14:19:00

America/Sao_Paulo

UTC-03:00

2026-05-25 | 16:19:00

Europe/London

UTC+01:00

2026-05-25 | 20:19:00

Europe/Paris

UTC+02:00

2026-05-25 | 21:19:00

Europe/Berlin

UTC+02:00

2026-05-25 | 21:19:00

Europe/Moscow

UTC+03:00

2026-05-25 | 22:19:00

Africa/Cairo

UTC+03:00

2026-05-25 | 22:19:00

Asia/Dubai

UTC+04:00

2026-05-25 | 23:19:00

Asia/Kolkata

UTC+05:30

2026-05-26 | 00:49:00

Asia/Shanghai

UTC+08:00

2026-05-26 | 03:19:00

Asia/Singapore

UTC+08:00

2026-05-26 | 03:19:00

Asia/Seoul

UTC+09:00

2026-05-26 | 04:19:00

Asia/Tokyo

UTC+09:00

2026-05-26 | 04:19:00

Australia/Sydney

UTC+10:00

2026-05-26 | 05:19:00

Pacific/Auckland

UTC+12:00

2026-05-26 | 07:19:00

Want the background behind this tool? Cron Expressions Explained: A Complete Scheduling Guide

How to use it

Pick a source date and time. The format follows your locale — use the picker to avoid ambiguity.
Choose the source time zone. Pick by IANA name (America/New_York) rather than abbreviation (EST) — abbreviations are ambiguous (CST means three different things in the world).
Read the converted time across popular zones at once. DST-aware: the displayed offsets reflect whether DST is active on the chosen date.
Iterate — slide the date forward or backward to find a time that works for everyone, or to confirm an upcoming DST transition does not move the meeting.

Examples

Schedule a Seoul standup across the US west coast

Your team meets at 10:00 KST. The converter surfaces the exact local time for teammates in San Francisco, New York, and UTC.

Input

source: 2024-09-10 10:00
zone:   Asia/Seoul (KST, +09:00)

Output

Asia/Seoul          2024-09-10  10:00
UTC                 2024-09-10  01:00
America/New_York    2024-09-09  21:00 (EDT)
America/Los_Angeles 2024-09-09  18:00 (PDT)
Europe/London       2024-09-10  02:00 (BST)

Correlate a UTC log timestamp back to local time

Server logs are stored in UTC. Paste a timestamp from an incident and read it in the operator's local zone — DST offsets applied automatically.

Input

source: 2024-03-15 23:45
zone:   UTC

Output

UTC                 2024-03-15  23:45
Asia/Seoul          2024-03-16  08:45 (KST)
America/Los_Angeles 2024-03-15  16:45 (PDT)
Europe/Berlin       2024-03-16  00:45 (CET)

Common time zones at a glance

IANA name	City	Standard	DST
`UTC`	(reference)	+00:00	No
`America/Los_Angeles`	San Francisco / LA	PST −08:00	PDT −07:00 (Mar-Nov)
`America/New_York`	New York / Toronto	EST −05:00	EDT −04:00 (Mar-Nov)
`America/Sao_Paulo`	São Paulo	BRT −03:00	No (dropped 2019)
`Europe/London`	London / Dublin	GMT +00:00	BST +01:00 (Mar-Oct)
`Europe/Berlin`	Berlin / Paris / Madrid	CET +01:00	CEST +02:00 (Mar-Oct)
`Africa/Johannesburg`	Johannesburg	SAST +02:00	No
`Asia/Dubai`	Dubai	GST +04:00	No
`Asia/Kolkata`	Mumbai / Bangalore	IST +05:30	No
`Asia/Singapore`	Singapore / KL	SGT +08:00	No
`Asia/Shanghai`	Beijing / Shanghai	CST +08:00	No
`Asia/Tokyo`	Tokyo	JST +09:00	No
`Asia/Seoul`	Seoul	KST +09:00	No
`Australia/Sydney`	Sydney	AEST +10:00	AEDT +11:00 (Oct-Apr)
`Pacific/Auckland`	Auckland	NZST +12:00	NZDT +13:00 (Sep-Apr)

About the IANA time zone database

UTC vs. GMT vs. Zulu — what they mean

UTC — Coordinated Universal Time. An atomic time scale with occasional leap seconds. The reference for all software timestamps. No DST.
GMT — Greenwich Mean Time. A solar time scale based on the mean position of the sun over Greenwich. Functionally identical to UTC for most software purposes (both are offset 0, no DST), but legally distinct in the UK where GMT is the winter standard time and BST is summer.
Zulu (Z) — Military shorthand for UTC. Z in an ISO 8601 timestamp (2024-01-15T10:30:00Z) means the same as +00:00.
Use UTC for new systems. Store, log, and exchange in UTC. Convert to a named zone only at the presentation layer.

ISO 8601 offset notation

ISO 8601 timestamps include an explicit offset from UTC. Forms you will see:

2024-01-15T10:30:00Z — UTC, Zulu form.
2024-01-15T10:30:00+00:00 — UTC, explicit offset.
2024-01-15T19:30:00+09:00 — Seoul (KST). Same instant as the two above.
2024-01-15T05:30:00-05:00 — New York (EST). Same instant.
2024-01-15T10:30:00 — local time, no offset. Avoid — this loses information and is impossible to convert without out-of-band context.

Always include the offset. APIs that drop it produce subtle bugs when clients and servers are in different zones.

Daylight saving time pitfalls

Spring forward gap. On the day clocks jump from 02:00 to 03:00 (most of US/Europe), wall-clock times like 02:30 do not exist. Most libraries silently round forward to 03:30 — verify if your scheduling logic depends on the exact slot.
Fall back ambiguity. When clocks roll from 02:00 back to 01:00, the 01:30 slot occurs twice. Storing only the wall-clock time loses the disambiguation; store UTC plus zone, or carry an explicit offset.
DST schedules drift politically.Brazil dropped DST in 2019. Egypt re-adopted it in 2023. Iran abolished it in 2022. Chile delayed its start in 2022. Australia's Lord Howe Island has a 30-minute offset shift. Always rely on an up-to-date tzdata — never hard-code offsets.
Northern vs. southern hemisphere.Sydney is in DST when New York is not, and vice versa. A weekly meeting between them moves by an hour twice a year on each side's transition (and twice more on the other side's). Confirm the next two meetings whenever a transition is near.
The US vs. EU transition gap. The US transitions on the 2nd Sunday of March; the EU transitions on the last Sunday of March. For two weeks, the New York-to-London offset is 4 hours instead of the usual 5. Calendar invitations across the Atlantic get this wrong all the time.

Common use cases

Scheduling meetings with distributed teams
Planning product launches across markets (announcement at 09:00 local)
Correlating logs from multi-region infrastructure (server in UTC, ops in local)
Translating customer event timestamps before raising support tickets
Picking a deployment window that avoids every team's working hours
Sanity-checking cron schedules that fire across DST transitions
Booking flights and calls with international clients

Troubleshooting

The converter shows an offset different from my watch.Your operating system's ICU/tzdata version may lag behind the latest IANA release. Update the OS (or browser on platforms where it bundles tzdata, like Firefox); if a country recently changed DST, the database may not have caught up.
The same time appears twice on the same day. You are looking at a fall-back DST day. The 01:30 hour really does occur twice; choose between the pre-DST (still summer) and post-DST (winter) instant.
The converter rejects a time. You picked a time in the spring-forward gap. 02:30 on the transition day does not exist; pick 01:30 or 03:30 instead.
Conversions look right but log timestamps still disagree.Logs may be in the server's local zone, not UTC. Run timedatectl on the server to confirm. Force logs to UTC via TZ=UTC in the systemd unit.

Frequently asked questions

Q: Why does the converter show a different result than my watch?

Q: Should I store local time or UTC in my database?

Q: What is the difference between `UTC` and `GMT`?

Q: Why do some zones show offsets like +05:30 or +05:45?

Q: How does the converter handle the DST transition day?

Q: Can I use this for a fixed-offset zone like "UTC+5"?

Related guides

Cron Expressions Explained: A Complete Scheduling Guide

Cron looks easy until you need "every 15 minutes only on weekdays" and stop trusting your own math. The five fields with examples for Linux crontab, GitHub Actions, and Kubernetes CronJob.

API Testing with HTTP Headers: A Hands-On Guide for Developers

Most API bugs live in the headers. Authentication, CORS preflight, cache-control, content negotiation, and the X-Request-ID pattern that makes distributed tracing actually work.