ESP32-C5-DevKitC-1
The ESP32-C5-DevKitC-1 is the first ESP32 with dual-band 2.4 GHz + 5 GHz WiFi 6 (802.11ax, 1T1R, band-selectable), paired with BLE 5.0 and an 802.15.4 radio for Thread and Zigbee. A single-core RISC-V at 240MHz, 4MB flash, and 384KB HP SRAM plus 16KB LP SRAM make it a Matter-era drop-in for networks where 2.4 GHz is too crowded or a 5 GHz-only AP is in use.
Best ESP32 when you need 5 GHz WiFi or dual-band connectivity; skip if 2.4 GHz is sufficient — the cheaper C6 gets you WiFi 6 + Thread without the dual-band premium.
Where to Buy
Pros
- Only ESP32 with dual-band 2.4/5 GHz WiFi 6 — unblocks 5 GHz-only networks
- WiFi 6 Target Wake Time + OFDMA improves battery life and dense-network behaviour
- 802.15.4 radio covers Thread, Zigbee 3.0, and Matter in one chip
- BLE 5.0 with long-range coded PHY and advertising extensions
- Shares the DevKitC-1 form factor with the C6 — most projects port with minor pin remapping
Cons
- Single-core at 240MHz is the same compute class as the C3 and C6 — not a performance step up
- 4MB flash and 384KB HP SRAM are typical for the C-series, not the larger N8 variants of S3
- No PSRAM — limits camera or image-buffering workloads
- 1T1R single radio selects one band at a time — not concurrent dual-band like a multi-radio access point
Why dual-band matters
Every other ESP32 variant is 2.4 GHz-only. That's a problem on two fronts. First, many newer routers and mesh systems default to 5 GHz for primary throughput and split 2.4 GHz off to guest or IoT SSIDs. Second, the 2.4 GHz band is shared with Bluetooth, Zigbee, microwaves, and every other consumer IoT device — congestion is severe in apartment buildings and dense suburbs.
The C5 handles both cases. The single 1T1R radio band-selects between 2.4 GHz and 5 GHz and will roam when the host STA reassociates. On a 5 GHz-only AP the C5 connects where a C6 cannot. On congested 2.4 GHz networks, moving to 5 GHz typically reduces contention — both chips use a single-stream 20 MHz link, so the real win is airtime and latency in crowded bands, not raw throughput.
WiFi 6 features that actually matter
WiFi 6 on an ESP32 is mostly about power and contention, not raw throughput — the physical radio on the C5 is still a single-stream link. The useful WiFi 6 features are Target Wake Time (the AP schedules when the C5 wakes to check for data, cutting keep-alive traffic dramatically), OFDMA (multiple devices share a single wide channel instead of serializing), and BSS colouring (inter-AP interference handling).
For battery sensors, TWT is the headline. A C5 that wakes every 5 minutes under TWT runs roughly 2x longer on the same battery as a C6 polling on WiFi 4. For smart-home meshes with 20-50 devices per AP, OFDMA is the feature that prevents command latency from ballooning during busy periods.
WiFi 6 and Dual-Band: Why It Matters for IoT
The ESP32-C5 is the first ESP32 to support dual-band WiFi — 2.4 GHz and 5 GHz — and the first with 802.11ax (WiFi 6). These are two separate upgrades that solve different problems, and understanding when each one actually helps for IoT is important because neither is universally beneficial.
Dual-band support addresses a real deployment pain point. Modern mesh routers from Eero, Google Nest, and UniFi often run a single SSID that steers clients to 5 GHz. Devices that only support 2.4 GHz — every previous ESP32 — can struggle to connect or get relegated to a legacy band with degraded performance. In enterprise environments, 2.4 GHz may be disabled entirely for security policy reasons. The C5 eliminates this class of deployment failure. Its 1T1R radio selects between bands, so it associates with whichever frequency the AP offers. Note this is band-selectable, not simultaneous dual-band — the radio operates on one band at a time, switching when it reassociates.
WiFi 6 (802.11ax) brings two features that genuinely matter at the IoT scale. Target Wake Time (TWT) lets the access point schedule when the C5 wakes to exchange data, replacing the constant polling of WiFi 4/5. For a sensor that reports temperature every 5 minutes, TWT can cut WiFi power consumption roughly in half compared to the C6's WiFi 6 without TWT scheduling. OFDMA (Orthogonal Frequency-Division Multiple Access) subdivides a WiFi channel so multiple IoT devices transmit simultaneously in different frequency sub-bands, rather than waiting for sequential airtime. In a dense apartment with 30-50 smart home devices sharing one AP, OFDMA reduces the latency spikes that cause smart home commands to feel sluggish.
Where WiFi 6 does not help: raw throughput. The C5's single-stream 20 MHz link tops out around 120 Mbps PHY rate — plenty for sensor data, but the improvement over WiFi 5 is modest at this channel width. WiFi 6's throughput gains primarily benefit multi-stream, wide-channel configurations (80/160 MHz) used by laptops and phones. For IoT, the power and contention improvements are the real payoff.
Matter + Thread + Zigbee coverage
The 802.15.4 radio mirrors what the C6 and H2 offer: Thread 1.3, Zigbee 3.0, and Matter over both Thread and WiFi. Where the C5 pulls ahead is specifically as a Thread border router — the dual-band WiFi avoids the classic coexistence problem where the border-router radio and the Thread radio fight for 2.4 GHz airtime. Run WiFi on 5 GHz and leave 2.4 GHz clear for Thread and the mesh performs noticeably better.
For end devices, the C5 and C6 are functionally equivalent on Matter. Pick the C5 for 5 GHz WiFi; pick the C6 for cost on 2.4 GHz-only networks.
Development Status and Early Adopter Considerations
The ESP32-C5 is Espressif's newest chip, and SDK support is still maturing in ways that affect real-world development. ESP-IDF has full C5 support with WiFi 6 dual-band, BLE 5.0, and 802.15.4 all functional. Arduino-ESP32 added C5 board definitions in late 2025, but the gap between "board compiles" and "ecosystem works" is meaningful. Libraries that rely on chip-specific register access, custom WiFi event handlers, or low-power mode configurations may not have been updated for C5 compatibility. Popular Arduino libraries like AsyncWebServer, ESPAsyncTCP, and PubSubClient work, but less common libraries targeting specific ESP32-S3 or C6 peripherals may require porting effort.
ESPHome support landed in 2025 through the standard ESP-IDF build path, and core components — GPIO, I2C, SPI, UART, WiFi, BLE — work as expected. However, some ESPHome components that were written specifically for the C6's register layout have not been tested on the C5. The dual-band WiFi configuration in ESPHome is newer and less battle-tested than the C6's 2.4GHz-only path. Early adopters report occasional association issues with specific 5GHz access points that use DFS channels (dynamic frequency selection), which require the client to handle radar detection handoffs — a scenario the C6 never encounters.
For production projects shipping in 2026, the C6 is the more proven choice. Its ESP-IDF support is two years more mature, Arduino library compatibility is thoroughly validated, and ESPHome component coverage is comprehensive. The C6 shares the same 802.15.4 radio for Thread and Matter, the same BLE 5.0, and WiFi 6 on 2.4GHz. Unless your deployment specifically requires 5GHz connectivity — because the target network is 5GHz-only, or because 2.4GHz congestion is a measured problem — the C6 delivers identical protocol coverage with lower risk.
For R&D labs and forward-looking product designs, the C5 is worth evaluating now. WiFi 6 on 5GHz will matter increasingly as IoT device density grows and 2.4GHz band congestion worsens in urban environments. Mesh router systems from Eero, Google Nest, and UniFi are already steering clients toward 5GHz by default. Building familiarity with the C5's dual-band capabilities today positions your team to ship on it when tooling matures — rather than scrambling to adopt it when 5GHz becomes a hard requirement for your deployment environment.
Full Specifications
Processor
| Specification | Value |
|---|---|
| Architecture | RISC-V [1] |
| CPU Cores | 1 [1] |
| Clock Speed | 240 MHz [1] |
Memory
| Specification | Value |
|---|---|
| Flash | 4 MB [1] |
| SRAM | 384 KB [1] |
| lp_sram_kb | 16 KB [1] |
Connectivity
| Specification | Value |
|---|---|
| WiFi | 802.11 a/b/g/n/ax (dual-band 2.4/5 GHz, WiFi 6, band-selectable 1T1R) [1] |
| Bluetooth | 5.0 [1] |
| Thread | Yes [1] |
| Zigbee | 3.0 [1] |
| Matter | Yes [1] |
| dual_band | Yes — first dual-band (2.4/5 GHz) ESP32 (single radio, band-selectable) [2] |
I/O & Interfaces
| Specification | Value |
|---|---|
| GPIO Pins | 27 [3] |
| ADC Channels | 6 [3] |
| SPI | 3 [3] |
| I2C | 2 [3] |
| UART | 3 [3] |
| USB | USB 2.0 (CDC) [3] |
Power
| Specification | Value |
|---|---|
| Input Voltage | 5 V [1] |
| Deep Sleep Current | 12 uA [1] |
Physical
| Specification | Value |
|---|---|
| Dimensions | 67 x 26 mm [3] |
| Form Factor | Standard breadboard [3] |
Who Should Buy This
The C5 is the only ESP32 that associates with 5 GHz-only APs. Mesh networks, Wi-Fi 6E hubs, and most corporate SSIDs now default to 5 GHz — the 2.4 GHz-only C3/C6/S3 silently fail to connect in those environments.
WiFi 6 dual-band backhaul plus a native 802.15.4 radio makes the C5 a strong border-router choice. It avoids the co-existence contention that 2.4 GHz-only routers hit when running a busy Thread mesh alongside WiFi.
WiFi 6 TWT extends sleep time significantly versus WiFi 4, so battery life improves. If your AP is 2.4 GHz-only, the ESP32-C6 delivers the same protocol set at a lower cost.
Better alternative: ESP32-C6-DevKitC-1
Single-core RISC-V, no PSRAM, no DVP or MIPI-CSI camera interface. The ESP32-S3 (with PSRAM and DVP) or ESP32-P4 (with MIPI-CSI) is the right tool.
Better alternative: ESP32-S3-DevKitC-1
The C5 is new enough (as of 2026) that some Arduino libraries and ESPHome components lag behind C6 support. If you don't need 5 GHz, start on the C6 for smoother tooling.
Better alternative: ESP32-C6-DevKitC-1
Ecosystem & Community
The ESP32-C5 is very new (2025) with growing but still maturing tooling — ESP-IDF is primary, Arduino and ESPHome support added but some components lag behind C6 maturity.
Compatible Software
What to Build First
Deploy a temperature sensor on a 5GHz-only network where 2.4GHz ESP32 boards cannot connect. Demonstrates the C5's unique dual-band capability for modern mesh WiFi systems that default to 5GHz.
View tutorial →Must-Have Accessories
Tutorials & Resources
- ESP32-C5 Getting Started GuideOfficial ESP-IDF setup and first project guide for the ESP32-C5-DevKitC-1docs
- ESP32-C5 DatasheetHardware specifications including dual-band radio capabilities, power modes, and pin functionsdocs
- Arduino-ESP32 (C5 board support)Arduino core with ESP32-C5 support — enables Arduino IDE development on the dual-band platformgithub
Frequently Asked Questions
Is the ESP32-C5 dual-band WiFi 6?
Yes — dual-band in the sense that the single 1T1R radio is band-selectable between 2.4 GHz and 5 GHz and implements 802.11ax (WiFi 6) on both, including Target Wake Time and OFDMA. It is not two concurrent radios like a dual-radio access point. No other ESP32 variant reaches 5 GHz.
ESP32-C5 vs ESP32-C6: which should I choose?
Pick the C5 if you need 5 GHz WiFi, dual-band roaming, or a Thread border router that keeps 2.4 GHz clear for the mesh. Pick the C6 when your network is 2.4 GHz-only — the C6 is cheaper, has more mature tooling, and provides the same Thread/Zigbee/Matter support.
Does the ESP32-C5 support Matter?
Yes. The C5 supports Matter over both WiFi (2.4 or 5 GHz) and Thread via its 802.15.4 radio. That makes it compatible with Apple Home, Google Home, Amazon Alexa, and Samsung SmartThings hubs.
How does ESPHome support the ESP32-C5?
ESPHome added C5 support in 2025 via the standard ESP-IDF build path. Some third-party components still default to C6 configs — check per-component compatibility notes before relying on rare peripherals.
Is the ESP32-C5 pin-compatible with the ESP32-C6?
The C5 DevKitC-1 and C6 DevKitC-1 share the same form factor and most pin functions, so many projects port directly. A handful of peripheral pins differ — verify against the datasheet if your project uses SDIO, USB, or the low-power GPIO mux.
What's the ESP32-C5's deep-sleep current?
Typical deep-sleep current is around 12 µA with RTC timer and LP memory retained per the ESP32-C5 datasheet v1.1 — higher than the C6's ~7 µA but still low enough for multi-year battery life on small sensors that wake infrequently when combined with WiFi 6 TWT.