Developers
Timestamp Converter
Unix timestamp to readable date — and back — in both local time and UTC.
To date
| Conversion | | |
|---|---|---|
| UTC | |
To timestamp
| Seconds | | |
|---|---|---|
| Milliseconds | |
A “created_at”: 1758614400 in an API response, a database column full of thirteen-digit numbers, a log line to line up against an incident: the Unix timestamp is everywhere, and unreadable to the naked eye. Paste it here and the corresponding date appears immediately, in both your local timezone and UTC — clearing up the ambiguities that skew analyses. The reverse works too: pick a date and time, get the timestamp in seconds or milliseconds. The “Now” button inserts the current instant in one click. Everything is computed in your browser: free, no sign-up, no limits, and nothing about your data is sent anywhere.
How does it work?
- Paste a Unix timestamp — or a date — into the input area.
- Choose the unit: seconds or milliseconds.
- Read the conversion in local time and UTC.
- Copy the result, or click “Now” for the current instant.
Frequently asked questions
Seconds or milliseconds — how can I tell?
Count the digits: a current timestamp in seconds has ten (1758614400), in milliseconds thirteen (1758614400000). Unix and most APIs speak in seconds; JavaScript (Date.now()) and Java in milliseconds. Mixing them up lands you in 1970 or in the year 57000 — the mistake shows quickly.
Does a timestamp depend on the timezone?
No — that is its strength: a timestamp counts seconds elapsed since 1 January 1970 at midnight UTC, identical everywhere on Earth. Only its rendering as a date varies with the timezone. Hence the golden rule: store as timestamps or UTC, convert to local time only for display.
Why 1970 as the starting point?
That is the Unix “epoch”, picked by the system’s designers in the early 1970s as a convenient, recent origin. Every date since is expressed as seconds elapsed from that instant — earlier dates simply produce negative timestamps.
What is the year 2038 problem?
On systems that still store timestamps as signed 32-bit integers, the counter overflows on 19 January 2038 and wraps back to 1901. Modern 64-bit systems are safe for billions of years, but embedded hardware and legacy databases remain exposed — a genuine audit topic.