How to Sync Computer Time and Fix Clock Drift
Synchronize a computer clock safely, diagnose failed time updates, and understand what automatic internet time actually changes.
To sync computer time, enable automatic date and time, confirm the correct time zone, and let the operating system contact its configured internet time source. If the clock still differs, the size and pattern of the error usually reveal what to check next.
Before You Press Sync
Compare the computer with a trusted reference and note the difference. Do not rely on another device that may share the same faulty network or settings. NIST provides time.gov as a public display of its time estimate, although network delay means a web display is not a laboratory calibration.
Check the selected time zone first. A machine that is exactly five hours wrong may already have the correct UTC instant but be displaying it with the wrong offset. Synchronization will not fix a bad zone selection because it solves a different problem.
What Automatic Time Does
NIST describes NTP as the most prevalent protocol used to set computer clocks. An NTP client exchanges timestamps with a server, estimates network delay and clock offset, and adjusts the local clock. Full NTP clients can compare several sources and reject responses that look inconsistent.
Small differences are often corrected gradually. This is called slewing. The clock runs slightly faster or slower until it converges without moving backward. A large startup error may be stepped immediately.
A Safe Sync Checklist
- Select the correct region or named time zone
- Enable automatic date and time
- Enable automatic time-zone detection only if location access is appropriate
- Connect to a normal network without a captive portal
- Use the operating system's sync-now control
- Wait briefly, then compare again
- Restart the time service or computer if a pending setting has not applied
The names of these controls differ between Windows, macOS, and Linux, but the order is the same: zone, source, network, sync, verify.
When Synchronization Fails
No change at all can indicate blocked NTP traffic, a disabled service, a policy managed by an organization, or a server name that cannot be resolved. A corporate device may be expected to synchronize with a domain controller rather than a public server.
A one-hour error around spring or autumn points to daylight-saving rules. Update the operating system's time-zone data and confirm the correct city rather than selecting a fixed UTC offset.
If the clock becomes wrong only after the computer has been fully powered off, synchronization may be working perfectly once online. The underlying problem could be a weak RTC battery.
Avoid Risky Workarounds
Do not backdate a computer to bypass an expired certificate, software license, or security check. The change can corrupt log order and may expose the machine to additional risk. Fix the certificate, account, or software problem directly.
Do not add a manual offset to "help" NTP. A time source supplies an instant; the time zone supplies the display. Mixing the two creates double corrections.
Verify the Result
After synchronization, confirm the full date, seconds, time zone, and daylight-saving status. Then check again after a restart. A stable result indicates that both the startup clock and network correction path are working. If the difference grows at a steady rate, record how many seconds it gains or loses per day. That measurement is more useful for troubleshooting than saying the clock is "sometimes wrong."
Offset, Delay, and Jitter
Three measurements help explain synchronization quality. Offset is the estimated difference between the local clock and its source. Delay is the round-trip travel time of the request. Jitter describes how much successive measurements vary.
A 5 ms network delay does not automatically mean a 5 ms clock error. NTP estimates the outward and return paths, but internet routes are not always symmetric. Wi-Fi congestion, VPNs, and mobile links can make measurements vary. A client that samples several sources over time has more evidence than a one-click web clock comparison.
For a home computer, staying within a fraction of a second is normally more than enough. Trading systems, telecom networks, laboratories, and distributed databases may require specialized authenticated sources, monitoring, or hardware timestamping. Use requirements that match the job instead of treating the number of displayed decimal places as proof of accuracy.