Auto-Sync: NTP and Mobile Network Time
The quartz crystal inside your device drifts a few seconds each day. Left alone, your clock would be wrong within a week.
To fix that, your operating system connects to a network time protocol server. Your device sends a query to an NTP server, typically run by your operating system vendor, your internet provider, or a public pool like NIST in the United States or NPL in the United Kingdom. The server replies with the exact UTC time. Your computer adjusts its own clock to match, usually in small gradual steps called slewing so you do not see the jump. The whole exchange takes milliseconds.
Mobile phones sync to their cellular network's time signal. The tower broadcasts the current time, and your phone sets its internal clock to match.
Most modern operating systems check the time every few hours to once per day. If you see your clock jump by a second or two, that is the sync happening.
Why Does My Computer Clock Change by One Hour?
Daylight saving time is not a single global rule. Each jurisdiction sets its own start and end dates. Europe switches on the last Sunday of March and off the last Sunday of October. North America switches on the second Sunday of March and the first Sunday of November. Russia has used permanent DST since 2014. Turkey has stayed on permanent UTC+3 since 2016.
Your operating system does not guess these dates. It ships with a copy of the IANA time zone database, which contains the full history of DST rules for every region. The IANA tz database is updated multiple times per year as governments change their rules. Your device downloads these updates through your regular system updates.
When the DST transition date arrives, your OS knows exactly when to spring forward or fall back. You do not see the change happen in real time. You wake up to a clock that is an hour ahead or behind.
How Does My Computer Know the Time Zone When I Travel?
Cross a time zone boundary and your phone or laptop detects the new location. On a phone, the cellular network or GPS provides the time zone. On a laptop, the operating system uses your IP address or your Wi-Fi network's location. You can also pick your zone from a map.
Once it knows your zone, your device loads the correct IANA time zone identifier from its database, something like America/New_York or Europe/Paris. That identifier tells the OS the region's UTC offset, its DST rules, and its history of past changes. Your clock adjusts to show the correct local time.
The key detail: changing your computer clock to a different time does not change your time zone. It changes the instant. If you manually set the clock to 3:00 PM but your system still thinks you are in America/New_York, the clock stays at 3:00 PM. Everything that depends on the zone (calendar events, file timestamps, scheduled jobs) will be wrong.
When Auto-Sync Goes Wrong: Common Issues
Three things break automatic time sync.
Wrong time zone setting. If your system thinks you are in Europe/London when you are in America/New_York, your clock will show the wrong local time even though the underlying UTC time is correct. Fix this in your OS time settings. On Windows, check Date & Time settings and turn off "Set time zone automatically" if it is using the wrong one. On macOS, open Date & Time preferences and confirm your region.
NTP server unreachable. If your computer cannot reach its NTP server because of a firewall, a network outage, or a misconfigured DNS, the clock will drift. Switch to a different NTP server. Public servers like time.nist.gov or pool.ntp.org are reliable alternatives.
A dead CMOS battery. On desktop computers, a small battery inside the motherboard keeps the clock running when the computer is off. When that battery dies, the clock resets to a default date, often January 1, 1970, every time you boot. Replace the battery. The clock will then sync again on the first NTP query.
How to Turn Auto-Sync On or Off
On Windows, go to Settings > Time & Language > Date & Time. Toggle "Set time automatically" for NTP sync. Toggle "Set time zone automatically" for zone detection.
On macOS, open System Preferences > Date & Time. Check "Set time zone automatically using location" and "Synchronize with network time servers."
On Linux, the service is usually called systemd-timesyncd or ntpd. Check its status with timedatectl. Toggle it with timedatectl set-ntp true or false.
On Android, go to Settings > System > Date & Time. Toggle "Automatic date & time" and "Automatic time zone."
On iOS, go to Settings > General > Date & Time. Toggle "Set Automatically."
Why Manually Setting the Time Can Cause Problems
Manual time setting creates two problems.
First, you set the clock to the wrong instant. If you are off by even a few seconds, any process that depends on accurate time (certificate validation, file timestamps, scheduled backups) will fail or produce confusing results.
Second, you set the clock but not the zone. Your browser reads the OS clock to get the current instant. Your browser then reads the OS time zone setting to format that instant as local time. If the clock says 3:00 PM but the zone says America/New_York, you see 3:00 PM Eastern time. If you manually moved the clock to 3:00 PM but you are actually in Los Angeles, your browser still shows 3:00 PM and labels it Eastern time. Everything is wrong.
Let the OS handle both the time and the zone. If you need to override, change the zone, not the clock.