Paste a timestamp
An integer is detected as seconds, milliseconds, microseconds, or nanoseconds by its length, then shown in local, UTC, ISO, and a selected zone.
Try different keywords
No results found
Current time, two-way conversion, and precision detection share the first screen. Seconds, milliseconds, microseconds, nanoseconds, and several time zones need no separate page.
————An integer is detected as seconds, milliseconds, microseconds, or nanoseconds by its length, then shown in local, UTC, ISO, and a selected zone.
Choose a date and time and state whether it should be interpreted as local time or UTC to get four timestamp precisions.
Every current and converted value is directly copyable without selecting one global output format.
A Unix timestamp is a location-independent timeline whose zero point is January 1, 1970 UTC. The same number represents the same instant in Shanghai, London, or New York; the time zone only controls the clock display.
Seconds and milliseconds dominate logs and web APIs. Microseconds and nanoseconds appear in high-precision databases and system traces, but JavaScript Date stores milliseconds, so finer precision is truncated for calendar display.
Seconds10Milliseconds13Microseconds16Nanoseconds19A common 10-digit timestamp counts seconds, while 13 digits counts milliseconds. Microseconds and nanoseconds commonly reach 16 and 19 digits.
No. It measures elapsed time from the UTC Unix epoch and represents the same instant worldwide. A time zone only changes its human-readable display.
A date string may have no zone. Stating how to interpret it prevents the same fields from becoming different timestamps on computers in different zones.
Yes. They represent dates before January 1, 1970 UTC, although very distant dates may be outside the JavaScript Date range.
Older systems storing epoch seconds in a signed 32-bit integer overflow on January 19, 2038. Modern 64-bit timestamp implementations do not share that limit.