Firmware v0.10.5 is the recommended stable release. The Web Flasher keeps the v0.9.32 and v0.9.28 stable images available for recovery, plus the v0.9.16 legacy recovery image; newer experimental builds require explicit confirmation.
CHECKING VERSION ARCHIVE
Display / Host — Waveshare ESP32-S3-Touch-LCD-3.5
SELECTED FIRMWARE
Checking...
Retrieving compiled and archived images.
Build information unavailable
EXPERIMENTAL / NOT TESTED.This firmware has not been physically validated. Use a tested version for normal operation.
Preserve Wi-Fi and Bluetooth pairing: when ESP Web Tools asks "Erase device", leave the checkbox UNCHECKED. Erasing deletes the device NVS (saved Wi-Fi and Bluetooth bond keys). Full erase is only for an intentional factory reset.
Checking available firmware versions...
Recovery: touchscreen freezes or display reboots
Connect the Waveshare Rev2.0 display to your computer with a USB data cable. Leave the computer on its normal Wi-Fi network.
Select v0.10.5 — recommended stable. The exact v0.9.32 and v0.9.28 images remain available as previous stable recovery; v0.9.16 is retained as legacy recovery.
If the USB serial port is unavailable because the new firmware keeps restarting, enter ESP32-S3 download mode using the board's BOOT and RESET controls, then retry connecting.
Always leave the Erase device checkbox unchecked for normal updates. An erase resets NVS and deletes saved Wi-Fi and BLE bonds. From v0.5.8, the split image writes bootloader, partition table and application without targeting NVS. Older merged installers can overwrite settings even without Erase. An SD Wi-Fi backup is plaintext and should be created before erasing. For a clean downgrade, you can choose Erase device in the installer. This will also erase saved Wi-Fi credentials and other settings.
Target limitation: these images are for the Waveshare ESP32-S3-Touch-LCD-3.5 non-B, Rev2.0 display. Do not flash a XIAO radio module or a Waveshare 3.5B with this image. Firmware installation may overwrite data.
How versions are maintained
The newest candidate is automatically published after the GitHub Actions build and checks succeed; it remains labeled experimental until hardware validation. The latest stable firmware is selected by default. Firmware images are compiled automatically in GitHub Actions from pinned source commits. The browser installs the compiled binary; it does not compile ESP-IDF source code locally. Each selectable build keeps its own manifest and SHA-256 checksum. Obsolete and known-broken versions are excluded from the active Web Flasher list; historical source commits remain in GitHub.