UnixFlux logo UnixFluxtimestamp observatory
TOOL · 01

Unix Timestamp Converter — read the clock inside the number

Now
—
—
seconds since epoch · click the number to copy
01 Decode a timestamp waiting

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.

STEP 1

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.

STEP 2

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.

STEP 3

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.

SCENE A

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.

SCENE B

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.

SCENE C

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 & timeWhy it matters
01970-01-01 00:00:00The Unix epoch itself — where all counting starts.
17000000002023-11-14 22:13:20A round-ish number you will meet in countless examples and fixtures.
17672256002026-01-01 00:00:00Midnight, New Year's Day 2026 — a classic cache-expiry value.
20000000002033-05-18 03:33:20Two billion seconds — handy for “far future” defaults.
21474836472038-01-19 03:14:07The Y2038 problem: the maximum of a signed 32-bit integer.
41024448002100-01-01 00:00:00Turn of the century, for genuinely long-lived records.

05Frequently Asked Questions

What is a Unix timestamp?
A Unix timestamp is the number of seconds that have passed since 00:00:00 UTC on January 1, 1970 — the Unix epoch. Databases, APIs, log files, and programming languages use it because it is a single integer that is easy to store, sort, and compare, independent of any time zone.
How do I tell seconds, milliseconds, and microseconds apart?
Count the digits. A 10-digit value such as 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?
A timestamp is an absolute moment in time; the date you see depends only on the clock you view it with. 1700000000 is 2023-11-14 22:13:20 UTC, which is already November 15 in Tokyo and still November 14 in New York. UnixFlux shows UTC, your local time, New York, London, Tokyo, and Sydney side by side so the difference is obvious.
Can I convert many timestamps at once?
Yes. Paste multiple values separated by new lines or commas — for example a column copied from a log file — and UnixFlux switches to batch mode, producing a table where every row shows the original value, its detected unit, the UTC ISO 8601 string, and your local time. Invalid rows are marked rather than dropped, and up to 300 rows are rendered at once.
What is the current Unix timestamp right now?
The dark display panel at the top of this page shows the live seconds timestamp, refreshing once per second, next to your local date and time. Click the big number to copy it. It is a handy reference when you need to eyeball whether a JWT exp claim or a log line is in the past or the future.
Does UnixFlux handle dates before 1970 or negative timestamps?
Yes. Values before the epoch are expressed as negative numbers, such as -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.
Do my timestamps get uploaded anywhere?
No. Every conversion runs in your browser as ordinary JavaScript. Nothing you paste is transmitted to a server, logged, or stored — the page even keeps working if you go offline after loading it.

Latest Articles

Guides on timestamps, JWT debugging, and log forensics are on the way — check back soon, or start with the epoch reference.