UTC Timestamp Converter
Convert any UTC or ISO 8601 timestamp or Unix epoch to local and international time zones.
Convert any UTC or ISO 8601 timestamp or Unix epoch to local and international time zones.
A UTC converter turns a timestamp written in Coordinated Universal Time — the reference clock used by servers, APIs, log files, and aviation — into readable local times. UTC has no offset and never shifts for Daylight Saving Time, which is why systems store times in it. People rarely think in UTC, though, so a log entry like 2026-05-15T14:30:00Z needs translating: it is 10:30 AM in New York (EDT, UTC−4) and 7:30 AM in Los Angeles (PDT, UTC−7).
The format of the timestamp decides how it is read. An ISO 8601 value ending in Z, or with an explicit offset such as +02:00, is unambiguous. An ISO value with no Z and no offset is usually treated as the viewer's local time, which can quietly shift the result by several hours. Unix epoch time counts seconds since 00:00:00 UTC on January 1, 1970; current dates are 10 digits in seconds or 13 digits in milliseconds, and mixing the two up produces dates in 1970 or tens of thousands of years in the future. Developers debugging logs, IT and support staff matching incident times, and analysts reading exported data all run into these formats.
To use this UTC converter, paste an ISO 8601 timestamp, a 9–10 digit Unix time in seconds, or a 13-digit value in milliseconds, then press Convert or hit Enter. The result lists the date and time in Pacific, Eastern, UTC, London, Paris, and Tokyo, plus the equivalent Unix epoch in seconds. The Use now button fills in the current moment as an ISO timestamp and converts it immediately. Input that cannot be read returns an invalid-timestamp message with an example of the expected format.
ISO 8601 (2026-05-15T14:30:00Z), Unix epoch in seconds (1747318200), or milliseconds (1747318200000).
Fills in the current UTC timestamp so you can check your current local time in multiple zones.
Results are estimates for planning purposes only.
| UTC time | New York (ET) | London (GMT/BST) | Tokyo (JST) | Sydney (AEST) |
|---|---|---|---|---|
| 00:00 UTC | 7:00 PM ET (prev day) | 12:00 AM GMT | 9:00 AM JST | 11:00 AM AEST |
| 09:00 UTC | 4:00 AM ET | 9:00 AM GMT | 6:00 PM JST | 8:00 PM AEST |
| 14:00 UTC | 9:00 AM ET | 2:00 PM GMT | 11:00 PM JST | 1:00 AM AEST (next) |
| 17:00 UTC | 12:00 PM ET | 5:00 PM GMT | 2:00 AM JST (next) | 4:00 AM AEST (next) |
| 22:00 UTC | 5:00 PM ET | 10:00 PM GMT | 7:00 AM JST (next) | 9:00 AM AEST (next) |
Note: ET and AEST offsets vary by ±1 hour during Daylight Saving Time periods.
UTC (Coordinated Universal Time) is the world's primary time standard. It does not observe Daylight Saving Time and is the reference point for all other time zones.
ISO 8601 is an international standard for expressing dates and times. Format: YYYY-MM-DDTHH:MM:SSZ. For example: 2026-05-15T14:30:00Z means May 15, 2026 at 2:30 PM UTC.
A Unix timestamp (or epoch timestamp) is the number of seconds elapsed since January 1, 1970, 00:00:00 UTC. It is widely used in programming and APIs. Example: 1747318200 = May 15, 2026 at some point in UTC.
Paste the 10-digit Unix timestamp (seconds) into the input above and click Convert. The tool shows the equivalent local time in six major time zones.
Z stands for Zulu time, which is another name for UTC. A timestamp ending in Z is unambiguously in UTC — no time zone conversion needed to determine the UTC value.
Count the digits: present-day timestamps are 10 digits in seconds and 13 digits in milliseconds. For example, 1767225600 and 1767225600000 both mean January 1, 2026 at 00:00 UTC.
It is the offset from UTC for the local time shown. 2026-01-10T09:00:00-05:00 is 9:00 AM Eastern Standard Time, which equals 14:00 UTC; add back the offset's opposite to get UTC.
Eastern time is 5 hours behind UTC in standard time (early November to mid-March) and 4 hours behind during Daylight Saving Time. So 18:00 UTC is 1:00 PM EST in winter and 2:00 PM EDT in summer.