Modern distributed systems emit Unix timestamps at four distinct precisions depending on the runtime and telemetry layer: POSIX tools and JWT exp/iat claims emit 10-digit seconds, JavaScript Date.now() and Java Instant.toEpochMilli() emit 13-digit milliseconds, PostgreSQL and Python datetime internals store 16-digit microseconds, and OpenTelemetry spans, Go time.UnixNano(), and Linux clock_gettime(CLOCK_REALTIME) emit 19-digit nanoseconds.
When you paste a 19-digit nanosecond timestamp such as 1784125800452819307 and select America/New_York as the target IANA timezone, the converter splits the integer quotient and sub-second remainder via 64-bit BigInt arithmetic and produces every wire format and scaled unit simultaneously:
{
"input": "1784125800452819307",
"detectedUnit": "nanoseconds (19-digit)",
"iso8601Utc": "2026-07-15T14:30:00.452819307Z",
"rfc3339TargetTz": "2026-07-15T10:30:00.452819307-04:00",
"targetTimezone": "America/New_York (EDT, UTC-04:00)",
"rfc2822Utc": "Wed, 15 Jul 2026 14:30:00 +0000",
"units": {
"seconds": "1784125800",
"milliseconds": "1784125800452",
"microseconds": "1784125800452819",
"nanoseconds": "1784125800452819307"
}
}
For log triage and database migrations, paste newline-separated rows mixing raw integers across precisions, negative pre-1970 epochs, and RFC 3339 strings for bidirectional normalization in a single pass:
# Input (newline-separated mixed batch)
1784125800
1784125800452
1784125800452819307
-14182940
2026-07-15T23:30:00+09:00
# Normalized Output (UTC ISO-8601 | Epoch Seconds | Detected Format)
2026-07-15T14:30:00Z | 1784125800 | seconds (10-digit)
2026-07-15T14:30:00.452Z | 1784125800 | milliseconds (13-digit)
2026-07-15T14:30:00.452819307Z | 1784125800 | nanoseconds (19-digit)
1969-07-20T20:17:40Z | -14182940 | seconds (signed pre-1970)
2026-07-15T14:30:00Z | 1784125800 | RFC 3339 / ISO-8601 string