TextArray
100% local

Unix timestamp converter

Convert Unix timestamps to readable dates and dates back to timestamps.

Input
Output

Unix timestamp converter

A Unix timestamp counts the seconds since 1 January 1970 UTC, and it turns up everywhere: database columns, log files, JWT payloads, API responses and cron output. None of it is readable as it stands. This converter turns the number into a date you can actually use, and it works the other way round too — an ISO date goes back to an epoch value.

Paste one value per line and the whole list converts at once. The direction is detected line by line, so you can mix timestamps and dates in the same batch; pin it to one direction if you would rather be explicit. Seconds and milliseconds are told apart by magnitude — a ten-digit value is seconds, a thirteen-digit one is milliseconds — and you can fix the unit when your data is unusual. Pick the time zone your dates are read and printed in: your own, UTC, or any IANA zone such as America/New_York. Daylight saving is applied for the instant in question rather than for today, so a January timestamp gets the winter offset.

Output arrives as a readable date in your language or as strict ISO 8601 with the correct offset, optionally followed by a relative time like "3 hours ago". Lines that cannot be read are marked with a question mark and counted, so one bad row never breaks the batch, and the tally under the output shows the current Unix time on every run.

Everything happens in your browser. Timestamps from production logs and customer records are never uploaded — no server ever sees them.

FAQ

Are seconds and milliseconds detected automatically?
Yes. Anything from 100,000,000,000 upwards is read as milliseconds, so a ten-digit value is seconds and a thirteen-digit one is milliseconds. Set the unit explicitly in the options when your data does not follow that pattern.
Which date formats can it read?
ISO-like dates: 2026-07-16, optionally with a time (2026-07-16 12:00 or 2026-07-16T12:00:00.250) and optionally with Z or an offset like +02:00. The parser is deliberately strict, because 03/04/2026 means two different days on two sides of the Atlantic and guessing would be worse than refusing.
How is the time zone applied?
Dates without an offset are read as a wall clock in the zone you selected, and every printed date is rendered in it. An explicit Z or offset in the input always wins over that selection.
Can I convert a whole list at once?
Yes. Put one value per line and each is converted independently. Lines that cannot be parsed become a question mark and are counted in the tally instead of stopping the conversion.
Are my timestamps uploaded anywhere?
No. The tool runs entirely in your browser and your input never leaves your device.