Unix Timestamp Converter — read the clock inside the number
02How UnixFlux Reads a Timestamp
A Unix timestamp is a plain integer counting time since 1970-01-01 00:00:00 UTC. UnixFlux turns that integer back into a wall clock you can actually read — in six places at once — with no keystrokes beyond the paste.
Unit detection by digit count
The parser counts digits before it counts anything else. Up to 11 digits means seconds, 12 to 14 digits means milliseconds, and 15 or 16 digits means microseconds, which is divided by 1,000 and flagged as approximate. The badge above the input shows exactly which unit was detected, so a 13-digit Java millisecond value can never masquerade as a far-future date.
Six clocks, one moment
Every valid value is rendered simultaneously as UTC (ISO 8601, the format APIs and databases speak), your system's local time, and the wall-clock time in New York, London, Tokyo, and Sydney. Daylight-saving transitions are handled by the browser's own time zone database, so the offsets you see match what the operating system would show.
Relative time, refreshed live
Next to the absolute times you get a plain-language distance from now — “2 hours ago”, “in 3 weeks” — recomputed once per second so it stays honest while the page is open. The precise difference in seconds is printed underneath for when you need the exact delta.
03Where These Numbers Come From
If you work with servers, timestamps find you. These are the three places they hide most often.
Database columns
MySQL's FROM_UNIXTIME() is fine until you are staring at a raw created_at integer in a CSV export or a query result. Paste the column here and the batch table gives you the UTC and local rendering of every row, in order, ready to compare against a business deadline.
JWT exp and iat claims
Decode a JSON Web Token and the payload is full of bare seconds values. Drop the exp number into the input and the relative line tells you instantly whether the token is already stale or good for another week — no mental math against the live counter at the top of the page.
Log files
nginx, application logs, and tracing systems love millisecond timestamps. Copy a burst of them out of a log, paste it in, and each line becomes a readable row. A sudden 3,600-second jump between rows usually means exactly what you suspect: a time zone or a DST bug upstream.
04Epoch Quick Reference
Landmark values worth recognizing on sight. Click any row in the converter above to see it across all six time zones.
| Timestamp (s) | UTC date & time | Why it matters |
|---|---|---|
| 0 | 1970-01-01 00:00:00 | The Unix epoch itself — where all counting starts. |
| 1700000000 | 2023-11-14 22:13:20 | A round-ish number you will meet in countless examples and fixtures. |
| 1767225600 | 2026-01-01 00:00:00 | Midnight, New Year's Day 2026 — a classic cache-expiry value. |
| 2000000000 | 2033-05-18 03:33:20 | Two billion seconds — handy for “far future” defaults. |
| 2147483647 | 2038-01-19 03:14:07 | The Y2038 problem: the maximum of a signed 32-bit integer. |
| 4102444800 | 2100-01-01 00:00:00 | Turn of the century, for genuinely long-lived records. |
When the number on your screen is a date you can't read
UnixFlux is built for moments when you're staring at a raw integer in a database row, a JWT payload, or a log line and need to know what wall-clock time it maps to — right now, without writing a conversion script. Paste the value, and the tool figures out whether it's seconds, milliseconds, or microseconds by counting digits, then shows you that instant across six time formats. It's for developers, SREs, and anyone debugging time-sensitive data who just needs the answer fast.
Turning a raw integer into a human timestamp
- Click the now (s) button to load the current Unix timestamp and see it decoded instantly.
- Try 1700000000 · s or 1700000000000 · ms to confirm the unit detection picks the right precision.
- Hit New Year 2026 to preview a future date across all six output clocks at once.
- Load the batch demo to convert several timestamps together instead of pasting them one by one.
- Press Clear when you're done to reset the input field and start over with a fresh value.
05Frequently Asked Questions
What is a Unix timestamp?
How do I tell seconds, milliseconds, and microseconds apart?
1700000000 is seconds; a 13-digit value such as 1700000000000 is milliseconds; a 16-digit value such as 1700000000000000 is microseconds. UnixFlux applies these rules automatically, converts everything to milliseconds internally, and labels the unit it detected on every result.Why does 1700000000 show a different date in my time zone?
Can I convert many timestamps at once?
What is the current Unix timestamp right now?
exp claim or a log line is in the past or the future.Does UnixFlux handle dates before 1970 or negative timestamps?
-3600 for 1969-12-31 23:00:00 UTC. UnixFlux accepts them and renders them across all six time zones, just like positive values. The only hard limit is the range JavaScript dates can represent — roughly 275,760 years in either direction.