What is a Unix timestamp and how does it work?

A Unix timestamp is the number of seconds that have elapsed since January 1, 1970 00:00:00 UTC (the Unix Epoch). It provides a timezone-independent way to represent a point in time as a single integer, making it easy to store, compare, and transmit dates.

What is the Year 2038 problem for Unix timestamps?

The Y2038 problem occurs because 32-bit systems store Unix timestamps as signed integers, which will overflow on January 19, 2038. Most modern systems have migrated to 64-bit timestamps, which extends the range billions of years into the future.

How do I convert a Unix timestamp to a readable date?

In JavaScript, use new Date(timestamp * 1000) to convert a Unix timestamp to a Date object. In Python, use datetime.fromtimestamp(timestamp). Most programming languages have built-in functions for this conversion, and online tools can also do it instantly.

Why is my Unix timestamp showing a date in 1970 or 54000?

This usually means you are mixing up seconds and milliseconds. JavaScript Date expects milliseconds, while most APIs and databases return seconds — so passing a 10-digit seconds value directly into new Date() gives you a date in 1970, and passing milliseconds into Python's datetime.fromtimestamp() gives a far-future date. A 10-digit timestamp is seconds; a 13-digit one is milliseconds.

Are Unix timestamps always in UTC?

Yes — a Unix timestamp counts seconds from the Unix Epoch in UTC and has no timezone of its own. The timezone only matters when you format the timestamp into a human-readable string. This is exactly why timestamps are preferred for storing time in databases and APIs: two servers in different timezones agree on the value.

Unix Timestamps Demystified: Convert, Calculate, and Never Get Confused Again

What is a Unix Timestamp?

A Unix timestamp (also known as Epoch time or POSIX time) is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC. This date is known as the "Unix Epoch."

Example

0 = January 1, 1970, 00:00:00 UTC
1000000000 = September 9, 2001, 01:46:40 UTC
1710547200 = March 16, 2024, 00:00:00 UTC

Why Use Unix Timestamps?

Universal - No timezone confusion. A timestamp means the same thing everywhere
Sortable - Simple numeric comparison for ordering events
Compact - A single integer vs. a formatted date string
Language-agnostic - Every programming language can handle integers

Common Operations

JavaScript

// Current timestamp (seconds)
Math.floor(Date.now() / 1000);

// Timestamp to Date
new Date(timestamp * 1000);

// Date to timestamp
Math.floor(new Date('2026-03-16').getTime() / 1000);

Python

import time
from datetime import datetime

# Current timestamp
time.time()

# Timestamp to datetime
datetime.fromtimestamp(1710547200)

# Datetime to timestamp
datetime(2026, 3, 16).timestamp()

The Year 2038 Problem

Unix timestamps stored as 32-bit signed integers will overflow on January 19, 2038. Modern systems use 64-bit integers, which won't overflow for another 292 billion years.

Milliseconds vs Seconds

Unix timestamp (seconds): 1710547200 (10 digits)
JavaScript timestamp (milliseconds): 1710547200000 (13 digits)

If a timestamp has 13 digits, it's in milliseconds. Divide by 1000 to get seconds.

Convert Timestamps Now

Use our free Unix Timestamp Converter to convert between Unix timestamps and human-readable dates instantly.