Matter vs Zigbee vs Z-Wave: which smart home protocol to build on

Short answer: build on Matter if you are starting fresh and want every major ecosystem to work; add Zigbee when you want the widest, cheapest device catalog and are willing to run a hub with that radio; choose Z-Wave when interference-free reliability matters more than price — locks, security sensors, and large installs. Most serious setups end up running two of the three on one hub.

The three protocols in one table

All three are local protocols — no cloud is required for a command to reach a device — but they differ in radio physics, in who certifies what, and in how many devices you can actually buy. Device counts below are from our dataset: Matter certifications from the CSA's compliance ledger, Zigbee support from the Zigbee2MQTT project, Z-Wave support from the Z-Wave JS project.

Matter Zigbee Z-Wave
Radio band Wi-Fi/Ethernet, or Thread on 2.4 GHz 2.4 GHz (shares band with Wi-Fi) Sub-GHz (908 MHz US / 868 MHz EU)
Mesh Thread devices mesh; Wi-Fi devices don't Mains-powered devices route Mains-powered devices route; Long Range mode is star
Power draw Wi-Fi high; Thread very low (battery-friendly) Very low — coin-cell sensors routine Very low — 800 series claims up to 10-year batteries
Hub requirement A controller; Thread devices also need a border router A coordinator (hub or USB dongle) A Z-Wave controller (hub or USB dongle)
Devices in our dataset 1,824 certified 5,405 supported 2,311 supported
Local control Yes, by design Yes Yes
Wi-Fi interference Thread shares 2.4 GHz Shares 2.4 GHz — channel planning helps None — different band

What actually separates them

Matter is an application standard, not a radio. It defines what a light or a lock is and runs over ordinary IP — Wi-Fi and Ethernet for powered devices, Thread for battery ones. Its selling point is ecosystem neutrality: one certified device works in Apple Home, Google Home, Alexa, and SmartThings, even all at once. Its weakness as of mid-2026 is maturity: controllers lag the spec, feature depth varies by ecosystem, and the certified catalog, while growing fast, is still a third the size of Zigbee's.

Zigbee is the volume market. A decade-plus head start means unmatched breadth — the 5,405 devices Zigbee2MQTT supports range from Hue and IKEA to sensors that cost less than a coffee. The flip side: interoperability is good but not guaranteed, because manufacturers bolt proprietary extensions onto the standard. A device may pair anywhere yet reveal its full features only on the maker's hub or on DIY platforms like Zigbee2MQTT and ZHA where the quirks are reverse-engineered.

Z-Wave is the reliability play. Its sub-GHz band penetrates walls better and never fights your Wi-Fi, and the Z-Wave Alliance's strict certification means cross-brand compatibility you can count on. It costs more per device and the catalog is smaller, but for locks and security sensors — where S2 authenticated pairing and battery life matter — it remains the professional's default. The 800-series chips and Z-Wave Long Range extend reach to detached buildings no 2.4 GHz mesh reliably covers.

When each one wins

You don't have to pick one

The protocols coexist happily because multi-radio hubs are now the norm: an Aeotec SmartThings hub or Hubitat C-8 runs Zigbee and Z-Wave side by side and speaks Matter; a Homey Pro or Home Assistant Green (with dongles) covers all three. The realistic strategy is to pick a hub with the radios you need and then buy each device in whichever protocol serves it best — our hub-choosing guide and the per-hub compatibility pages do that math from the dataset.

One useful boundary: a product having Wi-Fi and an app does not make it a Matter, Zigbee, or Z-Wave device. That distinction matters for large connected appliances such as EV chargers, where utility programs and the manufacturer's cloud are often more important than hub support. ChargerAtlas's guide to whether a smart EV charger is worth it separates those charger-specific benefits from smart-home interoperability.

Sources

← All guides