UTILITIES WORKSPACE
Unix Timestamp Converter
Convert explicit Unix time units and dates.
Input is processed on this site only when you run the tool. The application does not save inputs or results.
input.txt
Result result.txt
A little clarity goes here.
Run the tool to see your result.
Result preview
UTF-8 text, at most 262144 bytes per input. Tab leaves the editor. Plain text disables syntax colors. Browser textareas may normalize line endings to LF.
{"from-unix":{"inputMode":"text","options":{"unit":{"type":"enum","values":["seconds","milliseconds"],"default":"seconds"},"timezone":{"type":"timezone","default":"UTC"}}},"to-unix":{"inputMode":"text","options":{"unit":{"type":"enum","values":["seconds","milliseconds"],"default":"seconds"},"timezone":{"type":"timezone","default":"UTC"}}}}{"from-unix":{"input":"0","output":"1970-01-01T00:00:00Z","options":{"unit":"seconds","timezone":"UTC"}},"to-unix":{"input":"1970-01-01T00:00:00.001Z","output":"1","options":{"unit":"milliseconds","timezone":"UTC"}}}A QUICK WALKTHROUGH
A familiar workflow,
with room to focus.
Choose From Unix or To Unix and an explicit seconds/milliseconds unit.
Use an integer string or YYYY-MM-DDTHH:mm:ss with optional 1–3 fraction digits and required Z or ±HH:mm.
Choose an IANA display timezone and convert. Input offsets determine the instant; the selected zone controls display.
When to use Unix Timestamp Converter
Translate a Unix timestamp from a log into an explicit displayed instant, or convert an ISO timestamp with a known offset back to an integer.
Read the result
Seconds and milliseconds are separate selections. The input offset determines the instant; the chosen timezone determines display, and nonzero fractions need millisecond precision.
SEE IT IN PRACTICE
Worked examples
Sample input. A result you can inspect.
From Unix example
Input
0
- Timestamp unit
- Seconds
- Display timezone
- UTC
Expected result
1970-01-01T00:00:00Z
To Unix example
Input
1970-01-01T00:00:00.001Z
- Timestamp unit
- Milliseconds
- Display timezone
- UTC
Expected result
1
Formats, limits and common errors
Choose the correct unit, include an explicit offset and switch to milliseconds to preserve a nonzero fraction.
- 64-bit runtime required. Supported UTC range is year 0001 through 9999, to millisecond precision, also subject to an in-range display date.
- No whitespace, leading plus, padded integer spellings, inferred units, missing offsets, leap seconds, impossible dates or more than three fraction digits.
- Nonzero fractions require milliseconds. -00:00 denotes unknown offset and is rejected. Numeric offsets permit hours 00–23 and minutes 00–59.
- Historical timezone offsets containing seconds are rejected instead of rounded. Millisecond outputs always show three fraction digits.
- Input: 262,144 UTF-8 bytes per text field. Output: at most 524,288 UTF-8 bytes; serialized responses have a separate 1 MiB ceiling. Size/work failures return no partial result.