Matter vs Zigbee: which smart home standard should you choose?
Matter is an application layer over IP on Wi-Fi, Thread and Ethernet; Zigbee is a full mesh stack on 802.15.4. How they differ, coexist and when to pick each.
Photo: Jaye Haych / Unsplash
After reading this article you will be able to:
- Explain why Matter is an application layer over IP while Zigbee is a complete radio stack
- Compare setup, local control, multi-admin and device choice for the two standards
- Choose between Matter devices, Zigbee devices or a bridged mix for a home or a product
On this page
Matter and Zigbee are not two versions of the same thing. Matter is an application layer: a shared language for lights, locks, sensors and thermostats that runs over IP on Wi-Fi, Thread or Ethernet. Zigbee is a complete stack, from the radio up to its own application layer, that needs a hub to reach the rest of the home network. Both are maintained by the Connectivity Standards Alliance, and a single hub often runs both.
The short answer. Buy Matter devices when you use one or more of the big ecosystems (Apple Home, Google Home, Amazon Alexa, SmartThings) and want any of them to control the same device without a vendor bridge: plugs and lights over Wi-Fi, battery sensors over Thread. Stay with Zigbee, or start with it, when you run a local hub such as Home Assistant with a Zigbee radio, want the widest and cheapest choice of sensors, buttons and bulbs, or are extending a Zigbee installation that already works. Mixing the two through a bridge is normal and often the best answer.
| Matter | Zigbee | |
|---|---|---|
| What it is | Application layer and security over IPv6 | Full stack: radio, network and application layers |
| Network underneath | Wi-Fi, Thread, Ethernet; Bluetooth LE only for setup | IEEE 802.15.4 mesh, mostly at 2.4 GHz |
| What you need | Wi-Fi router; a Thread border router for Thread devices | A coordinator (hub or USB radio) |
| Several apps at once | Yes, multi-admin: one device, several ecosystems | Through the hub, or a bridge to Matter |
| Local control | Yes, on the home network | Yes, inside the hub |
| Device choice | Growing, some categories still thin | Large and mature |
How are Matter and Zigbee built differently?
Zigbee defines everything from the air interface up. Its physical and MAC layers are IEEE 802.15.4, it has its own mesh network layer with routers and sleepy end devices, and the Zigbee Cluster Library describes what an on/off light or a temperature sensor can do. A Zigbee device does not speak IP, so a coordinator, usually built into a hub, translates between the mesh and everything else.
Matter starts higher. The Matter 1.0 announcement in October 2022 described it as running over Ethernet, Wi-Fi and Thread, with Bluetooth Low Energy used only for commissioning. Every Matter device is an IPv6 node. A Wi-Fi plug sits on the home network directly; a Thread sensor sits on a low-power 802.15.4 mesh that a border router connects to the rest of the network. The data model borrows Zigbee’s idea of clusters, so the two feel related to a developer, but the transport is different.
That difference explains most of the practical trade-offs. Zigbee has one coordinator per network and one place where the smarts live. Matter devices can be reached by any authorized controller on the network.
How do setup and daily control compare?
Adding a Zigbee device means putting the hub into pairing mode and resetting or powering the device until it joins. The device belongs to that hub. If you want it in another app, the hub has to expose it through an integration or a bridge.
Matter setup, called commissioning, uses the QR code or numeric code on the device. The controller checks that the device is a certified product, gives it credentials for its fabric and hands it Wi-Fi or Thread network details. After that, multi-admin lets you add the same device to a second or third ecosystem without resetting it. Matter 1.6, released in June 2026, extends this with Joint Fabric, in which several controllers co-administer one shared Matter network, and with commissioning over NFC even before a device is fully powered on.
Multi-admin shares control of the device, not the setup around it. Rooms, scenes and automations still live separately in each app.
Which works without the cloud?
Both can run locally. A Zigbee network is local by design: the hub talks to the devices over the mesh, and automations on a hub such as Home Assistant keep working when the internet is down. Whether a commercial Zigbee hub keeps working offline depends on its maker.
Matter was designed for local operation too. Controllers talk to devices on the home network, without a round trip to a vendor cloud. Remote access, voice assistants and some automations still go through each ecosystem’s servers, and a device maker can require its own account for firmware updates or extra features. Neither standard guarantees that a given product works offline; both make it possible.
How do device choice and maturity compare?
Zigbee has a long head start. The CSA says more than a billion Zigbee devices are deployed, and Zigbee 3.0, ratified in December 2015, unified the earlier application profiles so that certified devices generally join any Zigbee 3.0 hub. Small door sensors, buttons and motion sensors are abundant and inexpensive. Some cheap devices still use manufacturer-specific extensions that only certain hubs understand.
Matter’s catalog is younger and grows with each release. Lighting, plugs, locks, thermostats, blinds and sensors arrived early; Matter 1.5 in November 2025 added cameras, a unified model for closures and energy tariff data. A Matter product can still expose only part of what its own app offers, because vendor-specific features have no standard cluster. Check that the features you care about are in the Matter data model before buying for them.
Is Matter replacing Zigbee?
Not on the evidence of the CSA’s own work. The Alliance announced Zigbee 4.0 in November 2025, with security updates, batch commissioning and support for European 800 MHz and North American 900 MHz bands, fully backward compatible with Zigbee 3.0. The sub-GHz variant is branded Suzi, and Suzi product certification opened in September 2026.
The direction for new consumer products is still Matter, often over Thread, because the large ecosystems certify and promote it. In practice the two meet in bridges: a Matter bridge exposes each Zigbee device behind a hub as a Matter endpoint, so Apple, Google or Amazon controllers see it as if it were native. Security stops at the bridge. The Zigbee leg keeps Zigbee’s own protection, and the bridge becomes a device you depend on.
When should you choose each?
Choose Matter when:
- You use more than one ecosystem at home, or sell into homes that do.
- You want devices that join the home network without a vendor hub (Wi-Fi), or through a Thread border router, which some smart speakers and streaming boxes already include.
- You build a product and want one certification that covers all the major controllers.
Choose Zigbee when:
- You run a local hub and want many low-cost battery sensors and buttons.
- You need a device type that Matter does not cover yet, or covers only partly.
- You are extending an existing Zigbee mesh with plenty of mains-powered routers.
Choose both when you already have Zigbee devices and want them in a Matter ecosystem: keep the Zigbee mesh, and let the hub bridge it.
Where to go next
- Matter explained covers commissioning, fabrics, multi-admin and bridges in detail.
- Zigbee explained explains the mesh roles, the cluster library and Zigbee security.
- Thread explained describes the low-power IP mesh most battery-powered Matter devices use.
- The smart home, explained puts both standards in the context of ecosystems, hubs and privacy.
- Matter over Thread vs Matter over Wi-Fi helps you decide which network your devices should use.
- ZHA vs Zigbee2MQTT compares the two ways to run Zigbee with Home Assistant.
- Zigbee vs Z-Wave compares frequencies, mesh, certification and Matter bridges.
Topics: Matter, Zigbee, smart home, Thread, comparison