ESP32-S3 Low-Power Modes Summary
0:36
Searching for documentation.
Running multiple web searches.
Found 10 results.
Found 9 results.
I didn’t find relevant ESP32-S3 low-power documentation in the uploaded-file index I could access; the search results were unrelated skills/reference files rather than Espressif docs . Using Espressif’s documentation, the main ESP32-S3 low-power options are:
Available sleep configurations
| Mode | What stays active | Typical use |
|---|---|---|
| Modem-sleep | CPU can keep running; radio/modem sleeps when idle | Connected Wi-Fi/BLE applications that need lower average power |
| Light-sleep | CPU paused, clocks gated, most RAM retained, fast wake | Duty-cycled sensing, periodic wakeups, moderate latency |
| Deep-sleep | CPUs off, most digital domain off, RTC domain retained as needed | Battery operation with long sleep intervals |
| Hibernation | Minimum RTC retention, most RTC resources off | Lowest possible standby power when only minimal wake logic is needed |
Espressif’s ESP32-S3 docs present two major sleep modes:
- Light-sleep
- Deep-sleep
And in the broader low-power guide they also discuss:
- Modem-sleep
- DFS (dynamic frequency scaling, not a sleep state but a power-saving run mode)
In practice, people often include hibernation as the deepest configuration under the deep-sleep family.
Key differences
Modem-sleep
- Best when wireless connectivity must be preserved intermittently.
- Mainly powers down Wi-Fi/BLE modem blocks when not needed.
- Lowest disruption to software behavior.
- Good balance between power savings and wake latency.
- RAM/context retention is much better than deep-sleep.
- Wake sources are broader and wake is relatively quick.
- Much lower power than light-sleep.
- Main CPUs restart on wake, so firmware usually boots again and checks the wake cause.
- RTC memory / RTC peripherals can be selectively kept for wake logic and retained state.
- Deepest standby option.
- Even more RTC resources are shut down than normal deep-sleep.
- Best for ultra-long battery life where wake latency and context retention matter less than minimum current.
Practical selection guide
| If you need... | Use |
|---|---|
| Wi-Fi/BLE still managed efficiently while active | Modem-sleep |
| Fast wake with RAM preserved | Light-sleep |
| Very low average current with periodic wake | Deep-sleep |
| Absolute minimum standby current | Hibernation |
- Sleep Modes: https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/api-reference/system/sleep_modes.html
- Low Power Modes overview: https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/api-guides/low-power-mode/index.html
- Wi-Fi low-power behavior: https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/api-guides/low-power-mode/low-power-mode-wifi.html
If you want, I can also turn this into a design-oriented recommendation for your use case, like:
- battery sensor node
- BLE peripheral
- Wi-Fi data logger
- always-on mains-powered device
Recommend a sleep mode
Show wakeup sources
Estimate battery life
22 days
To get started, talk to Flux or create a New Document.
Welcome 👋
Flux helps you build PCBs faster with an AI teammate!
Create your account to collaborate, stay updated, fork your own version, and get instant answers from our AI agent.