Read the live Unix epoch, inspect exact seconds through nanoseconds, compare IANA time zones, decode log timestamps in bulk, and preserve large integers without unsafe rounding.
Live epoch · exact unit inspection · log batch decoder
Unix Time Workbench
Read one browser wall-clock instant, inspect an arbitrary epoch or offset-aware ISO date-time, compare IANA time-zone renderings, decode log timestamps in bulk, and keep exact high-resolution integers as strings or BigInt-safe values.
LIVE
—
—
—milliseconds
—microseconds* scaled
—nanoseconds* scaled
—signed 32-bit Unix diagnostic
1. Inspect an epoch or offset-aware ISO instant
Paste seconds, milliseconds, microseconds or nanoseconds as an integer, or an ISO value ending in Z or an explicit numeric offset. Auto-detection is optimized for modern Unix epoch magnitudes.
—seconds
—milliseconds
—microseconds
—nanoseconds
ISO UTC—HTTP / RFC date—Browser local—Relative—
2. Render the same instant in three IANA time zones
A Unix timestamp does not contain a time zone. These selectors only change the human-readable rendering of the same instant.
Shift or snap to a UTC boundary
3. Developer log batch decoder
Decode up to 100 non-empty rows. Use timestamp or label,timestamp. Integer units are auto-detected; offset-aware ISO rows are accepted. Invalid rows remain visible instead of disappearing.
#
Label
Input
Detected
UTC ISO
Zone A
Relative
4. Copyable audit & code recipes
The audit keeps unit precision and rendering assumptions beside the values. Runtime snippets show common current-epoch calls.
5. Snapshots, project JSON & portable state
Save up to 20 named snapshots in this browser. Export/import the full snapshot list separately. A project JSON or portable URL preserves the active inspector settings; portable URLs cap batch data at 40 rows.
#
Name
Milliseconds
UTC ISO
Actions
Clock and precision boundary: live browser wall-clock values originate from Date.now(), which returns milliseconds since the Unix epoch and may be precision-reduced by the browser. The displayed live microseconds and nanoseconds are exact scaling of that millisecond sample, not measured sub-millisecond precision. performance.now() is appropriate for monotonic elapsed-time measurements but is not a Unix epoch clock. IANA zones change rendering only. Ordinary Unix/POSIX conversion does not represent leap seconds. The workbench keeps large µs/ns integers as BigInt/string-style values rather than silently forcing them into an unsafe JavaScript Number.
Seconds and milliseconds come from the browser wall clock. Microseconds/nanoseconds remain scaled from millisecond precision; Freeze snapshot gives a stable set to copy.
Built for developer copy-and-check workflows
v264 keeps current-time shortcuts, copy actions, practical mobile controls and the governing unit/zone assumption next to the result so common log and API timestamp checks take fewer steps.