Why the clock on your Mac shows the wrong time and how to fix it
A Mac showing the wrong time in the menu bar is not one problem. It is at least three, and they look identical from the outside. The clock can be reporting a time that is genuinely off by minutes, which is a synchronisation fault. It can be reporting a time that is off by whole hours, which is almost always the time zone. Or it can be reporting the correct time in a format that reads as wrong, which is a region setting and not a fault at all.
Working through them in the wrong order wastes an afternoon, because the fix for each lives in a different pane. Start by deciding which of the three is actually happening.
Tell the three apart before touching anything
Compare the menu bar clock against a phone standing next to it, and look at the size of the gap.
A gap of seconds or minutes means the clock is drifting. The machine is either not asking a time server, or asking one it cannot reach. That is the synchronisation case.
A gap of an exact number of hours, with the minutes matching, means the time itself is fine and the time zone is wrong. Half hour and forty five minute zones exist too, so a gap that is not a whole number of hours does not rule this out.
No gap at all, but the display looks wrong, means the format is the problem. A clock reading 15:00 when 3:00 PM was expected, or a date written as 09/02 when the second of September was meant, is a region setting doing exactly what it was told.
| Symptom | Likely cause | Where the fix lives |
|---|---|---|
| Off by seconds or minutes | No working time server | General, Date and Time |
| Off by whole hours | Time zone | General, Date and Time |
| Correct time, unfamiliar format | Region or 24 hour setting | General, Language and Region |
| Correct time, clock looks faded | A Focus is running | Menu Bar settings |
| Wrong again after every shutdown | Hardware clock | Not a settings problem |
The automatic setting, and the button beside it
Almost every synchronisation fault ends here. Open System Settings, click General in the sidebar, then click Date and Time, scrolling down if needed.
The first row is Set time and date automatically. With it on, the Mac keeps itself correct from a network time server, and Apple's reason for caring is worth repeating: the time stamps on emails, messages and files all depend on it, so a wrong clock quietly corrupts the ordering of everything the machine writes.
Beside that row is a Set button, and this is the part people skip. Clicking it reveals the address of the network time server the Mac is asking. If that field holds a server the machine cannot reach, whether because of a firewall, a captive network or a server that has been retired, the switch can be on and the clock can still drift. The row will look correct while doing nothing.
If the automatic setting refuses to stay on, or the time is needed immediately, turning the switch off makes the date and time editable. Click Set, enter them, and click Set again. That is a stopgap rather than a fix, because a manually set clock drifts from the moment it is entered.
Checking and changing the time server
The address the Mac is using can be read without opening System Settings at all, which is useful when the pane is not saving changes. The file holding it is plain text:
cat /etc/ntp.conf
The output is a single line beginning with the word server, followed by the address. Apple runs regional addresses, so a machine set up in one part of the world will show a different host from one set up elsewhere, and both are legitimate.
The same value is readable and writable through a command line tool:
sudo systemsetup -getnetworktimeserver
sudo systemsetup -getusingnetworktime
Those two answer the two questions the pane answers, and the matching set commands change them. If the pane shows the switch on but the second command disagrees, the pane is not the thing to trust.
To force a single correction rather than waiting, macOS includes a small client for exactly this:
sudo sntp -sS time.apple.com
That asks the named server and sets the clock from the answer. The two flags differ in how the correction is applied: one slews the clock gradually when the gap is small, the other sets it outright when the gap is large. If this command returns an error rather than a time, the problem is the network path to the server, not the Mac, and the next thing to test is whether the network allows time traffic out at all.
The time zone depends on a switch in a different pane
A clock that is wrong by whole hours is a time zone problem, and the setting that controls it has a dependency most people do not expect.
In the Date and Time pane, the row is Set time zone automatically using your current location. Apple attaches a note to it: Location Services has to be turned on for the Mac to work out where it is. That switch is not in this pane. It lives in Privacy and Security settings. With Location Services off, the automatic time zone row can be on and still do nothing, so the zone stays wherever it was last set, which is usually wherever the machine was first switched on.
Setting it by hand is straightforward. Turn the automatic switch off, type a city into the field at the bottom of the pane, and press Return. The pane then shows a Closest city, which is often a larger city nearby rather than the one that was typed. That is normal, and the zone is correct as long as the city shown shares it.
Travel makes this visible. A machine that crossed time zones with Location Services off will keep the old zone, and every calendar event created afterwards will be an hour or more out.
When the time is right and the writing is wrong
Two settings change how the clock reads without changing what it reports.
The 24 hour time switch is in the same Date and Time pane. Apple's description is the clearest way to see what it does: instead of 3:00 PM, show 15:00. Nothing about the underlying time changes.
The date format is somewhere else again, in System Settings under General, then Language and Region. Choosing a Region sets the date, time and number formats to that region's conventions all at once, and Date format can then be set on its own, which is where the choice between day before month and month before day is made. First day of week and calendar type are in the same list.
Neither of these is a fault. They are the most common reason someone concludes the clock is wrong when it is not.
The clock that looks wrong but is working
Two appearances get reported as faults regularly.
A faded or greyed out clock means a Focus is active and the Focus status menu is not being shown in the menu bar. With no icon available to announce the Focus, the system dims the clock instead. The fix is in Menu Bar settings: select Focus in the Menu Bar Controls list and choose Always Show or Show When Active. Show When Active is usually right, because the icon then appears only while a Focus is running.
A date that comes and goes is the Show date setting in Clock Options, which offers When Space Allows, Always and Never. On the When Space Allows setting the date is dropped whenever the menu bar runs short of room, which happens as soon as an app with long menu names comes to the front. Setting it to Always keeps the date, at the cost of width that the status icons were using. If the bar is already tight, that trade is worth thinking about rather than making blindly, and the feature list covers what can be done about a bar that has run out of room.
What a wrong clock breaks besides the clock
Apple gives one reason for keeping the time correct, and it is the mildest of them: the time stamps on emails, messages and files depend on it. That alone is enough to matter, because a mailbox sorted by date becomes unreliable and files saved during the drift sort into the wrong place forever, long after the clock has been fixed.
The louder failures come from anywhere the Mac talks to something else. A secure connection checks a certificate's validity dates against the system clock, so a machine whose clock has slipped far enough starts refusing connections that are perfectly fine, with errors that describe the certificate rather than the time. Sites stop loading, mail accounts stop authenticating, and app updates fail, all with messages that point in the wrong direction.
Shared calendars are the other common casualty. An event created while the time zone was wrong carries the wrong moment, and correcting the zone afterwards does not correct the event, because the event was stored as the time it was given. Anyone the invitation was sent to sees the wrong hour, and the mismatch survives every later fix.
This is the argument for checking the clock first whenever something inexplicable starts failing on a Mac that was fine yesterday. It costs one glance at the menu bar, and it rules out an entire class of problems that otherwise look like network faults, account faults or broken software.
It is also the reason a manually entered time is a stopgap rather than a solution. A hand set clock is correct at the moment it is typed and drifts from then on, so the same failures return later with no obvious trigger.
When it is wrong again after every restart
A clock that is correct while the Mac is running and wrong again after it has been shut down for a while is pointing at hardware rather than settings. The clock that keeps running while the machine is off does not use the same power as the rest of the system, and when that fails the date resets to a default on every cold start.
The tell is the pattern rather than the size of the error. Settings are not involved, so nothing in the panes above will hold. Automatic time will correct the clock a few seconds after the machine reaches the network, which makes the fault look intermittent and easy to dismiss until something depending on the date fails during startup, such as a certificate check on a secure connection.
What to change first
Open General, then Date and Time, click Set beside the automatic row, and read the server address that appears. Then check Location Services in Privacy and Security settings before touching the time zone. Those two account for nearly every case. If what actually bothers you is the crowded strip the clock sits in, Koffret handles that part.
Frequently asked questions
Why is the Mac clock off by exactly one hour?
That is a time zone, not a clock fault. Open System Settings, click General, then Date and Time, and check whether the time zone shown matches where the machine is. If the automatic switch is on and the zone is still wrong, Location Services is probably off in Privacy and Security settings, which stops the Mac working out where it is.
The automatic time switch is on but the clock still drifts. What now?
Click the Set button beside that row and read the network time server address it reveals. A switch that is on means nothing if the server cannot be reached, which happens on networks that block time traffic or when the address points at a retired host. Entering a reachable server and clicking Done restores the correction.
Is there a way to force the clock to correct itself right now?
Yes. macOS includes a small time client that can be run from Terminal, asking a named server and setting the clock from the answer. It reports an error instead of a time when the server cannot be reached, which is a quick way to tell a network problem from a settings problem.
Why did the clock change to a 24 hour format on its own?
Something changed either the 24 hour time switch in Date and Time or the Region setting in Language and Region, since choosing a region applies that region's conventions for time, date and numbers together. Setting the region back, or turning the 24 hour switch off, restores the previous reading.
Why does the menu bar clock look faded?
A Focus is running and its status menu is not shown in the menu bar, so the dimmed clock is standing in for the missing icon. Select Focus in Menu Bar settings and choose Always Show or Show When Active, and the clock returns to full brightness.