Horodatage Unix actuel

Visualisez l’horodatage Unix actuel en direct en secondes et en millisecondes.

Live Unix time

seconds since the epoch (updated every second)

milliseconds since the epoch (sampled each second)

Comment ça marche

  1. The page reads your device’s clock every second and converts the current instant to epoch seconds (milliseconds floored at 1000ths), epoch milliseconds, and an ISO 8601 string.
  2. Each update re-reads the clock rather than adding one to the previous value; background-tab throttling can never make the display drift, and returning to the tab resyncs immediately.
  3. Local date, time, zone and offset rows are derived from the same instant, so every value on the page agrees with every other.

Bon à savoir

  • The millisecond display is sampled once per second; its last three digits are the fraction of the current second at the sample moment.
  • Accuracy is limited by your device clock. For certified precision, sync against an NTP source; for most API work, device time is what servers also see (± network skew).
  • Copy buttons capture the value at the moment you click; the displays keep ticking.

Foire aux questions

How accurate is the live timestamp?
It reads your device clock, second-aligned, and re-reads it every tick so it stays correct even if the tab was throttled in the background. It is only as accurate as your device clock.
Do seconds and milliseconds tick together?
Yes. Both are derived from the same instant, so the millisecond value is exactly the second value × 1000 plus the current sub-second part.
Is this the same timestamp servers see?
Within network and clock skew, yes: UTC epoch time is global. If you need certified precision, sync from an NTP source rather than any web page.