What the number represents

Unix time counts elapsed seconds from the epoch, 1 January 1970 at 00:00:00 UTC. It is timezone-free: the same instant has the same timestamp in Shanghai, London and New York. Local time only appears when a program formats the number for a human.

Seconds are the standard unit in Unix and most APIs. Milliseconds are common in JavaScript, Java and browser APIs, which is why a 13-digit value usually means milliseconds and a 10-digit value usually means seconds.

  • 10 digits (for example 1763311200) — seconds, valid until the year 2286.
  • 13 digits (for example 1763311200000) — milliseconds, the JavaScript Date.now() format.
  • 16 digits — microseconds in modern epoch values; useful for profiling and tracing.
  • 19 digits — nanoseconds in modern epoch values; usually require a 64-bit integer or string.
  • 6 or 9 digits are not modern epoch units. The converter treats pure-digit values by length, so short values are interpreted as seconds.

Reading it in different formats

The same instant can be written as 1763311200, 2025-11-16T14:00:00Z, 2025-11-16T22:00:00+08:00, or Sun, 16 Nov 2025 14:00:00 GMT. All four are the same moment; only the representation differs. API bugs often come from mixing a UTC timestamp with a local date string.

text
seconds     1763311200
milliseconds 1763311200000
ISO 8601    2025-11-16T14:00:00.000Z
RFC 2822    Sun, 16 Nov 2025 14:00:00 +0000
local (UTC+8) 2025-11-16 22:00:00

Why the live clock matters

When comparing logs from several services, a live reference clock tells you whether a timestamp is plausible. A log line that claims to be from 2031 is usually a millisecond value interpreted as seconds, or a timezone applied twice.

If the live value is far from your system clock, check the device's NTP sync. A drifting clock breaks TLS, authentication and cron schedules.