Staring at 1793469667 in a log file, a JWT expiry, or a database row and need to know what date that actually is — or the other way round? This free timestamp converter translates Unix timestamps into readable dates and dates back into timestamps, in both directions, showing UTC, your local time, and ISO 8601 side by side. Everything runs in your browser, so nothing is uploaded and no signup is needed.
How to use this timestamp converter
Three quick steps — no signup, no cost.
Enter an epoch number, or use the date picker — click “now” to load the current time instantly.
Confirm seconds vs milliseconds and whether the date is read as UTC or your local time.
Copy the UTC string, the local time, the ISO 8601 form, or the timestamp itself. That is all.
Why this timestamp converter shows every form at once
One number, four readings — so you paste the right one.
Timestamp to date for reading logs, date to timestamp for writing queries, cookies, and JWT expiry values.
An epoch value itself has no timezone — the same number reads differently in each zone, so both readings are shown together.
A ticking “now” value at the top of the tool gives you the current timestamp in one click.
Your timestamps never leave your device, because the conversion runs entirely in your browser.
Seconds or milliseconds? The mistake behind most wrong dates
One number, two units — and a factor of 1000 between them.
Count the digits. A current timestamp in seconds has 10 digits; in milliseconds it has 13. JavaScript’s Date.now() returns milliseconds, while most Linux tools, PHP, and Python return seconds — so the same moment looks like two very different numbers depending on where you copied it from.
Wrong unit, wrong century. Reading a millisecond value as seconds lands you thousands of years in the future; reading seconds as milliseconds lands you in January 1970. If your converted date looks absurd, the unit is almost always the culprit — flip it before doubting the timestamp itself.
Timezone is a reading, not part of the number. An epoch value is defined in UTC and carries no timezone of its own. The same clock time typed as “local” vs “UTC” produces two different timestamps, so always check which interpretation the tool used.
Leap seconds are ignored. Unix time treats every day as exactly 86,400 seconds and does not increment during leap seconds, so it is not identical to UTC — a distinction that matters for precision work, not for everyday log reading.
Timestamp Converter FAQs
Short, direct answers to the questions readers ask most.
The number of seconds since 00:00:00 UTC on 1 January 1970 — the Unix epoch — excluding leap seconds. Timestamp 0 is that exact moment.
By digit count: 10 digits today means seconds, 13 means milliseconds. You can override the guess with the unit toggle when a value is ambiguous.
Because the timestamp itself has no timezone — UTC and your local time are two readings of the same moment, offset by your zone (and daylight saving at that date, not today’s offset).
Yes. Negative values are dates before 1 January 1970 — for example, −86400 is 31 December 1969.
Older systems that store timestamps as 32-bit signed integers can only count up to 03:14:07 UTC on 19 January 2038 (2,147,483,647 seconds after the epoch). Modern 64-bit systems are not affected.
Yes. It runs entirely in your browser — no account, no signup, and nothing uploaded.
Related Tools
More free converters that work the same way — right in your browser.
Free json to txt converter that turns structured data into plain text, with no upload and no signup.
TXT to CSV ConverterFree txt to csv converter that turns plain text into spreadsheet-ready rows, with no upload and no signup.
CSV to JSON ConverterFree csv to json converter that turns spreadsheet data into JSON, with no upload and no signup.
XML to JSON ConverterFree xml to json converter that turns XML data into JSON, with no upload and no signup.
Try the related tools above, or go back to the Convertion homepage for more free converters.
