[{"data":1,"prerenderedAt":464},["ShallowReactive",2],{"post-esp32-deep-sleep-real-current-draw-en":3,"related-posts-esp32-deep-sleep-real-current-draw-en":422,"related-categories-esp32-deep-sleep-real-current-draw-en":447},{"id":4,"title":5,"author":6,"authorImageUrl":7,"authorUrl":8,"body":9,"categorySlug":382,"categoryText":383,"dateModified":384,"datePublished":384,"description":385,"extension":386,"faqs":387,"image":406,"imageAlt":407,"language":408,"meta":409,"navigation":410,"path":411,"seo":412,"sitemap":413,"stem":414,"summary":415,"tags":416,"__hash__":421},"blog\u002Fblog\u002Fesp32-deep-sleep-real-current-draw.md","ESP32 Deep Sleep Current: Chip vs Dev Board","Mauro Brambilla","\u002Fimages\u002Fauthors\u002Fbruma.jpg","\u002Fabout",{"type":10,"value":11,"toc":372},"minimark",[12,16,32,37,40,46,72,80,84,87,92,127,134,143,148,157,166,170,173,177,185,198,219,223,226,230,246,257,273,277,280,284,287,292,298,301,305,308,314,334,346,358,362,365],[13,14,15],"p",{},"An ESP32 chip draws 5 to 10 µA in deep sleep according to Espressif's datasheets, but a dev board built around it usually draws more: 14 µA on the XIAO ESP32-S3 by Seeed's spec, and milliamps on boards with an AMS1117-type regulator, a power LED and a USB bridge. The board, not the chip, sets your battery life.",[13,17,18,19,26,27,31],{},"This post lines up the datasheet figure for each chip against the figure for the board, explains where the extra current comes from, and then covers the sleep modes, the wake-up sources and the battery-life formula. Everything comes from ",[20,21,25],"a",{"href":22,"rel":23},"https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Fesp-idf\u002Fen\u002Flatest\u002Fesp32s3\u002Fapi-reference\u002Fsystem\u002Fsleep_modes.html",[24],"nofollow","Espressif's datasheets and ESP-IDF documentation",", Seeed's wiki and a published bench test. None of the three ",[20,28,30],{"href":29},"\u002Fblog\u002Fwhat-is-opengizmo","OpenGizmo"," projects uses deep sleep, so I did not measure anything myself and I won't invent numbers.",[33,34,36],"h2",{"id":35},"how-much-current-does-an-esp32-draw-in-deep-sleep","How much current does an ESP32 draw in deep sleep?",[13,38,39],{},"Deep sleep is the mode where the CPU, most of the RAM and the digital peripherals are powered off and only a small always-on part of the chip, the RTC domain, keeps running. Espressif lists the chip's current in that mode in each datasheet, as of November 2026:",[41,42],"blog-table",{":headers":43,":highlightCol":44,":rows":45},"[\"Chip (datasheet version)\",\"Deep sleep (µA)\",\"Light sleep (µA)\",\"What the deep-sleep row includes\"]","1","[[\"ESP32 (v5.3)\",\"10\",\"800\",\"RTC timer and RTC memory on\"],[\"ESP32-S3 (v2.2)\",\"7\",\"240\",\"RTC memory on, RTC peripherals off (8 µA with RTC peripherals on)\"],[\"ESP32-C3 (v2.5)\",\"5\",\"130\",\"RTC timer and RTC memory on\"],[\"ESP32-C6 (v1.6)\",\"7\",\"180 (35)\",\"RTC timer and LP memory on; 35 µA is light sleep with peripherals powered down\"]]",[13,47,48,49,54,55,54,60,65,66,71],{},"The figures come from the low-power tables of the ",[20,50,53],{"href":51,"rel":52},"https:\u002F\u002Fdocumentation.espressif.com\u002Fesp32_datasheet_en.pdf",[24],"ESP32",", ",[20,56,59],{"href":57,"rel":58},"https:\u002F\u002Fdocumentation.espressif.com\u002Fesp32-s3_datasheet_en.pdf",[24],"ESP32-S3",[20,61,64],{"href":62,"rel":63},"https:\u002F\u002Fdocumentation.espressif.com\u002Fesp32-c3_datasheet_en.pdf",[24],"ESP32-C3"," and ",[20,67,70],{"href":68,"rel":69},"https:\u002F\u002Fdocumentation.espressif.com\u002Fesp32-c6_datasheet_en.pdf",[24],"ESP32-C6"," datasheets. Two details matter. The S3 and C3 light-sleep rows assume the Wi-Fi block is powered down and all GPIOs are high-impedance, and the S3 datasheet adds that chips with embedded PSRAM must add its draw, for example 140 µA for 8 MB of 8-line PSRAM at 3.3 V. And the original ESP32 also lists a hibernation mode at 5 µA with only the RTC timer running, which the newer chips do not list.",[13,73,74,75,79],{},"These are typical values for the bare chip. If you are still choosing a chip, ",[20,76,78],{"href":77},"\u002Fblog\u002Fwhich-esp32-chip-should-you-buy","which ESP32 to buy"," compares the families, and the C3's 5 µA looks like the winner on paper. Hold that thought, because the next section breaks it.",[33,81,83],{"id":82},"why-does-a-dev-board-draw-milliamps-instead-of-microamps","Why does a dev board draw milliamps instead of microamps?",[13,85,86],{},"A dev board adds parts that never go to sleep. Compare the datasheet rows with what the boards list themselves:",[41,88],{":headers":89,":highlightCol":90,":rows":91},"[\"Board\",\"Chip datasheet (µA)\",\"Seeed wiki spec (µA)\",\"Qoitech bench at 3.8 V (µA)\"]","0","[[\"XIAO ESP32-S3\",\"7\",\"14\",\"13.4\"],[\"XIAO ESP32-C3\",\"5\",\"44\",\"41.6\"],[\"XIAO ESP32-C6\",\"7\",\"15\",\"16.9\"],[\"XIAO ESP32-S3 Plus\",\"7\",\"33.51\",\"not measured\"]]",[13,93,94,95,54,100,65,105,110,111,116,117,121,122,126],{},"The Seeed numbers come from the wiki pages of the ",[20,96,99],{"href":97,"rel":98},"https:\u002F\u002Fwiki.seeedstudio.com\u002Fxiao_esp32s3_getting_started\u002F",[24],"XIAO ESP32-S3",[20,101,104],{"href":102,"rel":103},"https:\u002F\u002Fwiki.seeedstudio.com\u002FXIAO_ESP32C3_Getting_Started\u002F",[24],"XIAO ESP32-C3",[20,106,109],{"href":107,"rel":108},"https:\u002F\u002Fwiki.seeedstudio.com\u002Fxiao_esp32c6_getting_started\u002F",[24],"XIAO ESP32-C6",", and the bench column is from ",[20,112,115],{"href":113,"rel":114},"https:\u002F\u002Fwww.qoitech.com\u002Fblog\u002Fesp32-s3-c3-c6-sleep-power-consumption\u002F",[24],"Qoitech's August 2026 measurement"," with an Otii Ace Pro on the battery pad, running ESP-IDF 5.5.3. The ",[20,118,120],{"href":119},"\u002Fblog\u002Fxiao-esp32s3-vs-c3-vs-c6","XIAO comparison post"," goes through the three boards in full. Here the point is the gap: the S3 board is about twice its chip, and the C3 board is almost nine times its chip, even though the C3 chip is the lowest on paper. Firmware can make it worse, too: Qoitech found that holding the state of the LED pin, which is not an RTC-capable pin, with ",[123,124,125],"code",{},"gpio_deep_sleep_hold_en()"," pushed the C3 board to 461 µA, and removing the call brought it back to 41.6 µA.",[13,128,129],{},[130,131],"img",{"alt":132,"src":133},"Log-scale bars of deep-sleep current in µA: S3 chip 7, XIAO ESP32-S3 14, XIAO ESP32-C3 44, and an AMS1117 regulator alone 5,000","\u002Fimages\u002Fblog\u002Fesp32-deep-sleep-real-current-draw-chip-vs-board.webp",[13,135,136,137,142],{},"The red bar is the reason cheap dev boards disappoint. The ",[20,138,141],{"href":139,"rel":140},"http:\u002F\u002Fwww.advanced-monolithic.com\u002Fpdf\u002Fds1117.pdf",[24],"AMS1117 datasheet"," lists a quiescent current of 5 mA typical and 11 mA maximum, and a linear regulator burns that whether or not the chip sleeps. Here is where the rest of a typical board's current hides:",[144,145],"blog-list",{":items":146,"variant":147},"[\"Linear regulator: the AMS1117 draws 5 mA typical by itself. A low-quiescent LDO on a battery-first board draws microamps.\",\"Power LED: Espressif's ESP32-S3-DevKitC-1 guide lists a 3.3 V power-on LED that lights whenever USB power is connected. JLCPCB's arithmetic for a 1 kΩ resistor and a 2.0 V LED gives about 1.3 mA.\",\"USB-to-serial bridge: the DevKitC-1 carries one. JLCPCB cites 195 µA in USB suspend and 1.3 mA held in reset for a CP2102N, which I could not check against the Silicon Labs datasheet.\",\"Pull-ups: a 10 kΩ pull-up to 3.3 V on a line held low passes 330 µA (Ohm's law), more than the whole XIAO S3 board.\",\"Flash: ESP-IDF keeps the external flash powered in light sleep, and Qoitech saw the S3 board drop from 2.88 mA to 692 µA with CONFIG_ESP_SLEEP_POWER_DOWN_FLASH enabled, although ESP-IDF's sleep page recommends against that option and points to flash deep power-down instead.\"]","circle",[13,149,150,151,156],{},"The regulator and bridge numbers come from ",[20,152,155],{"href":153,"rel":154},"https:\u002F\u002Fjlcpcb.com\u002Fblog\u002Fesp32-power-consumption-explained",[24],"JLCPCB's power-consumption explainer",", a manufacturer's blog, so treat the CP2102N and LED figures as an illustration of the order of magnitude, and read your own board's schematic. The same article warns that its parts are typical of many boards, not all. Seeed's XIAO boards land far lower, and I did not read their schematics to say why. Qoitech only notes an onboard LDO between the battery input and the chip, which is why it powered the boards at 3.8 V.",[13,158,159,160,165],{},"Where you measure matters too. Espressif's ",[20,161,164],{"href":162,"rel":163},"https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Fesp-idf\u002Fen\u002Fv6.0\u002Fesp32c6\u002Fapi-guides\u002Fcurrent-consumption-measurement-modules.html",[24],"current measurement guide"," measured an ESP32-S3-WROOM-1 module at 8.14 µA in deep sleep with a Joulescope, close to the datasheet's 7 to 8 µA rows, and warns that an ordinary meter's voltage drop can make the module unstable. It recommends an ammeter with low internal resistance and fast range switching. A cheap multimeter in the supply line may read wrong, or reset the board.",[33,167,169],{"id":168},"deep-sleep-light-sleep-and-modem-sleep-what-is-the-difference","Deep sleep, light sleep and modem sleep: what is the difference?",[13,171,172],{},"The S3 datasheet defines four power modes: Active, Modem-sleep, Light-sleep and Deep-sleep. The three sleep modes trade wake-up cost against current:",[41,174],{":headers":175,":highlightCol":90,":rows":176},"[\"Mode\",\"What stays powered\",\"After waking\",\"ESP32-S3 chip (typ.)\"]","[[\"Modem-sleep\",\"CPU on, Wi-Fi clock gated, connection kept alive by switching the radio on periodically\",\"Nothing is lost\",\"27.6 mA at 160 MHz, CPU idle\"],[\"Light-sleep\",\"RAM kept, CPU stopped, Wi-Fi connection can stay alive\",\"Program continues where it stopped\",\"240 µA, Wi-Fi powered down\"],[\"Deep-sleep\",\"Only the RTC domain and RTC memory\",\"Program restarts from the beginning\",\"7 µA with RTC memory only\"]]",[13,178,179,180,184],{},"The Modem-sleep figure is from the S3 datasheet's Table 5-9 with peripheral clocks disabled. Seeed lists 27 mA for the XIAO ESP32-S3 in modem-sleep, 2 mA in light sleep and 14 µA in deep sleep, all at 3.8 V. Qoitech reads the 2 mA as a figure that assumes active Wi-Fi. The ESP-IDF ",[20,181,183],{"href":22,"rel":182},[24],"sleep modes page"," says that after light sleep \"the digital peripherals, RAM, and CPUs resume operation and their internal states are preserved\", while in deep sleep the CPUs, most RAM and the digital peripherals are powered off. Only the RTC controller, the ULP coprocessor and the RTC memories stay on.",[13,186,187,188,193,194,197],{},"Wi-Fi has its own, separate setting. ",[20,189,192],{"href":190,"rel":191},"https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Fesp-idf\u002Fen\u002Flatest\u002Fesp32s3\u002Fapi-guides\u002Fwifi-driver\u002Fwifi-performance-and-power-save.html",[24],"ESP-IDF's Wi-Fi power-save guide"," says the default Modem-sleep mode is ",[123,195,196],{},"WIFI_PS_MIN_MODEM",", where the station wakes every DTIM to receive the beacon, and that received data may be delayed by the same DTIM cycle. Light sleep and deep sleep are different: the datasheet says wireless connections can remain active in light sleep, while after deep sleep the program restarts and your firmware has to bring Wi-Fi up again, which is where the battery goes. The datasheet adds that wireless connection data is stored in RTC memory during deep sleep, but the program itself still restarts from the top.",[13,199,200,201,206,207,210,211,214,215,218],{},"The ",[20,202,205],{"href":203,"rel":204},"https:\u002F\u002Fgithub.com\u002Fopen-gizmo\u002Fgizmo-camera",[24],"Gizmo Camera"," firmware does the opposite on purpose. Its ",[123,208,209],{},"wifi.cpp"," (on the repository's ",[123,212,213],{},"feature"," branch as of this writing) calls ",[123,216,217],{},"WiFi.setSleep(false)",", with a comment saying that with power saving on, a snapshot of a few hundred KB takes several times longer to send. That is a speed choice for a USB-powered camera, not a battery recommendation, and I did not measure the difference.",[33,220,222],{"id":221},"what-can-wake-an-esp32-from-deep-sleep","What can wake an ESP32 from deep sleep?",[13,224,225],{},"Deep sleep only helps if something wakes the chip when it matters. On the ESP32-S3, the ESP-IDF page lists these sources:",[41,227],{":headers":228,":highlightCol":90,":rows":229},"[\"Wake-up source\",\"Function\",\"Good for\",\"Note\"]","[[\"RTC timer\",\"esp_sleep_enable_timer_wakeup()\",\"Periodic readings\",\"Deep and light sleep\"],[\"ext0\",\"esp_sleep_enable_ext0_wakeup()\",\"One button or sensor pin\",\"One RTC GPIO, set the pull yourself\"],[\"ext1\",\"esp_sleep_enable_ext1_wakeup_io()\",\"Several buttons\",\"Any-low or any-high on RTC GPIOs\"],[\"Touch pad\",\"esp_sleep_enable_touchpad_wakeup()\",\"Touch buttons\",\"Touch sensor interrupt\"],[\"ULP coprocessor\",\"esp_sleep_enable_ulp_wakeup()\",\"Slow sensor polling\",\"Runs from RTC SLOW memory\"],[\"GPIO\",\"esp_sleep_enable_gpio_wakeup()\",\"Any pin, light sleep\",\"For deep sleep on the S3 use ext0 or ext1 on RTC GPIOs\"]]",[13,231,232,233,237,238,241,242,245],{},"On the S3, the page lists RTC GPIOs 0 to 21 for ext0 and ext1. On the XIAO ESP32-S3, that covers the pads D0 to D5 and D8 to D10 (GPIO1 to GPIO9), but not the serial pads D6 and D7 (GPIO43 and GPIO44), according to the pad table in the ",[20,234,236],{"href":235},"\u002Fblog\u002Fxiao-esp32s3-pinout-safe-pins","pinout guide",". The page also says the application must set the ext0 pull-up or pull-down itself with ",[123,239,240],{},"rtc_gpio_pullup_en()"," before sleeping, and that after wake-up the pad is an RTC IO until you call ",[123,243,244],{},"rtc_gpio_deinit()",". This sketch shows the shape of it. It is built from those function names and I have not compiled or run it:",[247,248,255],"pre",{"className":249,"code":251,"filename":252,"language":253,"meta":254},[250],"language-cpp","#include \u003Cdriver\u002Frtc_io.h>\n#include \u003Cesp_sleep.h>\n\nRTC_DATA_ATTR int wakeCount = 0; \u002F\u002F survives deep sleep, lost on reset or power loss\n\nvoid setup() {\n    wakeCount++;\n    rtc_gpio_pullup_en(GPIO_NUM_1); \u002F\u002F button on D0, other leg to GND\n    esp_sleep_enable_ext0_wakeup(GPIO_NUM_1, 0); \u002F\u002F wake when the pin goes LOW\n    esp_sleep_enable_timer_wakeup(15ULL * 60 * 1000000); \u002F\u002F or after 15 minutes\n    esp_deep_sleep_start(); \u002F\u002F does not return\n}\n\nvoid loop() {}\n","deep_sleep_sketch.ino","cpp","",[123,256,251],{"__ignoreMap":254},[13,258,259,260,263,264,267,268,272],{},"Since a deep-sleep wake-up restarts the program, everything not in RTC memory is gone: the Wi-Fi connection, the web server, the display buffer. ",[123,261,262],{},"esp_sleep_get_wakeup_cause()"," tells ",[123,265,266],{},"setup()"," what woke it, though it reports only one source if several fire together. Mind the strapping pins when you choose a wake pin, because the level at reset can change the boot mode: the ",[20,269,271],{"href":270},"\u002Fblog\u002Fesp32-strapping-pins-by-chip","strapping pins by chip"," guide lists them.",[33,274,276],{"id":275},"how-do-you-estimate-esp32-battery-life","How do you estimate ESP32 battery life?",[13,278,279],{},"Battery life is the usable capacity divided by the average current, and the average is a weighted mix of awake and asleep:",[144,281],{":items":282,"variant":283},"[\"Average current (mA) = (active mA × active s + sleep mA × sleep s) ÷ cycle s\",\"Battery life (h) = usable capacity (mAh) ÷ average current (mA)\"]","numbered",[13,285,286],{},"Usable capacity is less than the label, because of cutoff voltage, temperature and regulator losses. I use 80 percent as a starting point, which is a rule of thumb of mine, not a datasheet value. As an example, take an 800 mAh usable battery, a wake every 15 minutes, 5 seconds awake at 100 mA to connect and send, and Seeed's 14 µA board figure for sleep. Those awake numbers are assumptions I chose, not measurements:",[41,288],{":headers":289,":highlightCol":290,":rows":291},"[\"Scenario\",\"Average current (mA)\",\"Battery life (days)\"]","2","[[\"14 µA sleep, wake every 15 min\",\"0.57\",\"58\"],[\"14 µA sleep, wake every 60 s\",\"8.35\",\"4.0\"],[\"14 µA sleep, wake every hour\",\"0.153\",\"218\"],[\"1 mA sleep, wake every 15 min\",\"1.55\",\"21\"],[\"6.5 mA sleep, wake every 15 min\",\"7.02\",\"4.7\"],[\"Never sleeps, 27 mA modem-sleep\",\"27\",\"1.2\"]]",[13,293,294],{},[130,295],{"alt":296,"src":297},"Bars of battery life for the assumed example: 58 days at 14 µA sleep, 21 days at 1 mA, 4.7 days at 6.5 mA, 1.2 days never sleeping","\u002Fimages\u002Fblog\u002Fesp32-deep-sleep-real-current-draw-battery-days.webp",[13,299,300],{},"The 6.5 mA row is the total JLCPCB estimates for a generic dev board, and the 27 mA row is Seeed's modem-sleep figure for the XIAO ESP32-S3. Two lessons stand out. With a 14 µA sleep current, 98 percent of the charge goes to the 5 awake seconds, so past this point trimming the awake time (a faster connect, a shorter request) beats shaving microamps. And with a dev board's milliamps, sleeping buys far less: at 6.5 mA the regulator and friends are the battery's real load, and the example only gains a few days over never sleeping. Sleeping every minute instead of every 15 minutes cuts the life from 58 to 4 days, which is why the wake interval is usually the biggest knob you have.",[33,302,304],{"id":303},"when-is-deep-sleep-not-worth-it","When is deep sleep not worth it?",[13,306,307],{},"Deep sleep pays when the device does nothing for minutes or hours, wakes on its own schedule, and tolerates a few seconds of reconnecting. It does not pay when the device must answer instantly, or when USB power is always there.",[13,309,310],{},[130,311],{"alt":312,"src":313},"USB-powered ESP32 boards run from a power strip on the desk, while unused batteries sleep on a shelf under a moon","\u002Fimages\u002Fblog\u002Fesp32-deep-sleep-real-current-draw-illustration.webp",[13,315,316,317,321,322,325,326,330,331,333],{},"The three OpenGizmo gadgets are in the second group. The ",[20,318,320],{"href":319},"\u002Fprojects\u002Fgizmo-ticker","Gizmo Ticker"," scrolls prices all the time, the ",[20,323,205],{"href":324},"\u002Fprojects\u002Fgizmo-camera"," must answer an HTTP snapshot at any moment, and the ",[20,327,329],{"href":328},"\u002Fprojects\u002Fgizmo-reolink-switch","Gizmo Reolink Switch"," shows a countdown on its LCD and serves a web app. All are USB-powered and none of the firmware calls any sleep function. I searched the three repositories for sleep and power-save calls and the only one is the camera's ",[123,332,217],{},", which turns Wi-Fi power saving off.",[13,335,336,337,341,342,345],{},"A battery Reolink Switch is an idea, not a build, and it would hit three problems. The README wires the LCD and buzzer to the board's 5 V pad, which Seeed's wiki says has no voltage on battery. The ",[20,338,340],{"href":339},"\u002Fblog\u002Fcontrol-reolink-nvr-esp32","build post"," explains that the firmware logs in to the NVR and keeps a restore timer, so each wake would pay for Wi-Fi and a login. And the button is on D0, which is GPIO1: inside the S3's RTC GPIO range, so waking on it is possible in principle, but the firmware's ",[123,343,344],{},"INPUT_PULLUP"," would have to become an RTC pull-up. I have not tried any of this.",[13,347,348,349,352,353,357],{},"If you only want fewer milliamps without losing the connection, light sleep or the default modem-sleep keep the Wi-Fi connection alive, at a cost of a few mA to tens of mA on the XIAO ESP32-S3 per Seeed's figures, and ",[123,350,351],{},"WIFI_PS_MAX_MODEM"," trades latency and missed broadcasts for a longer listen interval. If you are new to the chip itself, ",[20,354,356],{"href":355},"\u002Fblog\u002Fwhat-is-a-microcontroller","what is a microcontroller"," explains the CPU, RAM and pins that sleep modes switch off.",[33,359,361],{"id":360},"what-should-you-check-before-trusting-a-sleep-number","What should you check before trusting a sleep number?",[13,363,364],{},"The short version: chips sleep at 5 to 10 µA per Espressif, a well-designed board like the XIAO ESP32-S3 lands at 13 to 14 µA, and a generic dev board can be hundreds of times worse because of its regulator, LED and USB bridge. The figures in this post come from datasheets (versions listed above, as of November 2026), Seeed's wiki, Qoitech's August 2026 bench report and JLCPCB's article.",[13,366,367,368,371],{},"The limits are real. I measured nothing, the awake-current and capacity numbers are assumptions, I could not check the CP2102N figures, your board revision may differ, and Seeed's light-sleep figure assumes active Wi-Fi (per Qoitech) while the bench one does not. If battery life matters, put a proper ammeter on your own board and your own firmware. For choosing the board first, read ",[20,369,370],{"href":119},"XIAO ESP32-S3 vs C3 vs C6",".",{"title":254,"searchDepth":373,"depth":373,"links":374},2,[375,376,377,378,379,380,381],{"id":35,"depth":373,"text":36},{"id":82,"depth":373,"text":83},{"id":168,"depth":373,"text":169},{"id":221,"depth":373,"text":222},{"id":275,"depth":373,"text":276},{"id":303,"depth":373,"text":304},{"id":360,"depth":373,"text":361},"guides","Guides","2026-11-14T00:00:00Z","ESP32 deep sleep current is 5 to 10 µA for the chip, but 14 µA to several mA on a dev board. Datasheet figures, wake-up sources and battery life math.","md",[388,391,394,397,400,403],{"question":389,"answer":390},"How much current does an ESP32 use in deep sleep?","Espressif's datasheets list 10 µA for the original ESP32, 7 µA for the ESP32-S3 and ESP32-C6, and 5 µA for the ESP32-C3, with the RTC timer and RTC memory on. Those are chip figures. A dev board adds a regulator, LEDs and a USB bridge, so the board usually draws more.",{"question":392,"answer":393},"Why does my ESP32 dev board draw milliamps in deep sleep?","The chip sleeps, but the parts around it do not. A linear regulator such as the AMS1117 has a typical quiescent current of 5 mA, a power LED can add about 1 mA, and a USB-to-serial bridge stays powered. Boards built for batteries, such as the XIAO ESP32-S3, avoid most of this.",{"question":395,"answer":396},"What is the difference between ESP32 light sleep and deep sleep?","In light sleep the CPU is paused but RAM and peripheral state are preserved, so the program resumes where it stopped. In deep sleep the CPU and most RAM are powered off, only the RTC domain stays on, and the chip restarts the program from the beginning on wake-up.",{"question":398,"answer":399},"What can wake an ESP32-S3 from deep sleep?","According to the ESP-IDF sleep documentation, the ESP32-S3 can wake from deep sleep on the RTC timer, a touch sensor, ext0 (one RTC GPIO), ext1 (several RTC GPIOs) or the ULP coprocessor. On the S3, RTC GPIOs are GPIO0 to GPIO21. Plain GPIO wake-up is mainly a light-sleep feature.",{"question":401,"answer":402},"How long does an ESP32 last on a battery with deep sleep?","Divide the usable battery capacity in mAh by the average current in mA. With 800 mAh usable, 5 seconds awake at 100 mA every 15 minutes and a 14 µA sleep current, the average is 0.57 mA, about 58 days. These are assumed numbers, so measure your own firmware.",{"question":404,"answer":405},"Does the ESP32 keep variables in deep sleep?","Only variables placed in RTC memory. Mark them with RTC_DATA_ATTR and the ESP32 keeps them across deep-sleep cycles. Everything else in normal RAM is lost, because the chip restarts the program from the beginning on each wake-up. A power cycle or reset clears RTC memory too.","\u002Fimages\u002Fblog\u002Fesp32-deep-sleep-real-current-draw.jpg","A maker with glasses and a hand on his chin studies a multimeter set to µA, wired to a small ESP32 dev board, next to a moon with Zzz and a Deep sleep label.","en",{},true,"\u002Fblog\u002Fesp32-deep-sleep-real-current-draw",{"title":5,"description":385},{"loc":411},"blog\u002Fesp32-deep-sleep-real-current-draw","The ESP32 chip draws 5 to 10 µA in deep sleep per Espressif's datasheets. The XIAO ESP32-S3 lists 14 µA, and boards with an AMS1117-type regulator can draw milliamps.",[53,59,417,418,419,420],"Power","Microcontrollers","Hardware","IoT","B1DOo3Jm7oyB09qk4tWb4wAP3TFPUY4TS32sZVf5xuc",[423,429,436,442],{"title":424,"description":425,"image":426,"categoryText":383,"categorySlug":382,"tags":427,"path":270},"ESP32 Strapping Pins by Chip: S3, C3, C6, Classic","Every ESP32 strapping pin on the classic ESP32, S3, C3 and C6 with its default level and what it selects, straight from the datasheets, plus safe-use rules.","\u002Fimages\u002Fblog\u002Fesp32-strapping-pins-by-chip.jpg",[53,59,418,419,428],"Embedded Systems",{"title":430,"description":431,"image":432,"categoryText":433,"categorySlug":434,"tags":435,"path":119},"XIAO ESP32-S3 vs C3 vs C6: Which XIAO to Buy","XIAO ESP32-S3 vs ESP32-C3 vs C6 on memory, radios, antenna, battery charging and deep sleep, from Seeed's wiki, plus why OpenGizmo runs on the S3.","\u002Fimages\u002Fblog\u002Fxiao-esp32s3-vs-c3-vs-c6.jpg","Comparisons","comparisons",[99,59,53,418,419],{"title":437,"description":438,"image":439,"categoryText":433,"categorySlug":434,"tags":440,"path":77},"Which ESP32 Should You Buy? S3, C3, C6, P4 Compared","Buy an ESP32-S3 board for most projects. See when the C3, C6, P4 or the original ESP32 fits better, with datasheet numbers as of November 2026.","\u002Fimages\u002Fblog\u002Fwhich-esp32-chip-should-you-buy.jpg",[53,59,418,419,441],"Home Automation",{"title":443,"description":444,"image":445,"categoryText":383,"categorySlug":382,"tags":446,"path":235},"XIAO ESP32-S3 Pinout: Which Pins Are Safe to Use","XIAO ESP32-S3 pinout: D0 to D10 mapped to GPIO, the default I2C, SPI and UART pads, the one strapping pad to avoid, and two real firmware pin maps.","\u002Fimages\u002Fblog\u002Fxiao-esp32s3-pinout-safe-pins.jpg",[99,59,419,418,30],[448,454,458],{"name":449,"slug":450,"path":451,"count":452,"image":453},"Troubleshooting","troubleshooting","\u002Fblog\u002Fcategories\u002Ftroubleshooting",5,"\u002Fimages\u002Fblog\u002Fesp32-brownout-detector-was-triggered.jpg",{"name":433,"slug":434,"path":455,"count":456,"image":457},"\u002Fblog\u002Fcategories\u002Fcomparisons",8,"\u002Fimages\u002Fblog\u002Fesp32-ota-update-methods-compared.jpg",{"name":459,"slug":460,"path":461,"count":462,"image":463},"Builds","builds","\u002Fblog\u002Fcategories\u002Fbuilds",6,"\u002Fimages\u002Fblog\u002F3d-printed-esp32-enclosure-design-guide.jpg",1795018236237]