When to use it
To find out what 1730000000 in a log line actually means, or what
created_at in the database looks like in your own time zone. Goes
the other way too: turn "today at 9 PM" into a Unix integer to paste
into a query.
How it works
The top bar shows the current time as Unix seconds and milliseconds, live. Enter a value into either input field below and it becomes the source. The output list shows the same instant as local time, UTC, ISO 8601, relative ("3 minutes ago"), Unix seconds, and Unix milliseconds simultaneously.
Auto-detecting seconds vs milliseconds
Ten-digit numbers are treated as seconds, thirteen-digit numbers as milliseconds. Technically those ranges overlap, but not inside any timestamp a typical app emits.
Date strings
Anything that Date() understands works — 2025-01-15T09:30:00,
2025-01-15 09:30, Jan 15 2025 9:30 AM. When a format is
ambiguous (two-digit years, locale-specific ordering), prefer ISO
8601.
Time data uses your local timezone only
Auto-detect Unix seconds/ms · ISO 8601 · relative · UTC across 6 rows simultaneously. Only the system clock is consulted — no precise location is inferred.