Closing a laptop lid can leave every open window ready for a quick return, but that does not mean the computer is fully off. Depending on its power mode, the machine may keep the active session in memory, save it to storage, or use a platform-specific low-power state that behaves differently from older forms of sleep.
Sleep and hibernate both preserve an operating-system session, yet they store that state in different places. That distinction affects power use, resume time, resistance to power loss, and the amount of storage involved.
Sleep keeps the active state available in memory
A running computer holds active program data and operating-system state in RAM. Conventional sleep reduces power to much of the system while preserving the information needed to resume the session in memory.
RAM is volatile storage: it needs power to retain its contents. A sleeping computer therefore cannot behave exactly like a fully powered-off machine. The amount of energy used depends on the hardware and the sleep design, but maintaining a resumable state in memory requires some source of power.
This arrangement favors a quick return. The system does not need to reconstruct a fresh user session or read an entire saved memory image from persistent storage. It restores hardware operation and continues from the retained state.
On systems that use the ACPI S3 state, system memory remains powered while processor, cache, and chipset context is not retained in the same form. Firmware and the operating system cooperate to restore the machine to its working state after a wake event.
Not every current computer exposes S3. Some platforms use a newer low-power idle design while remaining in the ACPI S0 working state. Such systems can still present a familiar Sleep command to the user, even though the underlying power behavior differs from classic S3 sleep.
Hibernate moves the resumable state to persistent storage
Hibernate takes a different approach. Before the machine enters the ACPI S4 state, the operating system saves the state needed for resumption to persistent storage. Hardware can then power down far more completely because RAM does not need to retain the live session.
When the computer starts again, the operating system restores the saved state instead of beginning a normal fresh session. Open applications and windows can return much as they were before hibernation.
Persistent storage is the key distinction. If external power is removed and a removable battery is disconnected while a conventional sleeping system depends on RAM, the retained memory state can be lost. A correctly saved hibernation image remains on storage without continuous power, so the previous session can still be restored later.
Saving and restoring that image also means hibernation generally involves more storage I/O than sleep. Resume latency depends on the operating system, storage device, memory configuration, firmware, and other platform details. It should not be treated as a fixed number across computers.
The visible menu can hide different platform behavior
Names in a power menu describe user-facing actions, not every detail of the hardware state underneath them.
The ACPI specification defines system states ranging from S0, the working state, through sleeping states and S5 soft off. Traditional S3 sleep and S4 hibernation are distinct states, but current operating systems and hardware can implement other power-management patterns around those standards.
A computer with low-power idle support can remain logically in S0 while entering progressively lower-power conditions. The processor may stop ordinary work for periods, devices can enter low-power states, and selected activity may still occur. This differs from S3, where the system is in a defined sleeping state and normal code execution is not taking place.
As a result, two laptops showing the same Sleep label can differ in background behavior, wake sources, network activity, and battery drain. Those differences do not mean the word on the menu is meaningless; they mean the menu is an abstraction over platform-specific power management.
Power loss separates sleep from hibernate most clearly
The practical boundary appears when continuous power cannot be assumed.
With a session retained only in volatile memory, total power loss removes the information that made a direct resume possible. The next start then requires a normal boot, subject to whatever recovery behavior the operating system provides for applications and documents.
A hibernated session does not depend on RAM remaining powered. Its saved image is on persistent storage. ACPI S4 is designed around this model: hardware context is not retained in active memory, while system state needed for resumption is saved before power is reduced.
This makes hibernation suitable for a laptop that may sit unused long enough for its battery to discharge. Sleep is often more convenient for short pauses when rapid access matters and enough battery remains available.
Some operating systems also support combinations such as hybrid sleep, where session state is written to storage while the system also enters a sleep state. That design can offer a fast ordinary wake while retaining a stored recovery path if power disappears. Availability and exact behavior depend on the operating system and hardware.
Hibernation needs storage space for saved state
Because hibernation writes session state to persistent storage, the operating system needs a dedicated file or equivalent storage area. Its size and management policy are implementation details rather than a universal fraction that applies to every computer.
This storage use can matter on devices with limited free space. Disabling hibernation on some operating systems can remove or alter the associated file, but it can also affect features that rely on hibernation infrastructure. The exact result is system-dependent, so storage savings should not be considered separately from the power features a device uses.
Sleep does not require a full hibernation image merely to preserve a conventional in-memory session. A system can still use storage for other power-management features, application state, paging, or recovery mechanisms, so the absence of a user-requested hibernate action does not imply that no related storage is used.
Shutdown starts from a different premise
Shutdown is not simply a deeper version of preserving the same session. In the ACPI S5 soft-off state, the operating system does not retain the session context in the manner used for S4 hibernation. A later start performs a boot rather than restoring the saved S4 image.
Operating systems can add startup optimizations that make the boundary less obvious. Some shutdown implementations may preserve selected system state to speed a later start without restoring the complete user session as hibernation does. Application-level session restoration can also reopen windows after a boot. Neither behavior turns an ordinary shutdown into the same state as hibernation.
For practical use, the most useful distinction is the location of the resumable session. Sleep typically relies on powered memory or a low-power platform state. Hibernate commits resumable state to persistent storage. Shutdown ends the operating-system session and expects a subsequent boot.
That distinction matters more than the appearance of the power menu. If a computer needs to resume quickly after a short pause, sleep is usually aligned with that goal. If it may remain unused long enough that continuous power is uncertain, hibernation preserves the session without depending on RAM staying powered.