How to use Unix Timestamp Converter
- Choose timestamp-to-date, date-to-timestamp, ISO inspection or ISO construction.
- For a timestamp, explicitly choose seconds or milliseconds. Seconds accept an optional fraction; milliseconds must be whole numbers. For a named-zone date, enter its date, time and zone.
- ISO inspection accepts a date or an ISO timestamp. ISO construction uses a date, time and fixed offset such as Z or +06:00.
- Use the current-time button to fill the active mode from your device. It fills once; the nearby clock keeps ticking.
- Review the UTC value and any repeated-hour choice or warning. Dates without a time and offset do not identify an instant.
Example: Unix Timestamp Converter
Convert a seconds-based epoch value to midnight UTC on New Year’s Day.
Options
- Is that timestamp in seconds or milliseconds?
- Ten digits is usually seconds and thirteen digits is usually milliseconds, and the tool suggests a unit from the digit count. The choice stays yours, so a pasted millisecond value is never divided without telling you.
- Time zone for that date and time
- For an instant, the zone changes the displayed clock and can change the calendar day without changing the timestamp. UTC is also shown. An ISO calendar date without a time and offset does not identify an instant.
- If the local time happens twice
- Used only when a date and time falls inside a repeated hour. The earlier occurrence is the default.
- ISO inspection and construction
- Inspect YYYY-MM-DD or a timestamp such as 2026-01-01T12:00:00+06:00. Construct uses the Date, Time and ISO offset fields. A date alone has no instant. A fixed offset is separate from a named time zone and has no daylight saving rules.
- Exact microseconds and nanoseconds
- Choose explicit integer microseconds or nanoseconds. Arithmetic uses BigInt, preserves exact UTC fractions and shows coarser integer units truncated toward zero.
- Batch conversion and fractional dates
- Enter up to 1,000 timestamps, one per line, to export exact values as CSV. For date-to-timestamp microseconds or nanoseconds, add an optional 0.x fractional second with up to nine digits.
Supported inputs and limits
- Timestamp input accepts seconds from -2208988800 (1900-01-01T00:00:00Z) through 4102444800 (2100-01-01T00:00:00Z), or whole milliseconds, microseconds or nanoseconds for the same span.
- Seconds may have a fraction.
- Clock rows show whole seconds.
- Exact microsecond, nanosecond and batch results retain nine decimal places in UTC.
- Date/time and ISO inputs use calendar years 1970–2100.
More details
ISO timestamps need seconds and Z or ±HH:mm, with up to three fractional digits.
Overflow dates, leap seconds, -00:00 unknown offsets, week dates and ordinal dates are refused.
The unit stays an explicit choice; digit-count suggestions are hints.
The earlier occurrence is selected by default for a repeated named-zone reading.
Current-time controls use the device clock; browser zone data can be outdated.
Exact timestamp conversion supports the same 1900-to-2100 epoch range.
Single seconds with more than three fractional digits and all batch timestamps use exact subsecond arithmetic.
Named-zone clock rows show whole seconds;
UTC retains nine fractional places.
Date/ISO validation and browser time-zone-data limits still apply.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
The zone changes the clock, not the instant
A timestamp names a moment, not a place. Reading 1767225600 in UTC gives 2026-01-01 00:00:00, and reading the same value in a zone ahead of UTC gives a later clock time, still on the same number. The instant is fixed, so the zone only decides which local clock you compare it against.
Questions about Unix Timestamp Converter
Is a 10-digit number seconds and a 13-digit number milliseconds?
Usually. 1767225600 is a second value and 1767225600000 is the same instant in milliseconds. The tool suggests a unit from the digit count, but you confirm it, so a genuine 10-digit millisecond value is not misread.
What date is timestamp 0?
1970-01-01 00:00:00 UTC, the reference point the Unix clock counts from.
Why does a negative timestamp show a 1969 date?
Minus 1 counts one second before the reference point, which is 1969-12-31 23:59:59 UTC.
Does the time zone change the timestamp?
No. One instant is the same number everywhere. The zone changes the clock reading and can move the calendar day, and the result shows UTC next to the zone you picked.
Can I enter a fraction of a second?
Yes, when Timestamp is in seconds. For 1767225600.75, the whole-second clock row shows 00:00:00 and the UTC value includes .750 seconds. Millisecond input must be a whole number. Select microseconds, nanoseconds or batch conversion to retain exact values down to nanoseconds.