100% Free · Runs In Your Browser

Unix Timestamp Converter

Turn an epoch timestamp into a readable date, or a date into a timestamp. Works with seconds and milliseconds, shows UTC, your local time and ISO 8601, and displays the current Unix time live.

Unix timestamp converter

Current Unix time
—
— milliseconds

Timestamp to date

Date to timestamp

Conversions happen locally in your browser. Nothing is sent to our server.

What Is Unix Time?

Unix time counts the seconds since the Unix epoch: 00:00:00 UTC on 1 January 1970. Because it is one number that does not depend on a time zone, it is the standard way for programs, databases, logs and APIs to record when something happened. To show it to a person, the number is converted into a calendar date and a time zone, which is what this page does.

Seconds, Milliseconds and Microseconds

The same moment can be written at different precisions. The number of digits is the quickest clue:

UnitDigits todayExampleCommon in
Seconds101700000000Unix, Python, PHP, MySQL, JWT
Milliseconds131700000000000JavaScript, Java, Kotlin
Microseconds161700000000000000Some databases and logs
Nanoseconds191700000000000000000Go, high-resolution logs

A frequent bug is passing milliseconds to a function that expects seconds, which gives a date tens of thousands of years in the future. If a date looks wildly wrong, check the unit first.

Well-Known Timestamps

TimestampDate and time (UTC)
01 January 1970, 00:00:00 (the epoch)
10000000009 September 2001, 01:46:40
170000000014 November 2023, 22:13:20
200000000018 May 2033, 03:33:20
214748364719 January 2038, 03:14:07 (largest signed 32-bit value)

Useful lengths to remember: 3,600 seconds is one hour, 86,400 is one day and 604,800 is one week. To count whole working days between two dates instead, use the Business Days Calculator.

The Year 2038 Problem

Systems that keep the timestamp in a signed 32-bit integer can only count up to 2147483647, which is 03:14:07 UTC on 19 January 2038. After that the value wraps around to a negative number, which reads as a date in 1901. Current operating systems, languages and databases use 64-bit values, but old embedded devices and file formats can still be affected.

Unix Timestamps in Other Tools

Time-ordered identifiers carry the same kind of number. A UUID v7 starts with a 48-bit timestamp in milliseconds, and the checker in the UUID Generator shows the date stored inside one.

Convert a Timestamp in Your Own Code

// JavaScript (milliseconds)
Date.now()                                  // current time in ms
Math.floor(Date.now() / 1000)               // current time in seconds
new Date(1700000000 * 1000).toISOString()   // 2023-11-14T22:13:20.000Z

# Python
import time, datetime
int(time.time())
datetime.datetime.fromtimestamp(1700000000, tz=datetime.timezone.utc)

-- MySQL
SELECT UNIX_TIMESTAMP();
SELECT FROM_UNIXTIME(1700000000);

-- PostgreSQL
SELECT EXTRACT(EPOCH FROM now());
SELECT to_timestamp(1700000000);

# Linux (GNU date) and macOS
date -u -d @1700000000
date -u -r 1700000000

# Excel or Google Sheets (seconds in A1)
=A1/86400+DATE(1970,1,1)

The Excel formula gives a UTC date and time. Format the cell as a date and time to see it.

Frequently Asked Questions

A Unix timestamp, also called epoch time, is the number of seconds that have passed since 00:00:00 UTC on 1 January 1970. For example, 1700000000 is 14 November 2023, 22:13:20 UTC. It is a single number, so it is easy to store, compare and sort, and it does not depend on any time zone.

Count the digits. Current timestamps in seconds have 10 digits, for example 1700000000. In milliseconds they have 13 digits, for example 1700000000000. JavaScript and Java work in milliseconds, while Unix, Python and most databases use seconds. With Auto selected, this tool makes that guess for you.

No. It always counts from the same moment in UTC. The time zone only matters when you turn the number into a readable date, which is why this tool shows UTC and your local time side by side, and lets you pick another zone.

Older systems store the timestamp in a signed 32-bit integer, whose largest value is 2147483647. That second falls on 19 January 2038 at 03:14:07 UTC, and one second later the value overflows. Modern systems use 64-bit integers, which removes the limit for practical purposes.

Yes. A negative value is a moment before 1 January 1970. For example, -86400 is 31 December 1969, 00:00:00 UTC. Most programming languages handle it, though some older libraries do not.

No. Unix time treats every day as exactly 86,400 seconds, so leap seconds are not counted. For almost every application this makes no difference.

No. All conversions run in your browser with JavaScript, and nothing is uploaded or stored.

Explore All Free Tools

Password Generators

Account Password Generators

Security Tools

Guides

More Free Tools

Site