About UnixFlux — the observatory behind the integer
01Why We Built This
Every backend engineer knows the moment: a raw 1700000000 sits in a log line, a JWT payload, or a database export, and the question is simply “what o'clock is that?”. UnixFlux exists to answer it in one paste.
The problem
Unix time is a brilliant storage format and a terrible reading format. Ten, thirteen, or sixteen digits carry no visual clue about the unit, the year, or the time zone — and mental arithmetic against “roughly now” fails exactly when it matters, like deciding whether a token has expired or a certificate has lapsed.
The solution
UnixFlux reads the digits for you, detects seconds, milliseconds, or microseconds automatically, and renders the same instant as UTC ISO 8601, your local clock, and the wall time in New York, London, Tokyo, and Sydney. A live relative line — “3 minutes ago”, “in 2 weeks” — plus a per-second current-timestamp counter completes the picture.
Batch mode for logs
Paste a whole column of timestamps, separated by new lines or commas, and each one becomes a table row: original value, detected unit, UTC string, local time. Bad rows are flagged instead of silently skipped, so a malformed log entry never disappears from view.
02How It Works
All local, all the time
The parser, the unit detector, the time-zone renderer, and the batch table are plain client-side JavaScript. Nothing you paste is uploaded, logged, or stored. The page keeps converting even if your network drops.
Standards it follows
Time-zone rendering uses your browser's built-in IANA time zone database through the standard Intl.DateTimeFormat API, so daylight-saving rules match what your operating system would show. UTC output is genuine ISO 8601, the format APIs and databases expect.
Who it is for
Backend developers decoding JWT exp and iat claims, DBAs reading integer date columns, operators triaging log bursts, and QA engineers comparing server clocks. If a number ever made you wonder “is that today or last year?”, this tool is for you.