Mac Clock Showing the Wrong Time? How to Fix It

A Mac clock that's off by a few minutes has lost sync with its time server; one that's off by whole hours has the wrong time zone. Both fixes live in System Settings → General → Date & Time — and there's a one-line Terminal command for the stubborn cases.

Off by minutes: resync automatic time

1. Open System Settings → General → Date & Time.
2. Turn on Set time and date automatically. macOS syncs with Apple's time server (time.apple.com, shown in the field beside the toggle).
3. Already on but the clock is still wrong? Toggle it off, then on again — that forces a fresh sync. You'll need to authenticate as an admin.

A healthy Mac stays within a fraction of a second this way. Manual time-setting is the alternative when the toggle is off, but drift always returns — the real fix is making automatic sync work.

Off by hours: fix the time zone

Whole-hour errors (or the infamous "30 minutes off" in half-hour zones like India) are time-zone problems:

1. In the same Date & Time pane, check Set time zone automatically using your current location.
2. For automatic mode to work, Location Services must be on: System Settings → Privacy & Security → Location Services, then scroll to System Services → Details… and make sure Setting time zone is enabled.
3. If you'd rather not use location, turn automatic time zone off and set the Closest city field manually.

A Mac that "shows the wrong time after flying" is nearly always this: automatic time zone off (or blocked from Location Services), still living in the departure city.

Force a sync from Terminal

When you want the clock corrected now — after a long shutdown, a drained battery, or a VM pause:

# Query Apple's time server and step the clock to match
sudo sntp -sS time.apple.com

# Check whether network time is enabled
sudo systemsetup -getusingnetworktime

These don't change any settings — sntp just corrects the clock once, so there's nothing to undo. If getusingnetworktime says Off, turn it on with sudo systemsetup -setusingnetworktime on (undo: … off).

Locked-down networks and other stubborn cases

• Corporate, school, and hotel networks sometimes block NTP (UDP port 123). Symptom: time drifts only on that network, syncs fine on your phone's hotspot. Ask IT for the internal time server and point macOS at it — replace the server in the Date & Time pane, or run sudo systemsetup -setnetworktimeserver ntp.yourcompany.com (undo by setting it back to time.apple.com).
• Wrong by exactly the same amount after every sleep — check for battery/clock trouble on very old Intel Macs, and for VPN clients that route or block NTP.
• Date reset to 1970 or 2020 after a fully drained battery — connect to Wi-Fi and give automatic time a minute; the clock steps forward as soon as sync succeeds.

Right clock, wrong time in one app

If the menu bar clock is correct but times look wrong somewhere specific, stop debugging the system clock — that app has its own idea of the time zone. Browsers inherit the system zone but websites often render times in their chosen zone (or guess from a VPN exit point, which is why times shift when the VPN connects). Calendar deserves special mention: events store an absolute moment, so after a zone change they display shifted — correct, but surprising; the fix for cross-zone planning is Calendar → Settings → Advanced → Turn on time zone support. And in Terminal, a leftover TZ environment variable in your shell profile overrides everything for command-line tools only — echo $TZ should normally print nothing.