Unix Timestamp Converter
Convert Unix timestamps to readable dates and back — auto-detects seconds vs milliseconds, live current-epoch ticker.
Current Unix timestamp
1784077062
About this tool
Unix time counts the seconds since midnight UTC on January 1, 1970 — a single number that identifies a moment unambiguously, with no time zones, formats or locales to argue about. That's why it's everywhere in software: database columns, API responses, log files, JWTs, cache expiries. And it's why every developer regularly stares at 1799150400 wondering what actual day that is.
Paste any timestamp and get the answer four ways: your local time, UTC, the ISO 8601 string, and a relative description ("6 months from now") — often the version you actually wanted. The converter auto-detects the unit by digit count: 10 digits is seconds, 13 is milliseconds (the JavaScript convention), a distinction that has confused every developer at least once, usually via a date mysteriously in 1970 or the year 50,000+. Each output has its own copy button.
The reverse direction takes a date and time from a picker and produces both the seconds and milliseconds forms. And at the top, a live ticker shows the current Unix timestamp counting up each second, one click to copy — the small feature that quietly makes this the tab developers keep pinned. Everything runs locally in your browser.
How to use the Unix Timestamp Converter
- 1Copy the live current timestamp from the ticker, or…
- 2Paste any timestamp — seconds or milliseconds are detected automatically.
- 3Read it as local time, UTC, ISO 8601, and relative time; copy whichever you need.
- 4For the reverse, pick a date and time and copy the epoch in seconds or milliseconds.
Frequently asked questions
Seconds or milliseconds — which does my timestamp use?
Count the digits: current timestamps are 10 digits in seconds and 13 in milliseconds. Unix convention and most databases use seconds; JavaScript's Date.now() uses milliseconds. This converter detects the unit automatically and tells you which it assumed.
Why did my timestamp decode to January 1970?
The classic symptom of a milliseconds value treated as seconds (or a zero/near-zero value). 1970-01-01 is the epoch itself — time zero. Paste the raw value here; the auto-detection almost always resolves the confusion instantly.
What is the year 2038 problem?
Systems storing Unix time in a signed 32-bit integer overflow on January 19, 2038, when the count exceeds 2,147,483,647. Modern 64-bit systems are unaffected, but it's why legacy embedded systems and old databases need auditing — the sequel to Y2K.
Are Unix timestamps affected by time zones?
No — that's their whole point. A timestamp identifies one absolute instant; time zones only appear when you format it for humans. That's why this tool shows the same timestamp as both your local time and UTC: same moment, two renderings.
Related tools
Time Zone Converter
Convert any date and time between world time zones — DST-aware, with the live time difference shown.
Open toolDate Difference Calculator
Days between two dates — exact years/months/days, total days, weeks, and working days.
Open toolJWT Decoder
Decode JWT header and payload instantly — with human-readable expiry dates. Nothing leaves your browser.
Open toolHex Converter
Convert text to hex bytes and back, or decimal to hexadecimal — exact at any size, thanks to big-integer math.
Open tool