Timestamp Converter

Convert between Unix epoch and human-readable dates

Now: 1780696263 · 2026-06-05T21:51:03.179Z
UTC:Fri, 05 Jun 2026 21:51:03 GMT
ISO:2026-06-05T21:51:03.000Z
Local:Fri Jun 05 2026 21:51:03 GMT+0000 (Coordinated Universal Time)
Relative:now
Epoch (s):1780696263
Epoch (ms):1780696263179
UTC:Fri, 05 Jun 2026 21:51:03 GMT
Relative:now

What is a Unix timestamp?

A Unix timestamp is the number of seconds (or milliseconds) since 1970-01-01 00:00:00 UTC, the 'epoch'. It's the standard time format in databases, log files, APIs, and most programming languages. Seconds-based timestamps are 10 digits long today; millisecond timestamps are 13 digits.

The converter accepts both formats, auto-detecting based on length, and renders the result in your local timezone, UTC, and ISO 8601 — pick whichever your downstream system needs. The reverse direction works too: enter a date and get the corresponding timestamp.

Examples

InputResult
17000000002023-11-14T22:13:20Z (UTC) · ISO 8601
2024-01-01T00:00:00Z1704067200 (seconds) · 1704067200000 (ms)

Frequently asked questions

Seconds or milliseconds?

Most APIs use seconds (10-digit timestamps). JavaScript's `Date.now()` and many newer systems use milliseconds (13-digit). The tool auto-detects based on length.

Is the timestamp timezone-aware?

The timestamp itself is always UTC. Display is in your local timezone by default; toggle to show UTC or ISO 8601 with offset.

What happens after the year 2038?

32-bit signed Unix timestamps overflow at 03:14:07 UTC on 2038-01-19 (the Year 2038 problem). 64-bit timestamps are immune — most modern systems already use them.

Can I convert between timezones?

Pick your target timezone in the output panel. The conversion is purely a display change — the underlying timestamp doesn't move.

Is anything uploaded?

No — conversion runs in your browser using the native `Date` API.