What it is
The Unix Timestamp Converter turns a Unix timestamp into a readable date and a readable date back into a timestamp.
What a timestamp is
A Unix timestamp is the number of seconds since 1 January 1970 at 00:00 UTC, a moment called the epoch. It is how most systems store time internally, because a single integer is unambiguous: no timezone, no date format, no question of whether 03/04 means March or April.
That is exactly why it shows up in logs, databases, API responses, JWT tokens and cookie expiry dates, and exactly why you cannot read it at a glance.
How to use it
- Paste a timestamp to get the date, or pick a date to get the timestamp.
- Read the result in UTC and in your local time.
- Copy whichever you need.
Three things that cause bugs
Seconds or milliseconds. Unix time is seconds; JavaScript's Date.now() returns milliseconds. Feeding one where the other is expected puts you in 1970 or in the year 56000. A ten-digit number is seconds; thirteen digits is milliseconds.
Timezone. A timestamp has no timezone: it is a fixed instant. The date you read from it does, which is why the same timestamp is two different dates on two machines.
The 2038 problem. A timestamp stored in a signed 32-bit integer overflows on 19 January 2038. Modern systems use 64-bit and are fine, but old embedded code is not.
Nothing is uploaded
The whole operation runs inside your browser. Your file is never sent to a server, never stored and never seen by anyone else. No queue, no daily cap and no account.