Unix Timestamp Converter

A Unix timestamp (also called epoch time or POSIX time) is the number of seconds since 00:00:00 UTC on 1 January 1970, not counting leap seconds. The moment this page loaded was a timestamp of about 1.79 billion. It is the way most operating systems, databases, programming languages and APIs store a point in time, because a single integer is unambiguous: it has no time zone, no daylight saving and no calendar quirks. Converting it to a human-readable date is done at the last moment, in whatever zone the reader is in.

The converter shows the current timestamp ticking live, converts any timestamp you paste into a date in both UTC and your local zone, and converts a date and time back into a timestamp.

A ten-digit number (1,700,000,000) is seconds; a thirteen-digit number (1,700,000,000,000) is milliseconds, which is what JavaScript's Date.now() and many APIs return. The converter detects the length and treats the value accordingly, and the output can be copied in either form. Some systems, including .NET ticks and some databases, use microseconds (16 digits) or 100-nanosecond intervals from a different epoch; those need their own conversion and will produce dates in the far future if pasted here.

• Time zones. A timestamp is always UTC. If your converted date is off by exactly a few hours, something applied a local offset twice or not at all.
• Leap seconds are ignored: every Unix day has exactly 86,400 seconds, so timestamps are a few dozen seconds away from true atomic time. Almost nothing cares.
• Date-only values. A timestamp for "3 September 2026" usually means midnight UTC, which is the evening of 2 September in the Americas. Ask which was meant.

See the current time in any city with the world clock, convert between zones with the time zone converter, and read our explainer on UTC and offsets if timestamps keep coming out wrong by a few hours. For durations, the time unit converter turns seconds into days, weeks and years.