Skip to main content

Unix Timestamp Converter

Convert Unix epoch timestamps in seconds or milliseconds to human date/time.

Number of seconds (or milliseconds) elapsed since Jan 1, 1970 UTC

Presets:
UTC Date & Time
Monday, January 15, 2024 at 12:00:00 PM UTC

Unix timestamp 1705320000 (seconds) corresponds to 2024-01-15T12:00:00.000Z (2 years ago).

ISO 8601 (Standard)2024-01-15T12:00:00.000Z
Relative Time2 years ago
Day of WeekMonday
Day of YearDay 15 (Leap Year)
Seconds (Epoch)1,705,320,000
Milliseconds1,705,320,000,000
Format Variations:
ISO 8601: 2024-01-15T12:00:00.000Z
RFC 2822: Mon, 15 Jan 2024 12:00:00 GMT
Local Timezone: Mon, Jan 15, 2024, 12:00:00 PM UTC

How It Works

The Unix Timestamp Converter translates between POSIX/Unix integer timestamps and human-readable calendar dates in UTC and local time.

It automatically differentiates between 10-digit second timestamps (standard in backend databases and Unix systems) and 13-digit millisecond timestamps (standard in JavaScript).

Formula & Calculation

Unix Epoch Definition

Timestamp = Seconds Elapsed Since 1970-01-01T00:00:00Z
Epoch Base=Thursday, January 1, 1970, 00:00:00 Coordinated Universal Time (UTC)
Leap Seconds=POSIX timestamps exclude leap seconds by convention (every day = 86,400 s)

Unit Conversion Formula

Milliseconds = Seconds × 1,000 | Seconds = floor(Milliseconds / 1,000)
10-digit integer=Seconds precision (Unix / C / Python / SQL)
13-digit integer=Milliseconds precision (JavaScript Date.now())

Step-by-Step Example

Example: Converting Timestamp 1705320000

Translating timestamp 1,705,320,000 to UTC calendar time:

Step 1: Identify timestamp magnitude: 10 digits → Seconds precision→ 1,705,320,000 seconds
Step 2: Convert to milliseconds: 1,705,320,000 × 1,000→ 1,705,320,000,000 ms
Step 3: Resolve Gregorian date in UTC: Epoch + 1,705,320,000 seconds→ 2024-01-15T12:00:00.000Z

Timestamp 1705320000 corresponds to Monday, January 15, 2024, at 12:00:00 PM UTC.

Assumptions & Edge Cases

  • Year 2038 Problem (Y2038): Legacy 32-bit signed integers overflow on January 19, 2038, at 03:14:07 UTC. EverydayNumbers uses 64-bit IEEE double and decimal numbers, correctly supporting timestamps billions of years into the past and future.
  • Negative Timestamps: Negative timestamps represent dates prior to the January 1, 1970 epoch (for example, -315619200 represents January 1, 1960).

Frequently Asked Questions

Why do JavaScript timestamps have 13 digits while Unix has 10?

Standard Unix timestamps count seconds since the 1970 epoch (yielding 10 digits in the 2020s). JavaScript’s `Date.now()` counts milliseconds since the epoch, appending three additional digits.