Unix Timestamp ↔ Date

Time · epoch · Unix timestamp

Convert Unix timestamps to human-readable dates and the other way around. Paste epoch seconds or milliseconds from logs, JWTs, and APIs; see local and UTC interpretations without a server round-trip.

What a Unix timestamp is

A Unix timestamp counts seconds (or milliseconds) since the Unix epoch: 1970-01-01T00:00:00Z. APIs, databases, JWT exp/iat claims, and log shippers use this form because it is compact and timezone-agnostic in storage. Humans still need calendar dates — that conversion is what this tool does.

How to use it

1. Paste a numeric timestamp or pick/enter a date-time.
2. Confirm whether the source uses seconds or milliseconds (13-digit values are usually ms).
3. Read the converted local and/or UTC display.
4. Copy the form you need into docs, SQL, or support replies.

Seconds vs milliseconds

Where timestamps show up

• JWTs — exp, nbf, iat are usually seconds; pair with the JWT Decoder.
• Logs — correlate incidents across services in UTC, then convert for stakeholders’ local time.
• Databases — epoch columns vs timestamptz; know what your driver emits.
• Cron vs epoch — schedules are wall-clock; epoch is absolute. Different tools for different jobs.

Timezones & DST

Epoch is absolute. Display depends on timezone. “Tomorrow at 9am” in New York is not a single epoch without a zone. For distributed systems, store UTC (or epoch) and localize only at the edges.

FAQ

Related tools

JWT Decoder Cron Builder Cron Parser

Part of DevToolBox — free developer utilities that run in your browser. About · Privacy