Have a project in mind? Let's talk.

ESP32 Matter development has settled into a clear shape: Espressif ships a production-ready SDK for Matter, silicon that covers both Wi-Fi and Thread transports, and tooling that takes a devkit from a blank flash to a commissioned device controllable from a phone. What Matter adds on top of the ESP32 story you may already know is a standard application layer, so a light, lock, or sensor you build speaks the same data model to every major ecosystem. This guide walks the platform choices, the two setup paths, a first build, commissioning, and the data model where your product actually lives, all from Espressif's own documentation. Source: Introduction, Espressif's SDK for Matter Programming Guide
Espressif describes its Matter solutions as three layers: a full spectrum of Matter device platforms, a production-ready SDK, and Matter integration with its ESP RainMaker cloud. The platform split is the first practical fact: Wi-Fi-enabled SoCs such as the ESP32, ESP32-C, and ESP32-S series build Matter Wi-Fi devices, while the 802.15.4 parts, the ESP32-H series, ESP32-C5, and ESP32-C6, build Matter Thread devices. Combining an ESP32-H with a Wi-Fi SoC yields a Thread Border Router connecting the Thread network to Wi-Fi, with devkits, reference designs, and an SDK supporting Thread 1.3 for Matter. Source: Introduction, Espressif's SDK for Matter Programming Guide
The same documentation covers the bridge angle: Matter-Zigbee and Matter-BLE Mesh bridge solutions let non-Matter devices join a Matter fabric, which is how existing Zigbee product lines get a path forward without a hardware redesign. On the software side, the ESP-Matter SDK is built on the open source Matter SDK and adds simplified APIs, commonly used peripherals, and tools for security, manufacturing, and production, plus ESP RainMaker and ESP Insights integration for cloud services and remote diagnostics. Source: Introduction, Espressif's SDK for Matter Programming Guide
If you want a zero-setup taste before installing anything, Espressif's Launchpad lets you test Matter on Espressif devices in the browser, and its web-based Data Model Validator at the esp-matter-tools site checks a device data model before you commit it to firmware. Source: Introduction, Espressif's SDK for Matter Programming Guide
The developing guide offers a fork early: set up ESP-IDF and ESP-Matter on your host, or use the official Docker image that already includes both. Host setup supports Ubuntu 20.04, 22.04, or 24.04 LTS, macOS 10.15 or later, and Windows through WSL2, with the caveat that you clone repositories inside the WSL environment rather than a mounted directory. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
Within a host setup there is a second fork. The ESP Matter component, added with idf.py add-dependency "espressif/esp_matter^1.4.0", is the lighter path: SDK only, no repository clone, aimed at product applications. The full ESP-Matter repository adds the examples and the host tools, CHIP-tool, CHIP-cert, and ZAP, and is the path for development, commissioning, certification, and data-model work. Choose the component when you know your data model, the repository while you are still discovering it. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
The SDK's example set covers Light, Light Switch, Zap Light, Zigbee Bridge, and BLE Mesh Bridge. The build flow is standard ESP-IDF: idf.py set-target for your chip, then idf.py flash monitor. Two details from the docs save real time: the default device for a target is a specific devkit, and if yours differs you export ESP_MATTER_DEVICE_PATH for the correct board, and on a first flash it is recommended to run idf.py erase_flash to wipe the flash and start fresh, which clears stale state from earlier experiments. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
Peripheral components such as the LED and button drivers are selected automatically based on the chosen device, with the configuration in the device path's esp_matter_device.cmake file, so the same example source builds across boards with the hardware details factored out. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
A Matter device is useless until commissioned, and the developing guide names two commissioners. For development, the host-based chip-tool, an example Matter commissioner implementation from the connectedhomeip repository, is built during the install step and lands in the connectedhomeip out/host folder; it commissions and controls a device from your computer in interactive mode. For something closer to a consumer experience, Espressif's ESP RainMaker iOS and Android applications support commissioning and control of Matter devices. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
One platform footnote for Mac users: BLE commissioning on macOS requires installing the Bluetooth Central Matter Client Developer Mode Profile first, and it may need periodic reinstallation. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
The SDK also ships a device console for interacting with a running firmware directly, which pairs naturally with chip-tool during bring-up: commission from the host, then poke attributes and watch the device side respond. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
Everything a Matter device is, it declares through its data model. The developing guide's walkthrough starts by creating a Matter node as the root, then creates endpoints from standard device types: color_temperature_light, on_off_light, fan, door_lock, window_covering, pump, and more, all available through the esp_matter_endpoint.h header, each with a default configuration you can specialize. Multiple endpoints can be created on the same node, so one physical product can expose several logical devices. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
The standard device types carry sensible defaults with room to specialize. The window_covering configuration's constructor accepts an end product type, such as tilt-only interior blinds, overriding the default roller shade, and once instantiated that end product type cannot be modified. The pump example shows numeric configuration passed straight into its config constructor. These small structs are where a generic example becomes your product's declared behavior. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
The callback discipline is where firmware quality shows. When a Matter client changes the device, it updates attributes in the data model, and the SDK notifies your application through the attribute update callback. The documented pattern is PRE_UPDATE handling: the device driver acts on the new value first, and only if the driver update succeeds does the attribute value get written to the database. A separate identification callback handles the Identify cluster, which is how a device flashes an LED to identify itself from an app. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
Our assessment is that the real ESP32 decision in 2026 is rarely Matter versus Zigbee as an ideology; it is which transport your product needs, because Espressif now covers all of them with one vendor's toolchain and one consistent development flow. Wi-Fi devices skip Thread infrastructure entirely, Thread devices need a border router story, and the bridge solutions keep Zigbee fleets relevant. If you are weighing the alternatives, our ESP32 Zigbee guide covers that SDK's roles and network model, and our ESP32-C6 Thread border router post covers the infrastructure piece a Thread-based Matter product depends on.
Both Wi-Fi and 802.15.4 SoCs. The ESP32, ESP32-C, and ESP32-S series build Matter Wi-Fi devices, and the ESP32-H series, ESP32-C5, and ESP32-C6 build Matter Thread devices. A combination of an ESP32-H and a Wi-Fi SoC forms a Thread Border Router. Source: Introduction, Espressif's SDK for Matter Programming Guide
Not for a product application. The ESP Matter component, pulled in with idf.py add-dependency, is the lighter SDK-only setup. Clone the full repository when you need the examples and host tools like chip-tool, CHIP-cert, and ZAP for commissioning, certification, and data-model work. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
Two ways: the host-based chip-tool commissions and controls a device from your development machine, and Espressif's ESP RainMaker iOS and Android apps commission and control Matter devices from a phone. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
Yes, through bridges. Espressif provides Matter-Zigbee and Matter-BLE Mesh bridge solutions that bring non-Matter devices onto a Matter fabric without redesigning the end devices. Source: Introduction, Espressif's SDK for Matter Programming Guide
In the data model. You create a node, add endpoints built from standard device types like on_off_light, fan, or door_lock, and handle attribute updates through the PRE_UPDATE callback so your driver applies a change before the attribute database records it. Source: Developing with the SDK, Espressif's SDK for Matter Programming Guide
Ready to take the first step towards unlocking opportunities, realizing goals, and embracing innovation? We're here and eager to connect.