ESP32-DevKitC V4

Board
by Espressifesp32-devkitc-v4≈ cheap (under ~$15)
Flash this board — 2 firmware options · Unverified
ESP32-DevKitC V4 pinout
Pinout

Specifications

Radiosinherited from ESP32

Wi-Fi
Wi-Fi 4 · 2.4 GHz
Bluetooth LE
BLE 4.2
Bluetooth Classic
yes
802.15.4
no

USB

Native USB
no
Connector
micro-usb

Board

Form factor
devkit
Battery connector
no
Charging
no
Built onESP32-DevKitC V4 BoardESP32-WROOM-32E ModuleESP32 SoC

Espressif's small ESP32-WROOM/WROVER dev board: one micro-USB bridged to UART, most GPIOs on dual headers.

Firmware for this board

Unverified

  • ESPHomeUnverifiedhomeweb flasher
    Flash ESPHomeweb flasher

    Unverified esp-atlas asserts this board↔firmware link at the shown trust tier — it does not guarantee your specific unit or the current firmware version. Flashing can erase keys/config and can brick the device. At your own risk.

  • TasmotaUnverifiedhomeweb flasher
    Flash Tasmotaweb flasher

    Unverified esp-atlas asserts this board↔firmware link at the shown trust tier — it does not guarantee your specific unit or the current firmware version. Flashing can erase keys/config and can brick the device. At your own risk.

Notes

  • Single micro-USB (power/flash/comms via on-board USB-to-UART bridge); classic ESP32 has no native USB
  • Bridge chip model not named in the official user guide (omitted)
  • Ships with several module variants; fixed here to esp32-wroom-32e
  • Dimensions live only in a separate Dimensions PDF (omitted, not guessed)
  • io.gpio_free=17 DERIVED, not quoted (SPEC-io-power.md §5.3). Header J2+J3 break out 32 pads total (quoted from the user guide pin tables: J2 = GPIO 9-14,25-27,32-36,39; J3 = GPIO 0-8,15-19,21-23). Subtracting esp32's soc.reserved_pins that are exposed -- strapping {0,2,5,12,15} (5), input_only {34,35,36,39} (4), and usb_flash_tied {6,7,8,9,10,11} (6) -- gives 32 - 5 - 4 - 6 = 17. Math not vendor-stated; verify before treating as exact.

Verify my board

Reads the connected chip over USB and checks it against what esp-atlas cites for ESP32-DevKitC V4 — over Web Serial, no backend, nothing leaves your browser.

In-browser verify needs Web Serial: Chrome or Edge on a desktop. Safari, Firefox and phones cannot do it.

Serial monitor

Not connected.