Unix Epoch Timestamp Converter

Convert Unix timestamps to human-readable dates and times in your local timezone and UTC. Supports timestamps in seconds, milliseconds, or microseconds. Includes output in RFC 3339, RFC 2822, and ISO 8601 formats. Unix time counts seconds since 00:00:00 UTC on January 1, 1970 (Unix epoch), with each day always exactly 86,400 seconds (leap seconds are ignored).

Unix Timestamp
Relative
Readable (UTC)
Readable (Local)
RFC 3339
RFC 2822
ISO 8601
Seconds
Milliseconds
Microseconds

More about Unix Timestamps

What is Unix Time?

Unix time (also called POSIX time or epoch time) counts the number of seconds that have elapsed since 00:00:00 UTC on January 1, 1970. This date is known as the Unix epoch. The value is timezone-independent since it is always relative to UTC.

Timestamp Precision
PrecisionDigitsExample (2025-01-15 12:00:00 UTC)Used By
Seconds101736942400Unix/Linux, C, PHP, Python
Milliseconds131736942400000JavaScript, Java, Kafka
Microseconds161736942400000000PostgreSQL, Go, Python
Nanoseconds191736942400000000000Go, InfluxDB
Notable Timestamps
  • 0: January 1, 1970 00:00:00 UTC (the epoch)
  • -1: December 31, 1969 23:59:59 UTC (negative values represent dates before the epoch)
  • 1000000000: September 9, 2001 01:46:40 UTC (the billennium)
  • 2147483647: January 19, 2038 03:14:07 UTC (the Year 2038 problem, see below)
The Year 2038 Problem

Systems that store Unix time as a signed 32-bit integer will overflow on January 19, 2038 at 03:14:07 UTC. The maximum value, 2,147,483,647, will wrap to -2,147,483,648, representing December 13, 1901. Modern systems use 64-bit integers, which will not overflow for over 292 billion years.

Common Date Formats
  • ISO 8601: 2025-01-15T12:00:00Z (the Z suffix means UTC)
  • RFC 3339: 2025-01-15T12:00:00+00:00 (profile of ISO 8601 for internet protocols)
  • RFC 2822: Wed, 15 Jan 2025 12:00:00 +0000 (used in email headers and HTTP)

Related Tools