Skip to main content

Timestamp Converter

Convert unix timestamps to readable dates and dates back to unix time, in seconds or milliseconds.

Runs in your browser — your data never leaves your deviceFree, no sign-up

How it works

Integer input is treated as a unix timestamp: seconds (up to 11 digits) or milliseconds (13 digits), auto-detected and labelled with the result. Any other input is parsed as a date string. Either direction, you get the full picture: unix seconds and milliseconds, ISO 8601, UTC and local time, date and time parts, weekday, and a relative description.

The Now button shows the current moment — handy as a reference when reading logs or JWT expiry times.

Features

  • Unix seconds ↔ milliseconds auto-detection
  • Date strings (ISO 8601, RFC 2822, …) to unix time
  • UTC and your local time zone side by side
  • Relative description (e.g. “3 days ago”)
  • One-click current timestamp
  • 100% client-side — nothing leaves your browser

How to use

  1. Paste a unix timestamp (e.g. 1767225600) or a date string (e.g. 2026-01-01T12:30:00Z).
  2. Press Convert — or Now for the current moment.
  3. Copy the full result table if you need it.

Example

Input:  1767225600
ISO:    2026-01-01T00:00:00.000Z
Local:  (your time zone, same instant)

Frequently asked questions

Is my timestamp in seconds or milliseconds?
This tool detects it automatically: 10-digit values are unix seconds, 13-digit values are unix milliseconds. The interpretation is shown with the result, so you can confirm it picked the right one. (JavaScript commonly uses milliseconds; Unix systems and APIs like JWT use seconds.)
What is the unix epoch?
Unix time counts the seconds elapsed since 1 January 1970 00:00:00 UTC (the "epoch"). Timestamp 0 is that exact moment; 1767225600 is 1 January 2026. Negative timestamps represent moments before 1970.
Why does the local time differ from the UTC time?
UTC is the universal reference; local time is UTC shifted by your time zone (and daylight saving). Both describe the same instant. This tool always shows both, and the local row uses your browser's time zone setting.
Which date formats can I convert from?
Anything your browser can parse: ISO 8601 (2026-09-05 or 2026-09-05T12:30:00Z), RFC 2822, and most common date-time strings. ISO 8601 is recommended — unambiguous and supported everywhere.
Is my data sent to a server?
No. Conversion happens entirely in your browser using built-in date functions. Nothing you enter is transmitted anywhere — you can verify this in your browser's network inspector.