MMaxTools

Timestamp Converter

Convert between epoch, ISO 8601, RFC 2822 and human-readable dates — any format in.

The Timestamp Converter is the Swiss-army date tool for anyone who juggles multiple date formats: Unix epoch seconds, milliseconds, ISO 8601, RFC 2822 email dates, database literals and plain '2026-09-06 15:30' text. Paste almost any timestamp and it auto-detects the format, parses the instant, and prints every other representation side by side — each with a copy button.

The second half of the tool works in reverse: pick any date and time and instantly get all its formats, which is exactly what you need when writing an API payload, generating a test fixture, or filling a database column that expects a specific literal.

Format confusion causes real bugs — a timestamp read as seconds when it is milliseconds is off by a factor of 1000 — so the tool always labels the unit it detected. Everything parses locally in your browser.

Parse any timestamp

Accepts Unix seconds (10 digits), milliseconds (13 digits), ISO 8601, RFC 2822, or 'YYYY-MM-DD HH:MM'.

Paste any common timestamp format — the tool auto-detects what it is.

Convert a date to all formats

How to use the Timestamp Converter

  1. Paste any timestamp into the top field: 10-digit epoch, 13-digit milliseconds, ISO 8601 with Z or offset, RFC 2822, or 'YYYY-MM-DD HH:MM'.
  2. Read the detection note and the UTC date below.
  3. Copy any of the six output formats — ISO 8601, RFC 2822, local readable, epoch seconds, epoch milliseconds or date only.
  4. For the reverse direction, pick a date and time in the lower section.
  5. Copy the format your target system requires.

Frequently asked questions

What formats can this converter parse?

Unix epoch seconds (10 digits) and milliseconds (13 digits), ISO 8601 strings like 2026-09-06T15:30:00Z (with or without a timezone offset), RFC 2822 like 'Sun, 06 Sep 2026 15:30:00 GMT', and common short forms like 2026-09-06 or 2026-09-06 15:30 interpreted in your local time.

Why does the output include both seconds and milliseconds?

Different systems expect different units — Unix/POSIX and many databases want seconds, while JavaScript and several APIs use milliseconds. Having both, clearly labelled, removes the classic 1000× bug where a value is interpreted in the wrong unit.

What is RFC 2822 format?

RFC 2822 is the standard format for dates in email headers (for example 'Sun, 06 Sep 2026 15:30:00 GMT'). It is still seen in legacy systems, HTTP headers and logs. The converter produces it automatically from any parsed timestamp.

Which timezone is used when my input has no offset?

Dates without an explicit timezone (like '2026-09-06 15:30') are interpreted in your browser's local timezone, which is usually the intuitive choice. Values with a 'Z' or a numeric offset (like +02:00) are interpreted as UTC or that offset, respectively.