Timestamp Converter

Convert between Unix epoch timestamps and human-readable date/time formats. All processing happens locally in your browser.

Seconds or milliseconds since epoch (1 Jan 1970 UTC).
UTC
Local
ISO 8601
RFC 2822
Relative
Read as
Seconds
Milliseconds
ISO 8601

About Unix Timestamps

A Unix timestamp (or epoch time) is the number of seconds that have elapsed since 1 January 1970 00:00:00 UTC. It is widely used in programming, databases, and APIs to represent points in time in a timezone-independent way.

The unit matters more than it looks. A millisecond value from the year 2000 is smaller than many second values from today, so guessing by magnitude gets it wrong; this page decides by digit count instead and shows you which unit it settled on, so you can override it. Time zones come from the browser's own database, and entering a wall clock converts it from that zone rather than from UTC, which is the part most converters quietly get wrong. Relative phrasing comes from the browser too, so it reads correctly in each language.

Reshaping data by hand again?

A payload you have to fix in a browser tab every time is a job for code. We build the integrations, parsers and services that move data between systems, and we repair the ones that quietly corrupt it on the way through.

Tell us what you are moving

Frequently Asked Questions

How do I know if a number is seconds or milliseconds?
By its length, not its size. Ten digits is seconds, thirteen is milliseconds, sixteen is microseconds and nineteen is nanoseconds. Judging by magnitude fails, because a millisecond value from the year 2000 is smaller than a second value from today. The page shows which unit it used so you can correct it.
What is a Unix timestamp counting from?
The first instant of 1970 in UTC, ignoring leap seconds. That epoch is why timestamps are the same number everywhere in the world: the value carries no time zone at all, and a zone only enters when you turn it into a date a person can read.
Does the date to timestamp direction use my time zone?
It uses whichever zone you select, and the offset for that particular date, so a summer date gets summer time. This is worth checking in any converter you use, because reading an entered wall clock as UTC is a common mistake and it shifts every result by your offset.
Why does the same timestamp show a different date for me?
It does not. The instant is the same everywhere; only the wall clock differs. A timestamp that reads as late evening in London reads as the next morning in Tokyo, which is why a log timestamp should always be compared in a stated zone rather than in whatever the reader's machine is set to.
Can I convert a whole column at once?
Yes. Paste one timestamp per line into the batch tab and each line comes back with its ISO 8601 form in the selected zone. Lines that are not numbers are returned with the reason, so a bad row does not stop the rest.