Timezone Converter
Convert Unix timestamps, compare timezones, and format dates instantly.
Current Time
Unix (seconds)
1778637451
Unix (milliseconds)
1778637451163
Local Time
2026-05-13 01:57:31
UTC Time
2026-05-13 01:57:31
Input
Output
Enter a timestamp or date to see results
Quick Comparison
| City | Timezone | Time | Offset | DST |
|---|---|---|---|---|
| UTC | UTC | 2026-05-13 01:57:31 | UTC+00:00 | — |
| Seoul | Asia/Seoul | 2026-05-13 10:57:31 | UTC+09:00 | — |
| Tokyo | Asia/Tokyo | 2026-05-13 10:57:31 | UTC+09:00 | — |
| Shanghai | Asia/Shanghai | 2026-05-13 09:57:31 | UTC+08:00 | — |
| Mumbai | Asia/Kolkata | 2026-05-13 07:27:31 | UTC+05:30 | — |
| Berlin | Europe/Berlin | 2026-05-13 03:57:31 | UTC+02:00 | Active |
| London | Europe/London | 2026-05-13 02:57:31 | UTC+01:00 | Active |
| New York | America/New_York | 2026-05-12 21:57:31 | UTC-04:00 | Active |
| Chicago | America/Chicago | 2026-05-12 20:57:31 | UTC-05:00 | Active |
| Los Angeles | America/Los_Angeles | 2026-05-12 18:57:31 | UTC-07:00 | Active |
Real-time Clock
Live-updating Unix timestamp and UTC/local time, refreshed every second.
DST Auto-Detection
Automatically detects Daylight Saving Time status for every timezone.
100% Client-Side
All conversions happen locally in your browser. No data is ever sent to a server.
About the Timezone Converter
The Timezone Converter translates a moment in time across IANA timezones — Asia/Seoul to America/Los_Angeles, UTC to Europe/London, anywhere in the 600+ zone database. Pick the source zone and time, choose target zones, and the converted times render with DST-aware offsets. Backed by dayjs with the timezone plugin, the converter handles historical zones, half-hour offsets (India, Iran), and 45-minute offsets (Nepal). Everything runs client-side; nothing about your meeting times leaves the browser.
Updated: May 8, 2026
Related Tools
Cron GeneratorBuild cron schedules with timezone-aware next-fire previews.Try it JSON ViewerInspect API timestamps in ISO 8601 / RFC 3339 format.Try it UUID Generatorv7 UUIDs embed a millisecond Unix timestamp — pair with timezone conversion.Try it Diff CheckerCompare two timestamp lists side-by-side.Try it Regex TesterBuild patterns to extract timestamps from log files.Try it
How to use the converter
- Enter a Unix timestamp (seconds or milliseconds — auto-detected) or a date string (ISO 8601, RFC 2822, or common formats like "2026-05-08 10:30:00") into the input field.
- The detected input type and parsed result appear instantly, with relative time ("3 hours ago") shown alongside.
- Pick an output format from the dropdown: ISO 8601, RFC 2822, SQL timestamp, Unix seconds, Unix milliseconds, short date, short time, or full ("Friday, May 8, 2026 10:30:00 AM").
- The Quick Comparison table shows your input mapped to 10 preset cities (Seoul, Tokyo, Shanghai, Mumbai, Berlin, London, New York, Chicago, Los Angeles, plus UTC) — each row reports local time, UTC offset, and DST status.
- Use the Now button to fill the input with the current timestamp; the live clock at the top updates every second.
Common use cases
- Cross-team meeting planning — confirm "Friday 10am PT" lands on a sane time in Seoul, Bangalore, and London before sending the calendar invite.
- On-call schedule verification — when an alerting policy says "page primary at 03:00 UTC", the converter shows what local time that is for each on-call engineer.
- Release window communication — "deploy at 2am Pacific" needs to be communicated as a local time for Asia-Pacific stakeholders to book around.
- Historical timestamp investigation — log lines in UTC need to be cross-referenced against business-hours behavior in the affected region.
- Travel scheduling — flight departure in Seoul, arrival in Frankfurt with a connection in Dubai — the converter shows the actual elapsed time.
Privacy and security
dayjs and its timezone + UTC plugins run entirely in your browser. The IANA timezone database is bundled into the page (about 30 KB after gzip). No outbound request is made — your meeting times, calendar events, and time conversions never touch a server.
Tips and pitfalls
- Daylight Saving Time differs by hemisphere and country. The US shifts in March/November; Europe in March/October; the Southern Hemisphere is the opposite. The converter applies the correct DST status for the date you entered, which can flip a meeting time by an hour in transition weeks.
- India Standard Time (IST) is UTC+5:30 — a half-hour offset. Nepal is UTC+5:45. Confused with Iran Standard Time (also IST, UTC+3:30). Always use the full IANA zone name (Asia/Kolkata, Asia/Tehran) to disambiguate.
- Some zones changed historical offsets — Russia abolished DST in 2014, North Korea swapped to KST in 2018. dayjs uses the current IANA database, so converting timestamps from before those changes might show the modern offset, not the historical one.
- Windows zone names differ from IANA. "Pacific Standard Time" (Windows) is "America/Los_Angeles" (IANA). Cloud schedulers and most APIs use IANA; the converter rejects Windows names with a clear error.
- UTC offset shorthand (UTC+9) is ambiguous — Korea, Japan, parts of Indonesia, and Yakutsk all share that offset but have different DST rules. Prefer named zones (Asia/Seoul) over offsets in stored data.
Frequently Asked Questions
- How are timezones identified?
- By IANA Time Zone Database identifiers — region/city pairs like "Asia/Seoul", "America/Los_Angeles", "Europe/London". The IANA database is the canonical reference and is updated regularly to track political timezone changes.
- Does the converter handle DST correctly?
- Yes. dayjs with the timezone plugin uses the bundled IANA database and applies DST offsets based on the date you entered. A meeting at 10am Pacific on March 15 reflects PST (UTC-8); on March 20 it reflects PDT (UTC-7) automatically.
- What about half-hour and 45-minute offsets?
- Fully supported. India (UTC+5:30), Iran (UTC+3:30), Newfoundland (UTC-3:30), Nepal (UTC+5:45), Chatham Islands (UTC+12:45). The converter renders the exact offset for each zone.
- Is the IANA database up to date?
- The dayjs version bundled here uses the most recent IANA tzdata as of 2026. For applications that store timestamps long-term, refresh the database periodically — political timezone changes (Samoa's dateline jump in 2011, Turkey abandoning DST in 2016) can affect historical conversions.
- How do I share a converted time with a teammate?
- The URL automatically encodes the source time and selected zones. Copy the URL from the address bar (or use the Share button) and your teammate sees the same conversion. Useful for documentation: paste the link into a ticket or chat.
- Why do some zones share UTC+9?
- Korea (KST), Japan (JST), parts of Indonesia (WIT), and Yakutsk Time all use UTC+9 but they have different historical and political contexts. KST does not observe DST; JST does not observe DST; some Indonesian provinces do not. The IANA name disambiguates these even when the current offset is identical.
- Does the converter work offline?
- Yes. After the first page load, the IANA database is cached in your browser. All conversions happen locally without any network call. Disconnect from the network and the tool continues to work.
- What about UTC versus GMT?
- For most practical purposes they are interchangeable. UTC (Coordinated Universal Time) is the modern atomic-clock-based standard; GMT (Greenwich Mean Time) is the historical solar-time standard. They differ by less than a second; software treats them identically.