Unix Timestamp Converter

Current Time
Timestamp to Date
Supports both seconds (10 digits) and milliseconds (13 digits)
Date to Timestamp
About Unix Timestamps

Unix timestamp is the number of seconds since January 1, 1970, 00:00:00 UTC (Unix Epoch).

Formats:
  • Unix Timestamp (seconds): 10 digits (e.g., 1701936000)
  • Unix Timestamp (milliseconds): 13 digits (e.g., 1701936000000)
Range:
  • Min: January 1, 1970
  • Max: January 19, 2038 (32-bit)
  • Max: Year 292 billion (64-bit)
Common Use Cases
  • Database Storage - Efficient time storage
  • API Responses - Standard time format
  • Log Analysis - Server log timestamps
  • Scheduling - Cron jobs and tasks
  • JWT Tokens - Expiration times
Format Examples
ISO 8601:
RFC 2822:
Relative:

Unix Timestamps, Decoded

A Unix timestamp counts seconds since 1 January 1970 UTC - 10 digits means seconds, 13 means milliseconds, and the tool detects which one you pasted. Conversion works both ways with timezone selection, because that is usually the real problem: the timestamp is UTC, the bug report is in local time. The format's history, the year-2038 problem and per-language quirks are collected in the Unix timestamp guide.

Timestamps turn up constantly in JWT claims (exp, iat, nbf) and in JSON API responses - paste any epoch value here to see when it actually is.

Timestamp Questions

Seconds since January 1, 1970, UTC. It's how computers track time without worrying about timezones, daylight saving, or date formats. Every language and system speaks it.

10 digits = seconds (classic Unix). 13 digits = milliseconds (JavaScript, Java, most modern APIs). This tool detects which you've got automatically.

Timestamps are always UTC. This tool shows both UTC and your local time. When storing time, stick with timestamps - convert to local only when displaying to users.

32-bit signed integers overflow on Jan 19, 2038. If you're still running 32-bit systems by then, you'll have bigger problems. 64-bit systems are fine for the next few billion years.