Reviewed 2026-08-28
Unix Timestamps Across Seconds and Milliseconds
Identify units and UTC meaning before applying a display timezone.
Example input
1767225600
Expected output
2026-01-01T00:00:00.000Z
Reproducible method
- Preserve the original and create the smallest representative sample.
- Run a strict parse or validation before transformation.
- Record options, compare counts and structure, then test in the receiving system.
Common error
Seconds and milliseconds differ by a factor of one thousand.
Reduce a failure while retaining the problematic structure; this separates malformed input from unsupported behavior.
Technical limitation
Unix time omits leap seconds and local timezone intent.
A successful preview does not remove format ambiguity or downstream requirements.
Security and privacy
Do not use a client clock as a security authority.
Local processing reduces transfer risk but cannot protect a compromised browser, unsafe extensions, clipboard history, or later misuse.
Verification checklist
- Check field, record, page, or byte counts.
- Review edge cases and error output.
- Retain the original until acceptance.
- Document assumptions for automation.