ESP32-S3-DevKitC-1

Board
by Espressifesp32-s3-devkitc-1≈ medium (~$15–50)

Also known as: esp32-s3-devkitc-1-n32r8v, esp32-s3-devkitc1-n16r16, esp32-s3-devkitc1-n16r2, esp32-s3-devkitc1-n16r8, esp32-s3-devkitc1-n4r2, esp32-s3-devkitc1-n4r8, esp32-s3-devkitc1-n8r2, esp32-s3-devkitc1-n8r8

View 9 firmware recipes · 1 known good
ESP32-S3-DevKitC-1 board
Board
ESP32-S3-DevKitC-1 pinout
Pinout

Specifications

Radiosinherited from ESP32-S3

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

USB

Native USB
yes
Connector
micro-usb

Board

Form factor
devkit
Battery connector
no
Charging
no

Display & extras

Extras
rgb-led
Built onESP32-S3-DevKitC-1 BoardESP32-S3-WROOM-1 ModuleESP32-S3 SoC

ESP32-S3-WROOM-1 dev board with two micro-USB ports (UART bridge + native USB OTG) and an addressable RGB LED.

Firmware for this board

Known good

  • WLEDKnown goodhomeweb flasher
    Flash WLEDweb flasherknown-goodread the caveat

    Known good 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.

    Caveat: `board = esp32-s3-devkitc-1` in several official ESP32-S3 build environments; flash the matching S3 build from install.wled.me.

Declared

  • ESP-Claw For StickS3Declaredmulti
    Flash ESP-Claw For StickS3guided

    Declared 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.

Unverified

  • ESP32 Bit PirateUnverifiedpentest
    Flash ESP32 Bit Pirateguidedread the caveat

    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.

    Caveat: esp32-bit-pirate names this board as esp32-s3-devkitc-1 in its platformio.ini (env s3-devkit); derived from the repo's own build files, not verified on hardware.

  • ESPHomeUnverifiedhomeweb flasher
    Flash ESPHomeweb flasherread the caveat

    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.

    Caveat: ESPHome's `esp32:` component targets a standard Espressif devkit per chip variant by default; the Espressif ESP32-S3-DevKitC-1 is that reference board for `variant: esp32s3`, so any esphome YAML with that variant (or no board override) runs on it unmodified.

  • KryonOSUnverifiedmulti
    Flash KryonOSguidedread the caveat

    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.

    Caveat: kryonos names this board as esp32-s3-devkitc-1 in its platformio.ini (env esp32-s3-devkitc-1-n16r8); derived from the repo's own build files, not verified on hardware.

  • NerdMiner v2Unverifieddisplay
    Flash NerdMiner v2guidedread the caveat

    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.

    Caveat: nerdminer-v2 names this board as esp32-s3-devkitc-1 in its platformio.ini (env ESP32-S3-devKitv1); derived from the repo's own build files, not verified on hardware.

  • NightDriverStripUnverifiedmulti
    Flash NightDriverStripguidedread the caveat

    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.

    Caveat: nightdriverstrip names this board as esp32-s3-devkitc-1 in its platformio.ini (env mesmerizer_devkit_s3); derived from the repo's own build files, not verified on hardware.

  • OpenMQTTGatewayUnverifiedhome
    Flash OpenMQTTGatewayguidedread the caveat

    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.

    Caveat: openmqttgateway names this board as esp32-s3-devkitc-1 in its platformio.ini (env esp32s3-dev-c1-ble); derived from the repo's own build files, not verified on hardware.

  • RuViewUnverifiedmulti
    Flash RuViewguidedread the caveat

    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.

    Caveat: RuView's own README names this board twice: "Recommended boards | ESP32-S3-DevKitC-1, XIAO ESP32-S3", and a dedicated build note for "Display-less boards (ESP32-S3-DevKitC-1 and similar)" telling you to build with the `sdkconfig.defaults.devkitc` overlay, because the default build compiles display support in and its runtime panel probe false-positives on a board with no panel — which disables the MGMT+DATA CSI upgrade and collapses CSI yield to 0 pps. This board record carries 4 MB of flash, so the matching prebuilt package is `esp32-csi-node-v0.8.8-s3-4mb-flash-bundle.zip`; the `s3-8mb` bundle is for 8 MB S3 boards. No `flash` block is declared on purpose: the bundle is a four-file install (bootloader 0x0, partition-table 0x8000, otadata 0xf000, app 0x20000) and the bare `esp32-csi-node-v0.8.8-s3-4mb.bin` asset is the application image only, so it cannot be flashed at 0x0 as a single merged binary and must not be offered as a one-click in-browser flash. `unverified`: not yet run on real hardware here.

Notes

  • Two micro-USB: a UART-bridge port and the native ESP32-S3 full-speed USB OTG port
  • Addressable RGB LED (GPIO38 on v1.1, GPIO48 on v1.0)
  • Carries ESP32-S3-WROOM-1/-1U/-2; fixed here to esp32-s3-wroom-1
  • Dimensions only in a separate Dimensions PDF (omitted)
  • io.gpio_free=27 DERIVED, not quoted (SPEC-io-power.md §5.3). Header J1+J3 break out 36 pads total (quoted from the user guide pin tables: J1 = GPIO 3-18,46; J3 = GPIO 0-2,19-21,35-45,47,48). Subtracting esp32-s3's soc.reserved_pins that are exposed -- strapping {0,3,45,46} (4) and usb_flash_tied {19,20,35,36,37} (5) -- gives 36 - 4 - 5 = 27. 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-S3-DevKitC-1 — 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.