Flash ESP Firmware from Your Browser
Connect an Espressif device through Web Serial and write one or more BIN files using esptool-js. Each file is paired with its flash offset; the correct files and offsets come from your firmware build or release instructions.
Browser, Board and Firmware Requirements
Use a desktop browser with Web Serial enabled, such as Chrome or Edge, over HTTPS or localhost. Your board must expose a compatible serial download connection. A data USB cable and, for some adapters, a system USB-to-serial driver are required.
The esptool-js dependency includes loaders for ESP8266 and ESP32 variants such as ESP32-S2, S3, C3 and C6. Library support is not a guarantee that a particular board, USB connection or security configuration has been tested with this page. Confirm the detected chip and your firmware’s intended target.
How to Flash ESP Firmware
- Close other serial monitors, connect the board and select a suitable connection speed.
- Select Connect and choose the board’s serial port. Check the detected chip information.
- Add each BIN file and enter its documented starting offset. Check the complete file-and-address list.
- Decide whether a full erase is required by the firmware instructions; leave it disabled when it is not needed.
- Start flashing and wait for completion. Reset the board if necessary, then disconnect before opening the Web Serial Terminal.
Firmware Files and Flash Offsets
Separate bootloader, partition-table and application files may each need different offsets. A merged image has its own documented starting offset. Do not treat the prefilled addresses as a universal recipe.
Use the flashing command, manifest or release instructions supplied with the exact firmware build. Enter offsets in hexadecimal with a 0x prefix, or in decimal. Ensure files do not overlap and fit the target’s flash layout.
Full erase removes flash contents, which can include firmware, stored credentials, settings and filesystem data. This interface does not create a backup before erasing.
Connection and Boot Troubleshooting
No port or failure to open: check the data cable, system driver and permissions, and close other programs using the port.
Failed handshake: follow your board’s download-mode instructions. On many ESP32 development boards, holding BOOT while pressing and releasing EN/RESET enters download mode; button behavior varies by board and chip.
Interrupted writes: try a lower speed, a shorter cable and a stable power supply. Confirm that no other application is accessing the board.
Flash completes but the application does not boot: verify chip compatibility, the complete set of files, their offsets and the partition layout. Follow the board’s instructions to leave download mode. Secure boot or flash encryption may require a different, project-specific workflow.
Frequently Asked Questions
Where do I find the correct flash offsets?
Use the build output’s flashing command, firmware manifest or release documentation. Offsets depend on the chip and project layout; the application offset alone is not a complete flashing plan.
Do I always need to hold BOOT?
No. Many boards support automatic reset into download mode. If that fails, use the manual sequence documented for your exact board.
Can I upload HEX or ELF firmware?
This interface accepts BIN files. Obtain the BIN images and their offsets from the project’s build or release process.
Are firmware files uploaded to a server?
The flashing code reads files locally and sends their bytes to the selected serial device. It does not upload them to a flashing server. The website also loads third-party analytics and advertising scripts.