Unix Timestamp to Date Converter

Convert a Unix epoch timestamp (seconds or milliseconds) to a human-readable date and time. This page is dedicated to the unix timestamp to date converter — paste your value and get the result instantly, right in your browser.

What is a Unix Timestamp and Why Does It Matter?

Every time your application records when something happened — a user signed in, a payment cleared, an error was thrown — it almost certainly stores that moment as a Unix timestamp. The format is deliberately simple: a single integer counting seconds (or milliseconds) since midnight on 1 January 1970, UTC. No timezone, no locale, no ambiguity. Two servers on opposite sides of the planet will always agree on what 1705320000 means.

The problem is that humans are not good at reading integers. 1705320000 tells you nothing at a glance — you need a converter. This tool is that converter, and it works in all three directions you might need.

Three Conversion Modes

• Unix → Date: Paste any 10-digit (seconds) or 13-digit (milliseconds) epoch integer and instantly get back the equivalent ISO 8601 string, UTC-formatted date, and your local time. Useful when tailing logs or inspecting a database row and you want to know exactly when that record was created.
• Date → Unix: Type or paste a human-readable date — in ISO 8601, RFC 2822, or a natural short form like 2024-01-15 — and get back the Unix seconds, milliseconds, and the normalized ISO string. Handy when crafting an API request that expects a since or before epoch parameter.
• ms → seconds: A quick-division helper for when you have a JavaScript Date.now() value (milliseconds) and need the traditional Unix seconds form — for example, when writing to a POSIX-style system call, a cron expression parser, or a Go/Rust API that expects i64 seconds.

The Live Epoch Ticker

At the top of the tool is a live clock showing the current Unix epoch in both seconds and milliseconds, updated every second. This is handy when you need to grab the current timestamp to paste into a terminal command (date -r 1705320000), a SQL WHERE clause, or a feature flag configuration — without interrupting your flow to open a terminal.

Common Use Cases

• Reading application logs — timestamps from AWS CloudWatch, Datadog, or Nginx are often Unix integers.
• Debugging JWT tokens — the iat (issued at) and exp (expires at) claims are Unix seconds.
• Building API requests — REST and GraphQL endpoints frequently accept date ranges as epoch parameters.
• Data migrations — converting a CSV column of human-readable dates to Unix seconds for database import.
• Checking Last-Modified headers — HTTP timestamps need translating to a date to be meaningful.

Seconds vs Milliseconds — a Common Source of Bugs

One of the most common timestamp bugs in JavaScript is mixing up seconds and milliseconds. Passing a 10-digit seconds value to new Date() (which expects milliseconds) produces a date in January 1970. Passing a 13-digit millisecond value to a Python datetime.utcfromtimestamp() (which expects seconds) gives a date far in the future. This tool auto-detects the unit by digit count and labels the output clearly so you always know which format you are working with.

All conversions run entirely in your browser. No timestamp you enter is ever transmitted to any server. You can safely use this tool with production timestamps, internal system logs, or any other time data you would rather keep private.