The best default is to save your work, lock the screen, and shut the machine down at the end of the day, especially on a desktop that runs on wall power. Choose sleep instead when you need fast resumption, background updates, or remote access overnight. Hibernate for laptops that may run out of battery. Always lock before you walk away, and never rely on sleep alone for security.
The reasoning behind that short answer is more interesting than the answer itself. Sleep, hibernate, shutdown, and lock are not just conveniences. They place your machine in physically different states, with different power draws, different security exposures, and different failure modes. Understanding how each state works explains when the default should change.
The Four End-of-Day States and What They Actually Do
Sleep, in the S3 state on most desktops, cuts power to the processor, drives, and most peripherals while keeping a small current flowing to the memory modules. That current refreshes the RAM thousands of times per second, because dynamic memory loses its contents without constant electrical refresh. Resuming takes a second or two because the operating system and open programs were never unloaded. The cost is that the memory stays energized, which leaves data readable in principle to anyone who can physically access the modules.
Modern Standby, sometimes labeled S0 low-power idle, behaves differently on many recent laptops. The machine stays partially awake, so it can download mail, sync files, and respond to network wake commands. It resumes almost instantly, but its idle power draw is higher than classic S3 sleep, and some machines wake unexpectedly or run warm inside a bag.
Hibernate writes the entire contents of memory to a file on disk, then powers the machine fully off. Nothing stays energized. The trade-off is time: resuming means reading that file back into memory, which takes longer than sleep on machines with slow storage. The advantage is that hibernation survives a battery running flat, because the session is already on disk.
Shutdown closes programs, flushes caches, writes pending data, and powers everything down. It gives the cleanest slate, installs some updates, and clears transient faults. It is also the slowest to resume and loses whatever was open unless you saved it.
Locking the screen is not a power state at all. It is a security action that leaves the machine running exactly as it was while requiring authentication to continue. Locking deserves to be treated as mandatory regardless of which power state you choose.
What It Costs Overnight in Power and Heat
The differences are small per night but compound across a year. A typical desktop in sleep draws somewhere around 1 to 5 watts, and modern low-power desktops can sit near the bottom of that range. Over a night of 10 hours that is perhaps 10 to 50 watt-hours, and across a year roughly 4 to 18 kilowatt-hours. At an electricity price of about USD 0.17 per kilowatt-hour, that works out to roughly USD 1 to USD 3 per year.
A desktop left fully awake but idle draws far more, commonly 30 to 60 watts or higher depending on the processor and graphics card. Over the same 10-hour night that is 300 to 600 watt-hours, or roughly 110 to 220 kilowatt-hours a year. At the same price that is about USD 18 to USD 37 annually, before any monitor draw. Shutdown and hibernate draw effectively nothing overnight.
The heat matters as much as the bill. A machine that sleeps in a closed drawer or under a blanket can trap warmth, and wake events can push it into a warmer state than expected. That is one reason the modern sleep states, which sometimes stay partly awake, are best on a hard surface with ventilation.
[Sleep versus shutdown power estimates around 1-5 W and 30-60 W idle are commonly cited industry ranges; confirm with your device's published specifications if precise figures matter.]
The Security Edge Cases That Change the Answer
Sleep is the riskiest state when physical access is possible. A sleeping machine holds decrypted data in live memory. Someone with brief access can often wake it, and on some systems certain features can be triggered without a full login depending on configuration. Full-disk encryption protects a powered-off disk, but it does not protect memory that is still being refreshed. Hibernation and shutdown write data to encrypted storage and power down, so the encryption keys are no longer resident in active memory.
The counterintuitive detail is that a locked screen is not the same as a secure state. Locking blocks casual use, but the machine behind the lock is still running, still networked, and still holding memory contents. A lock screen left overnight on an unattended machine in a shared space is weaker than a hibernated or shut-down machine, even though both look locked. Security people treat shutdown as the only state that reliably clears memory and network exposure.
Remote access is the other edge case. If you need to reach the machine from home, or run overnight backups and updates, an outright shutdown breaks that. Here the professional answer is to keep it on but tighten it: a locked screen, a sleep state that supports network wake, and firewall rules that close everything you do not need.
Leave a laptop asleep in a bag for hours without a lock: risk of heat and accidental wake. Rely on a lock screen alone overnight on a shared or public machine: memory and network stay live. Trust sleep for long-term storage: an unexpected power loss wipes the session. Use hibernate on a machine with very little free disk: the hibernation file needs space roughly the size of installed memory. Shut down during a critical background update or file sync: possible corruption or lost work.
Those are the situations where the default advice should be overridden.
Misconceptions Worth Retiring
The most common misconception is that shutting down your computer every night wears out the hardware. Modern solid-state drives and processors are rated for far more write cycles and power cycles than typical daily use delivers. Daily shutdowns are not a meaningful lifespan threat on current consumer hardware.
Another is that sleep saves nothing compared with leaving the machine on. Sleep cuts processor and drive draw dramatically, and the difference between sleep and full idle is real and measurable, even if the nightly savings are small.
A third is that hibernate and sleep are interchangeable. They are not. Sleep keeps memory energized and resumes fast; hibernate powers down fully and resumes slower. A power loss during sleep loses the session, while hibernate survives it.
A fourth is that a screensaver or a lock screen is enough. Neither stops the machine from downloading, networking, or holding decrypted data. They are visual and access controls, not power or memory controls.
Finally, people assume the answer is the same for every machine. A desktop on wall power, a laptop that travels, and a shared workstation have different constraints. The best choice depends on which constraint dominates: speed, security, battery, or background work.
The Comparison: Which State Fits Which Situation
| State | What stays powered | Typical idle draw | Resume speed | Security posture | Best for |
|---|---|---|---|---|---|
| Lock only | Everything | Full idle | Instant | Weak: memory and network live | Short step away, same room |
| Sleep (S3) | Memory refresh | Low, roughly 1 to 5 W | Seconds | Moderate: memory live, disk encrypted | Overnight when remote access needed |
| Modern Standby | Partly awake | Higher than S3 | Near instant | Weaker: network and wakes active | Laptops needing background sync |
| Hibernate | Nothing | Effectively zero | Tens of seconds | Strong: memory on encrypted disk | Laptops that may lose battery |
| Shutdown | Nothing | Effectively zero | Slowest boot | Strongest: clean slate | Default end-of-day on desktops |
The table shows the central tension. The faster the resume, the more you leave live. The more you leave live, the more power and exposure you accept. Shutdown sits at the secure, slow end; sleep and modern standby sit at the fast, exposed end; hibernate sits in between with a disk-based session.
A Timeline of What Happens Overnight
| Time after leaving | Sleep (S3) | Modern Standby | Hibernate | Shutdown |
|---|---|---|---|---|
| First minutes | Memory refreshed, network dropping | Still syncing, wakes possible | Writing memory to disk | Caches flushing, drives parking |
| First hour | Low draw, session intact | Higher draw, background tasks | Fully off | Fully off |
| Through the night | Steady low draw | Steady higher draw, occasional wakes | Fully off | Fully off |
| If power is lost | Session lost | Session lost | Session recovered from disk | Machine was already off |
| Morning resume | Seconds, session restored | Near instant | Tens of seconds | Full boot |
| If left for days | Power wasted, exposure persists | More power, more wakes | Minimal drain | None |
The timeline makes the failure modes concrete. Sleep and modern standby waste power and keep exposure for as long as they last. Hibernate and shutdown do not care how long they sit there. Only hibernate preserves the session across a power cut.
Practical Steps and Thresholds
The practical answer is a short routine with clear thresholds. Use these steps as a checklist.
Save and close work, then lock the screen before anything else. Locking is non-negotiable whether you stay on or power down. If the machine lives on wall power and you do not need it overnight, shut it down. This is the default for desktops. If you need fast resume or overnight remote access, use sleep, but keep the screen locked and close unnecessary network services. If the machine is a laptop that may run out of battery, hibernate. Make sure the hibernation file has room roughly equal to installed memory. If the machine will sit unattended for more than a day, shut it down or hibernate. Sleep and modern standby are for short gaps, not long storage. Watch for heat in bags and drawers. If a sleeping laptop feels warm, switch to hibernate.
A simple threshold: if the gap is under a few hours and you are nearby, lock and sleep is fine. If the gap is overnight and the machine is on wall power, shut down. If the gap is overnight on battery, hibernate. If the machine is shared or in a public space, shut down or hibernate regardless.
Those thresholds reconcile the competing advice you will see elsewhere. Advice to sleep is usually about convenience and background tasks. Advice to shut down is usually about security and power. Both are right within their constraints. The routine above picks the constraint that dominates for your situation.
Limitations and What This Advice Cannot Cover
This guidance describes stable mechanisms and general power behavior. Actual idle draw, resume times, and wake behavior vary widely by processor, operating system version, firmware, and configuration. The power figures here are typical ranges, not guarantees for your specific device.
Security outcomes also depend on configuration you may not control. Full-disk encryption, firmware passwords, and wake-on-LAN settings change the exposure of a sleeping machine. If your organization sets policy, follow it; the default advice here may conflict with managed-device requirements.
Finally, no single routine fits every machine. A workstation running long compute jobs, a laptop that must stay reachable, and a shared kiosk each need different handling. Match the state to the dominant constraint, and lock the screen every time.
This article is general educational information about computer power and security states, not a security audit, legal opinion, or device-specific configuration guide. It does not promise any particular power savings or security outcome. For organizational policy, managed devices, or sensitive data, consult a qualified IT or security professional.