ClipGate Tools · Timestamp Converter

Every timestamp format, at once.

Paste Unix seconds, milliseconds, ISO 8601, or any date string. Auto-detected, converted to every major format, with timezone-aware local time. All in your browser.

100% client-side No ads Unix · ISO 8601 · RFC 2822
Why this sidebar?

ClipGate knows timestamps

ClipGate's classifier recognizes epoch numbers and ISO strings. It lets you re-copy them in any format and find them later by the human date — no digits to remember.

Timestamp

Try: 1713528896 1713528896000 2026-04-19T12:34:56Z in 3 days 2 hours ago
Waiting for input…
Unix (seconds)
Unix (milliseconds)
ISO 8601 (UTC)
ISO 8601 (local)
RFC 2822
Human (UTC)
Human (local)
Relative
Day of week
Day of year
Week of year (ISO)

About timestamps

A timestamp is just a number — the count of seconds (or milliseconds) since 1970-01-01T00:00:00Z, the Unix epoch. Every other format — ISO 8601, RFC 2822, "last Tuesday at 3:14 PM" — is a human skin over that same integer. This tool auto-detects which skin you pasted and shows all the others, so you can copy whatever your system wants.

Unix seconds vs. milliseconds — which is which?

Unix seconds is a 10-digit number today (e.g. 1713528896) and will stay 10 digits until the year 2286. Milliseconds is 13 digits (e.g. 1713528896000) and is the default for JavaScript's Date and Java's System.currentTimeMillis(). This tool auto-detects based on digit count, so you don't have to remember.

What does ISO 8601 look like?

The canonical form is YYYY-MM-DDTHH:mm:ss.sssZ — e.g. 2026-04-19T12:34:56Z. The T separates date and time; Z means UTC; +05:30 or -08:00 can replace Z to indicate a local offset. ISO 8601 is lexicographically sortable — sort the strings, you sort the instants.

Why do UTC and local time differ?

A timestamp is a single instant. UTC is the fixed reference; local time is that instant shifted by your timezone's offset (and DST, if applicable). This tool shows both UTC and your selected timezone so you can cross-check. Use the dropdown in the top-right to preview the same instant in any zone.

Is the Y2038 problem real?

Yes, for 32-bit systems. On 2038-01-19T03:14:07Z, signed 32-bit Unix seconds overflow. Most modern runtimes use 64-bit integers or doubles and are fine until well past the year 290,000,000. Legacy C, embedded firmware, and old database schemas are the ones to audit.

How does ClipGate tag timestamps?

ClipGate's classifier recognizes Unix epoch numbers and ISO 8601 strings in your clipboard history. Copy one and ClipGate stores the raw value plus a human-readable date — so you can search "that timestamp from last Tuesday" and actually find it. It can also re-copy the same instant in a different format on request.