Blog
ESP32 Erase: Wipe Flash, Reset Settings
Erasing an ESP32 is the fix people reach for after reset fails, and it’s usually the one that works — it removes firmware, settings, and everything else. What you can erase, what survives, and what “format” means on a chip with no disk.
How to Erase ESP32?
esptool.py erase_flash, connected over USB. It wipes the entire chip — bootloader, firmware, NVS, everything — and most boards re-enter download mode afterwards, ready for re-upload. On Windows I run esptool.py –port COM7 erase_flash and wait for “Chip erase completed successfully”. How to erase esp32 is, in 95% of cases, that one command; the flashing guide covers the re-upload.
How to Format ESP32?
There is no disk to format — flash is raw silicon — but filesystems live inside it. SPIFFS.format() or LittleFS.format() clears just that partition, the closest thing to formatting an ESP32. For a clean slate, how to format esp32 means erasing the whole chip and letting firmware rebuild its filesystem on first boot.
What Type of Information Does a ESP32 Take?
Flash holds four things: the firmware, a partition table saying where everything lives, NVS key-value settings, and file partitions like SPIFFS or LittleFS. RTC memory is a fifth, battery-backed area. That’s all the non-volatile storage an ESP32 has. What type of information does a esp32 take is answered by that list — there is no other drive.
What Type of Information Does a ESP32 Use?
At runtime it reads the same regions: code executes from flash, WiFi credentials and calibration come from NVS, files from SPIFFS or LittleFS. What type of information does a esp32 use day to day is mostly NVS — the Preferences library writes there, and so does the WiFi stack. Erase flash and the chip boots with none of it.
Does erasing my ESP32 delete the code on it?
Yes, entirely — erase_flash removes the firmware, and the chip boots into the ROM bootloader to wait. You must upload code again after an erase; that’s the point, not a bug. Most boards auto-enter download mode afterwards.
Can I erase only part of the flash?
esptool.py erase_region 0x9000 0x5000 clears just the NVS area, and partition tools do the same by name. Precise addresses depend on your partition table — official documentation is thin here — so for most people a full erase is simpler than regional surgery. If you must keep the firmware, NVS-only is the safe middle ground.
How do I wipe just the WiFi credentials and settings?
Erase the NVS partition, or clear it from code: Preferences.clear() wipes the default namespace; nvs_flash_erase() plus nvs_flash_init() does the same in ESP-IDF. Firmware stays intact while saved passwords and calibration go — handy for “out of the box” without reflashing.
Can I erase an ESP32 without a computer?
Not the flash itself — no button or on-device wipe exists. The closest options are a sketch that clears NVS on boot or an OTA reflash, and both still run code that lives in flash. A truly empty chip needs a host; practice in the simulator before you own one.
What happens if I erase while the firmware is running?
Don’t. Erasing the region the chip executes from produces garbage reads and a stuck reboot loop — the classic “I erased and now it’s dead” post. It isn’t dead: re-enter download mode and reflash. The ESP32 is remarkably hard to actually kill, as this FAQ series repeats.
Will erasing fix a crashing or bricked-looking ESP32?
Usually yes — corrupt firmware, half-written OTA updates, and bad partition layouts heal with a full erase and reflash. If the chip still won’t talk after erase_flash, the problem is outside flash: power, the USB chip, or the board. Erase is a great first cure, not a universal one, and it mostly works; flash known-good firmware afterwards.
Erasing, Without Consequences
Want to feel what “flash erased to 0xFF” means before doing it to a board you care about? Every simulator example is a clean-flash machine: run any sketch, break it, refresh — the virtual chip returns to factory state with no esptool and no risk. The erase commands in this FAQ are for real silicon; rehearsing the build-and-verify loop around them is free here.