Timestamp Converter
Unix time to a human date, and any date back to Unix time — in seconds, ms, µs or ns.
Your data is processed entirely in your browser and is never uploaded.
Tool workspace
Options
The unit your input timestamp is expressed in.
Two directions, one moment in time
A Unix timestamp counts seconds (or milliseconds, microseconds, nanoseconds) since January 1st, 1970 UTC. This tool reads that number and shows you the instant it names — then it can go the other way and turn any date you type back into the numbers.
Pick a direction
Timestamp → Date to read a number; Date → Timestamp to get the numbers for a date.
Choose the unit
Seconds is classic Unix, milliseconds is what JS Date.now() returns, µs matches Go and Postgres, ns matches Go and Rust.
Paste or use "now"
Type or paste a value and it converts live — or grab the exact current time with one click.
Two directions across one instant
A Unix timestamp counts the elapsed time since the epoch — January 1st, 1970, 00:00:00 UTC — in a chosen unit: seconds (classic Unix), milliseconds (what JavaScript's Date.now() returns), microseconds (Go, Postgres), or nanoseconds (Go, Rust). In the Timestamp → Date direction the engine rescales your number to milliseconds, builds a Date, and shows the same instant in your local time and UTC, plus a richer breakdown (day of year, ISO week, relative time). In the reverse direction it parses a human-readable date — local ISO, UTC (Z), RFC/HTTP, or a bare date — and reports the equivalent value in every unit at once. All of it runs locally on the browser's native Date engine.
Things to know
Magnitude betrays the unit
A timestamp's digit count usually tells you its unit: 10 digits is seconds, 13 is milliseconds, 16 is microseconds, 19 is nanoseconds. Load this — it's a seconds value — then try switching the unit to milliseconds and watch the date jump to 1970-Jan-01.
1753862400
Fractional seconds
A timestamp can carry a decimal part (e.g. 1753862400.5). Because the engine always rescales through milliseconds, the fractional second survives the round-trip instead of being silently dropped.
1753862400.5
Local vs UTC is not a bug
A timestamp is an absolute instant, but the same instant is displayed differently in your local timezone versus UTC. The readout shows both side by side, so an 'off by an hour' is your zone's offset — not an error in the conversion.
What the reverse accepts
Date → Timestamp parses local ISO strings (2026-08-05T12:00:00, treated as your local time), UTC ISO strings ending in Z, RFC/HTTP dates like Wed, 05 Aug 2026 12:00:00 GMT, and bare dates like 2026-08-05 (local midnight). Anything else reports the exact error.
2026-08-05T12:00:00
Try these
0
10-digit seconds — the number every Unix reference starts from.
1753862400
A typical 2020s timestamp in seconds.
1753862400000
13 digits — what new Date().getTime() returns in JavaScript.
2026-08-05T12:00:00
Switch to Date → Timestamp and watch every unit appear at once.
pair this withGenerate a fresh id → UUID Generator·Decode a token's time claims → JWT Decoder·Encode / decode values → Base64 Encode / Decode
Quick answers
Is my timestamp sent anywhere?
No. All conversion runs entirely in your browser with the native Date engine. Nothing you paste leaves your machine.
Which unit should I pick?
If the number is 10 digits long, it's seconds. 13 digits → milliseconds. 16 digits → microseconds. 19 digits → nanoseconds. When in doubt, try seconds first — the readout makes it obvious if the value looks wrong.
Why does the date look off by an hour?
A timestamp is an absolute instant; the same instant reads differently in UTC and in your local timezone. The readout shows both, side by side, so the "off by an hour" is just your zone's offset — not a bug.
What date formats can I paste?
Local ISO like 2026-08-05T12:00:00 (treated as your local time), UTC ISO ending in Z, RFC/HTTP dates like Wed, 05 Aug 2026 12:00:00 GMT, and bare dates like 2026-08-05 (local midnight).