Locked or asleep? What your Mac's status actually means
A locked Mac is wide awake with your session sealed behind your password. A sleeping Mac has stopped: its processor is suspended and your work is held in memory. From across the room both look the same — a dark screen — and only one of them says anything about whether you are protected. Here is what each state actually is, and what any of them looks like when you are reading it from somewhere else and the reading might be minutes old.
Locked, asleep, display-off: three different things
macOS has three ways of going dark, and most people have one word for all of them. They behave differently, they are controlled by different settings, and they mean different things to someone who has walked away.
Locked: everything is still running, the session is just sealed
When your Mac locks, nothing stops. Downloads finish, backups run, mail arrives, a build keeps compiling. What changes is that your session is sealed: the desktop is replaced by the login screen, and macOS won't hand it back without your password, your fingerprint, or an Apple Watch you've authorised. Locking is about access and nothing else. It saves no meaningful power and interrupts no work.
Asleep: memory holds your work, almost everything else is powered down
Sleep is the opposite trade. The processor is suspended, the display and drives are parked, and the machine drops to a trickle of power that keeps memory alive. Your open windows and unsaved documents are exactly where you left them, because RAM is still being refreshed. Nothing is executing, though. A sleeping Mac isn't working through your queue, and — the part that matters later on this page — it cannot answer a question about itself.
Display off: the screen is dark and nothing else changed
The third dark screen is the least interesting and the most often misread. A display can switch itself off on its own timer while the Mac stays fully awake and fully unlocked. Anyone who taps the trackpad gets your desktop straight back, no password involved. If you have ever watched a Mac's screen go black as you left the room and taken that as a sign it was safe, this is the case where it wasn't.
Why they come apart in practice
These three drift apart because separate timers drive them. When the display switches off, when the system sleeps, and whether waking asks for a password are three different settings, and their default values don't line up. That's why a Mac can be asleep and unlocked, awake and locked, or dark and neither of those.
Closing a MacBook's lid is the case people ask about most, because it feels decisive — you shut the thing. It sleeps the Mac. Whether it also locks it comes down to that third setting, which is a question with its own answer: see whether closing the lid locked it.
Why asleep and locked need to be told apart from a distance
Standing at the machine, the distinction is academic. You press a key and find out in a second. It starts to matter the moment you can't do that: you're on the train, the Mac mini is at home, the MacBook is on a desk in an open-plan office and you left in a hurry.
Then the two states answer different questions. Locked tells you the session is sealed — someone can wake the machine and get a login prompt. Asleep tells you the machine has stopped, which usually implies the session is sealed too, but only if that password setting was configured to make it so. And Unlocked, on a Mac you are not sitting at, is the reading you actually want to know about, because it means the desktop is open to whoever walks past.
This is the gap Lock Status is built for. A free menu-bar helper on the Mac notices each lock, unlock, and sleep and writes it to your own private iCloud; your iPhone reads it back from there. The overview lives on the page for the app that reports it.
How Lock Status labels each state
Unlocked, Locked, Asleep
Three labels, and no fourth. You won't see "Offline", and that omission is deliberate. When the app stops hearing from a Mac, what it knows is that it stopped hearing — not why. The machine might be shut down, off Wi-Fi, in a bag, or simply slow to sync. Printing "Offline" would name a cause nobody has established.
Every reading carries when we last heard it
The helper checks in with a timestamp, and that timestamp travels with the status. So a reading is never just a word. It's a word and an age: "Unlocked · now", "Locked · 3m ago", "Asleep · 1h ago". The age is not decoration and it never gets trimmed to make a layout fit, including in the widgets, where space is tightest.
After three minutes a reading stops claiming to be current
Three minutes — 180 seconds — is the line. Inside it, a reading counts as live. Past it, three things happen at once, and none of them is hiding the reading from you: the label stays exactly what it was, the colour turns amber, and the age keeps counting up.
"Locked · 12m ago" in amber is the app saying: twelve minutes ago this Mac was locked, and I have not heard from it since. That is less satisfying than a confident green "Locked", and it is the only version of it that's true. Falling back to older data is fine. Falling back silently, so that a twelve-minute-old reading renders identically to a two-second-old one, is the thing this app will not do.
Why an asleep Mac is the one state we still call current
One state breaks that rule, on purpose. A Mac announces that it is going to sleep, and then — because its processor is suspended — it physically cannot check in again. Waiting for a heartbeat from a sleeping Mac is waiting for something that can't arrive.
So "Asleep" is the single label that stays confident as it ages. "Asleep · 1h ago" isn't hedged, because the silence is the expected consequence of the last thing the Mac told us. It's one carve-out, it exists for a mechanical reason, and it's the only one on this list.
"No contact since 14:32" is an answer, not an error
When there's been no word for long enough that a relative age stops being useful, the app gives you the wall-clock time instead. A blank screen, a spinner that never resolves, or a plausible-looking guess would all be worse than that sentence, because all three leave you thinking you know something you don't. "No contact since 14:32" is genuinely usable: whatever happened to that Mac, it happened after 14:32.
Reading the app: three examples, three honest answers
- "Unlocked · now", in green. The Mac checked in seconds ago and a session is open on it. If you are not the person sitting at it, this is the reading worth doing something about.
- "Locked · 12m ago", in amber. Twelve minutes ago it was locked. Since then, nothing. The likeliest explanation is that it slept and the announcement didn't reach iCloud before the machine went quiet — but it could also be shut down, or off the network. The app won't pick between those for you, because it doesn't know either.
- "Asleep · 1h ago", not hedged. It said it was going to sleep an hour ago, and a sleeping Mac has nothing further to add.
All three are answers to "what is happening now", however old the evidence is. If your question is retrospective instead — who was at this Mac while I was out, and when — that's a different page: you can look back at when it was last unlocked.
Common questions
Does a sleeping Mac lock itself?
Not on its own. Sleeping and locking are separate events, and whether waking the Mac asks for your password is decided by a separate setting. A Mac can be asleep and still unlocked, so the setting that decides it is worth checking once on each machine you care about.
Is a locked Mac still using power and network?
Yes. Locking seals your session; it doesn't stop the machine. A locked Mac keeps running — downloads finish, backups run, mail arrives — and it draws roughly the power it was drawing before you locked it. This is also why a locked Mac keeps checking in, and a sleeping one stops.
Does "Asleep" mean my Mac is shut down?
No. Asleep means suspended with your session held in memory, and it wakes back to where you left it. A Mac that has actually been shut down can't report anything, so you won't see a label for that either. What you'll see is the last state the app did hear, with the time it heard it.
Why does my Mac's status say "12m ago" instead of "now"?
Because 12m ago is when that Mac last checked in, and nothing has arrived since. The app could round that up to "now" and the screen would look better; it would also be inventing twelve minutes it knows nothing about. So the reading keeps its label, turns amber, and shows its age.