Epoch Converter
Current epoch time
Timestamp to date
Paste an epoch in seconds, milliseconds, microseconds or nanoseconds. The unit is detected from the magnitude. Date strings like 2026-07-22T09:00Z work too.
Epoch to UTC, PST, EST and other time zones
The current time in each zone. Paste a timestamp above to convert that instant instead.
Date to timestamp
Pick a date and time, interpreted in your local zone or UTC.
Unix timestamps to dates and back, read across every zone you care about, with the unit detected for you.
Converting epoch time to UTC, PST and EST
An epoch value is an instant, not a time of day. It names the same moment everywhere on Earth, and a time zone only decides how that moment is written down. So 1787744559 is one instant that reads as 04:22 in UTC, 21:22 the previous day in Los Angeles and 09:52 in Kolkata.
The table above does all of those at once: UTC, Los Angeles, Denver, Chicago, New York, São Paulo, London, Berlin, Dubai, Kolkata, Shanghai, Tokyo and Sydney, plus your own zone when it is not already among them. Abbreviations are worked out from the date rather than hardcoded, so a June timestamp in New York reads EDT and a December one reads EST. Getting that backwards is the most common error in a hand-written conversion, and it is an hour wrong every time.
Seconds, milliseconds, microseconds and nanoseconds
The unit is readable from the length. A present-day timestamp is 10 digits in seconds, 13 in milliseconds, 16 in microseconds and 19 in nanoseconds, and those magnitudes are far enough apart to tell without being told. Paste any of them and the unit is detected; override it from the dropdown if a value comes from somewhere unusual.
Reading milliseconds as seconds is the classic mistake: it puts the date somewhere around the year 56000 rather than this week, which at least fails loudly. The reverse is worse, because seconds read as milliseconds land in January 1970 and look plausible enough in a log to be believed.
ISO 8601 with the right offset
Every row gives ISO 8601 carrying that zone's own offset, such as 2026-08-26T09:52:39+05:30, rather than normalising everything to a Z suffix. Both describe the same instant, but the offset form keeps the zone the reading was taken in, which is what you want when the string is going into a bug report, a changelog or a message to somebody in another country.
Epoch time FAQs
What is Unix epoch time?
The number of seconds elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is the standard machine representation of time: compact, timezone-free, and trivial to compare and sort, which is why logs, databases and APIs use it everywhere.
Is my timestamp in seconds or milliseconds?
You can tell by length: current dates are 10 digits in seconds and 13 in milliseconds. Microseconds are 16 digits and nanoseconds 19. This converter detects the unit automatically from the magnitude, so pasting any of them just works, and you can override the detection if you need to.
What is the year 2038 problem?
Systems that store epoch seconds in a signed 32-bit integer overflow on 19 January 2038 at 03:14:07 UTC. Modern platforms use 64-bit time values, which postpone the problem by roughly 292 billion years, but old embedded systems and legacy file formats can still be affected.
How do I convert an epoch timestamp to PST or EST?
Paste the timestamp and read the zone table. It shows the instant in UTC, Los Angeles, Denver, Chicago, New York, São Paulo, London, Berlin, Dubai, Kolkata, Shanghai, Tokyo and Sydney at once, plus your own zone if it is not already listed. The abbreviation follows the date rather than being fixed, so a July timestamp reads PDT and a January one reads PST, which is the detail most conversions get wrong.
How do I convert epoch milliseconds rather than seconds?
Just paste them. A 13-digit value is milliseconds, 16 is microseconds and 19 is nanoseconds, and the unit is detected from the magnitude. If you have a value from an unusual source, the dropdown next to the input forces a specific unit instead.
Does epoch time depend on my timezone?
No. An epoch value names one instant, identical everywhere on Earth. Timezones only change how that instant is displayed as a wall-clock date. That is why this page shows the same timestamp as both UTC and your local time: same moment, two renderings.
How do leap seconds affect Unix time?
Unix time pretends leap seconds do not exist: every day is exactly 86,400 seconds. When a leap second is inserted, Unix clocks typically repeat or smear a second. For everyday conversion this is irrelevant, but it matters in timekeeping systems that need sub-second accuracy across decades.
Is anything I enter sent to a server?
No. Conversion happens entirely in your browser and the page keeps working offline. Timestamps from logs and incident timelines can be sensitive, and they stay on your machine.