On load, the clock sends one HEAD request to the current page, reads the server Date header, and compensates for half of the round-trip latency. If the request or header is unavailable, the offset stays at zero and the clock continues with device time instead of interrupting the display.
The selector includes local time, UTC, and common IANA time zones such as New York, London, Taipei, Tokyo, Sydney, and Auckland. The analog clock, digital time, date, weekday, and UTC offset all update to the selected zone.
Choose an analog clock, a large digital clock, or both displays together. Single-display modes use the full available area, and your choice stays active when entering full screen.
The full-screen control works on phones and desktops, centering and enlarging the clock for personal displays, projectors, classrooms, and meeting rooms. Browsers without the native Fullscreen API automatically use a full-viewport fallback. The page does not store time-zone activity.
Common questions and answers about this topic.
When the page loads, the clock attempts to sync with server time and compensate for network latency. After a successful sample it updates every second with the measured offset; if the sync is unavailable, it continues using your device time.
Yes. Use the time zone selector above to switch to UTC, Tokyo, New York, London and other common zones. The clock face, digital time and date all update to that zone.
No. Apart from a single request to the server on load to sync the current time, all display and time-zone conversion happens inside your browser. No usage data is stored or uploaded.
Yes. The full-screen button beside the time-zone selector works on phones and desktops, centering and enlarging both clock displays. Press the exit button or Esc to leave; browsers without native fullscreen automatically use a full-viewport fallback.