Read the status beside the clock before treating the displayed time as a synchronized estimate.

Start with the status

A clock face can look precise even when its source is uncertain. Clock.live keeps the status next to the time so you can see what the page is using. “Synchronized recently” means the browser accepted a recent response from a server reporting healthy synchronization. It is an estimate, not a certification of accuracy.

“Using device time” means the display follows your computer or phone clock. If an earlier synchronized estimate remains usable, the page can continue from it and identify it as the last estimate. After a clock discontinuity or loss of a usable reference, it falls back to device time. A frozen Preview on the board is a different mode: it deliberately shows a chosen instant.

Why a web clock has uncertainty

A reply takes time to travel between your browser and the server. Clock.live samples the time service three times, accounts for the server’s processing interval, and uses the accepted sample with the lowest measured network delay. The estimate assumes the remaining travel time is roughly balanced in both directions; real networks can be uneven.

When the server supplies an error estimate, the displayed estimate also accounts for network delay and a small engineering allowance for drift since sampling. If server uncertainty is unknown, the page keeps it unknown. More decimal places would not make that uncertainty disappear. The site does not claim atomic-clock precision, certified timestamping or a guaranteed maximum error.

A time source and a time zone solve different problems

The source provides an instant. A named time zone translates that instant into a local date and time. Changing from London to Tokyo should change the local reading, not the underlying moment. Named zones include daylight-saving rules; a fixed label such as UTC+01:00 describes only an offset.

The first local clock uses the zone reported by your browser. That identifies a time zone rather than your exact city, and does not require precise location permission. Select a city when you want its full place identity. Supported conversion and preview dates run from 1970 through 2100, using the pinned rules listed on the data-sources page. Future government rule changes can require a data update.

If the reading looks wrong

  1. Check the displayed date as well as the hour, especially near midnight.
  2. Check the selected city and named zone; similarly named cities can belong to different zones.
  3. Read the synchronization status. Restore connectivity or reload to request a fresh attempt if the service was unavailable.
  4. Check the device’s automatic date/time settings when the page is using device time. Independently verify any time used for a critical deadline.