🔍 Find your chip and USB type
Two things decide your firmware file: the chip (ESP32, ESP32-S3 or ESP32-C3) and, for S3 and C3, the USB type: native USB gives _usb, a USB-to-UART bridge gives _uart.
- Install esptool
pip install esptool
- Read the chip
Plug the board in (if it is not detected, hold BOOT while plugging in), then run:
esptool chip-id
With esptool 4.x the command is esptool.py chip_id. If several ports are connected, add --port COM5 (Windows) or --port /dev/ttyUSB0 (Linux).
Look for the line “Chip is …” (example)
Chip is ESP32-S3 (QFN56) (revision v0.1)
Features: WiFi, BLE, Embedded PSRAM 8MB
- Read the flash size (optional)
esptool flash-id
Look for Detected flash size: 8MB. The firmware needs 4MB or more (esptool 4.x: esptool.py flash_id).
- Find the USB type
pyserial is installed with esptool, so you can list the ports with their USB IDs:
python -m serial.tools.list_ports -v
Read the “USB VID:PID=” value (example)
COM5
desc: USB Serial Device (COM5)
hwid: USB VID:PID=303A:1001 ...
| VID | Device | Firmware |
303A | Espressif native USB | _usb |
10C4 | CP210x bridge | _uart |
1A86 | CH340 / CH9102 bridge | _uart |
0403 | FTDI bridge | _uart |
- Open the tool
Use Chrome or Edge on a computer (it needs Web Serial). Nothing to install.
Open Espressif esptool-js ↗
- Connect
Plug the board in, click Connect, and choose your board’s port in the browser dialog. If it fails, hold BOOT while plugging in and try again.
- Read the log
The tool detects the chip when it connects and prints it in its log (for example ESP32-S3), with the chip features. That is your chip.
- Disconnect
Click Disconnect or close the tab. Only one program can use the port at a time, so do this before flashing with another tool.
This tool tells you the chip, not the USB type. For the USB type, use the USB type (no tools) tab.
Plug the board in and check how your computer names the port.
| System | Native USB (_usb) | Bridge (_uart) |
Windows Device Manager → Ports → Properties → Details → Hardware Ids | VID_303A | VID_10C4 (CP210x), VID_1A86 (CH340), VID_0403 (FTDI) |
macOS
ls /dev/cu.* | cu.usbmodem… | cu.usbserial-…, cu.SLAB_USBtoUART, cu.wchusbserial… |
Linux
ls /dev/ttyACM* /dev/ttyUSB* and lsusb | ttyACM0, ID 303a:… | ttyUSB0, ID 10c4:ea60, 1a86:7523 or 1a86:55d4, 0403:6001 |
Two USB connectors on your board? Use the type of the one you flash through. Boards labelled “UART” or “COM” usually go through a bridge; the one labelled “USB” is usually native.
Then pick your firmware
| Chip | USB type | File suffix |
| ESP32 | not needed | _esp32.bin |
| ESP32-S3 | native USB / bridge | _esp32s3_usb.bin / _esp32s3_uart.bin |
| ESP32-C3 | native USB / bridge | _esp32c3_usb.bin / _esp32c3_uart.bin |
Any other chip (for example ESP32-S2 or ESP32-C6) has no firmware yet.