Unix Timestamp Converter

Convert Unix timestamps to human-readable dates and vice versa. Supports seconds and milliseconds.

Your data never leaves your browser

How to Use

  1. 1

    Enter a timestamp or date

    Type a Unix timestamp (e.g., 1700000000) or a date string (e.g., 2024-01-15T10:30:00Z).

  2. 2

    Click Transform

    The tool detects the input format and converts accordingly.

  3. 3

    View the result

    See the converted value in multiple formats: UTC, ISO 8601, local time, and both seconds and milliseconds timestamps.

What is Unix Timestamp Converter?

A Unix timestamp — also called Epoch time, POSIX time, or simply "seconds since 1970" — is a single integer that pinpoints an exact moment in time. It counts the number of seconds elapsed since midnight UTC on January 1, 1970 (the Unix Epoch), ignoring leap seconds. Right now, the current Unix timestamp is a 10-digit number above 1.7 billion; the same moment in milliseconds is 13 digits.

Developers encounter Unix timestamps everywhere: in database rows, API response payloads, JSON Web Tokens (JWT exp and iat claims), log files, file system metadata, and HTTP headers. The format is universal because it is timezone-free — a single number means the same instant whether your server is in Tokyo or New York.

This converter handles both directions: paste a numeric timestamp (seconds or milliseconds are auto-detected) to see the human-readable date in UTC, ISO 8601, and your local timezone — or enter a date string to get the corresponding Unix timestamp. It also shows relative time ("3 hours ago") for quick sanity checks.

Common pitfalls include mixing up seconds and milliseconds (a 10-digit vs. 13-digit number), the Year 2038 overflow for 32-bit systems, and forgetting that JavaScript's Date.now() returns milliseconds while Python's time.time() returns seconds with a decimal fraction.

FAQ

What is the difference between seconds and milliseconds timestamps?
Unix timestamps in seconds are 10 digits (e.g., 1700000000). Millisecond timestamps are 13 digits (e.g., 1700000000000). JavaScript's Date.now() returns milliseconds, while most Unix systems use seconds.
What is the Year 2038 problem?
32-bit systems store Unix time as a signed 32-bit integer, which overflows on January 19, 2038. Most modern systems use 64-bit integers, which won't overflow for billions of years.
Does the tool handle timezones?
Unix timestamps are always UTC. The tool shows the result in UTC, ISO 8601, and your local timezone as detected by your browser.
What is the current Unix timestamp?
The current Unix timestamp changes every second. Open this tool and leave the input empty — it shows the live current timestamp in both seconds and milliseconds, updating in real time.
Why is it called 'Epoch' time?
An epoch is a reference point in time from which other times are measured. The Unix Epoch — January 1, 1970, 00:00:00 UTC — was chosen by the original Unix developers at Bell Labs. All Unix timestamps are measured from this point.
How do I get the current Unix timestamp in my programming language?
JavaScript: Math.floor(Date.now() / 1000); Python: import time; int(time.time()); PHP: time(); Ruby: Time.now.to_i; Go: time.Now().Unix(); Bash: date +%s. All return seconds since the Unix Epoch.

Related Articles

Related Tools