Quick summary: Espressif released Arduino-ESP32 4.0.0 on 19 November 2026. The first stable 4.x core moves Arduino development to ESP-IDF 6.1.1, adds ESP32-S31 support and brings a substantial set of networking, WebServer, USB, OTA and board-definition changes. Existing projects should be rebuilt and tested before a fleet-wide upgrade.

Arduino-ESP32 4.0.0 is now the latest stable release of Espressif’s Arduino core. This is a major-version transition, not another patch on the 3.3 branch: the underlying framework jumps from ESP-IDF 5.5.5 in the recent 3.3.x line to ESP-IDF 6.1.1.
That timing matters because Arduino-ESP32 3.3.13 arrived only a day earlier. The two releases serve different needs. Version 3.3.13 is the conservative maintenance option for existing 3.x projects; 4.0.0 brings the newer ESP-IDF base and should be treated as a planned migration.
What Arduino-ESP32 4.0.0 changes
The rebase puts Arduino projects on the same ESP-IDF 6.1.1 foundation covered in our ESP-IDF 6.1.1 report. It does not turn an Arduino sketch into a native ESP-IDF project, but libraries that call ESP-IDF functions directly now compile against the 6.1.1 headers and behaviour.
- Networking and WebServer: the release adds IPv6 DNS configuration, stops failed DNS lookups from continuing into a connection attempt, fixes a full AsyncUDP queue lock-up and tightens WebServer header, upload and multi-client authentication handling.
- OTA and security helpers: there is a new OTA
onPrepare()callback, password prompting inespota, a new HMAC builder, Base64 decode functions and configurable TLS cipher selection throughNetworkClientSecure. - Peripheral work: I²C slave operation is fixed for newer SoCs, USB Audio Class 1 and 2 gain multiple sample-rate support, and TinyUSB CDC receives additional notification and host-detection fixes.
- Board definitions: 4.0.0 adds or updates variants for hardware including the LilyGo T-Deck, DFRobot FireBeetle 2 ESP32-C5PriceAliExpress price, SparkFun ESP32-P4Price IoT RedBoards, ELEGOO ESP32-C6 and several ESP32-S3 boards.
The documented 3.x-to-4.0 API change
Espressif’s migration guide currently highlights one Arduino-layer breaking change: Server-Sent Events state moves from NetworkClient to WebServer. The old NetworkClient::setSSE() and NetworkClient::isSSE() methods still work for now, but are deprecated and scheduled for removal in Arduino-ESP32 5.0.
New code should call WebServer::enableSSE() inside the request handler and query WebServer::isSSE(). The change is small, but it corrects ownership: keeping the connection open is a server directive rather than a property of whichever TCP client wrapper happens to expose it.
The short Arduino migration guide should not be read as a promise that every third-party library will compile unchanged. Libraries that use private ESP-IDF headers, removed IDF APIs or target-specific internals deserve a clean rebuild on a copy of the project. For deployed devices, test flash layout, networking, OTA and sleep behaviour before changing the production toolchain.
ESP32-S31 support is core support, not a new board
The release adds Arduino-core support for the ESP32-S31 chip family. That means the framework and build system can target the silicon; it does not guarantee that every ESP32-S31 development board has a complete variant, correct pin map or working definition for all exposed peripherals. Board makers still need to supply and validate those details.
Developers looking for actual S31 hardware can compare that software milestone with our coverage of the ESP-Mosaico ESP32-S31 development kit. The distinction is important: chip support enables board work, but it is not evidence that a particular display, camera, radio path or connector is ready in Arduino.
Availability and upgrade advice
Arduino-ESP32 4.0.0 is published as the latest stable GitHub release. For a new project that needs ESP-IDF 6.1.1 or ESP32-S31, it is the logical starting point. For a working 3.x installation, update one representative board first and keep 3.3.13 available for rollback. A major core update is the wrong place for an untested mass upgrade, even when a simple sketch compiles cleanly.

