Matter vs Zigbee vs Z-Wave vs Thread, which should you use?

Matter, Zigbee, Z-Wave and Thread solve different parts of the same problem. Matter decides what a device is and how any brand’s controller talks to it. Thread decides how small devices move IP packets across a low-power mesh. Zigbee and Z-Wave each do both jobs, with their own network and their own device language, so a Zigbee or Z-Wave device needs a hub that speaks that stack.

That is why “Matter vs Thread” is not a real choice, while “Thread vs Zigbee” and “Zigbee vs Z-Wave” are. The table below puts all four, plus Bluetooth Mesh, side by side as their own bodies described them in October 2026.

Thread is only a network, Matter is only an application standard, and Zigbee and Z-Wave are both.

• Matter sits on top. The open-source Matter SDK describes it as an application layer built on IP, with a data model, an interaction model, security and message framing. The Connectivity Standards Alliance (CSA) lists Wi-Fi, Thread and Ethernet as the networks it runs on, plus Bluetooth LE for device setup.
• Thread sits underneath. OpenThread describes it as an IPv6 networking protocol for low-power devices on IEEE 802.15.4. The Thread Group lists several application layers that run on it, including Matter, OCF, KNX and DALI.
• Zigbee is a complete stack, from the mesh network up to the language devices use to work together, in the CSA’s own description.
• Z-Wave is also a complete stack: a sub-GHz mesh plus a library of command classes, such as door lock status, thermostat and metering, that the Z-Wave Alliance maintains so devices of different brands work together.

Matter vs Thread covers the first pair in depth, and Thread vs Zigbee covers why two stacks on the same radio still cannot join each other’s mesh.

All four need some box in the home, and the box does a different job for each.

• Thread needs a border router to reach any other network. OpenThread states that a Thread network requires one to connect to other networks. The Thread Group calls it a function, not a device, so it is often built into a smart speaker, streaming box or Wi-Fi router. What is a Thread border router? explains how to tell whether you already have one.
• Matter needs a controller, and the ecosystem decides whether that is a phone or a hub. The CSA says Matter-only devices need an internet-connected controller in the home to be controlled from away. Apple says Thread-enabled Matter accessories need a Thread-enabled home hub. Does Matter work without internet? compares the ecosystems.
• Zigbee needs a coordinator to form the network, and usually a hub or gateway to reach apps and IP networks. With Zigbee 4.0, the CSA says Zigbee Direct is built in, so phones can onboard and control devices over Bluetooth LE without a hub.
• Z-Wave needs a controller. The Z-Wave Alliance’s overview says both Z-Wave and Z-Wave Long Range work through a gateway or hub.
• Bluetooth Mesh needs none. The Bluetooth SIG says Bluetooth Mesh control systems do not require centralised controllers.

Zigbee and Z-Wave devices work with Matter through a bridge, and not natively. The CSA’s Matter FAQ says Matter supports bridges that let devices using other protocols, such as Zigbee or Z-Wave, take part in a Matter ecosystem, and that there is no native interoperability between Matter and Zigbee devices.

A bridge is a hub that speaks Zigbee or Z-Wave on one side and presents each device to Matter controllers on the other. The Zigbee or Z-Wave device itself does not change and does not become a Matter device. If the bridge goes offline, Matter controllers lose those devices.

In practice:

1. Check whether your Zigbee or Z-Wave hub can act as a Matter bridge, in the hub maker’s own documentation.
2. Add the bridge to your Matter controller the way you add any Matter device, with its setup code.
3. Confirm that each device type you need is exposed. A bridge can only expose device types that Matter defines.

Z-Wave Long Range reaches furthest by the figures the standards bodies publish, and every option offers multi-year battery devices.

• Z-Wave: the Z-Wave Alliance gives about 100 metres per hop for mesh Z-Wave. For Z-Wave Long Range it cites a proven 1 mile (1.6 km) line of sight, up to 1.5 miles at full power, up to 4,000 nodes in a star around the hub, and up to 10 years on a single coin cell. Mesh Z-Wave supports up to 232 nodes.
• Zigbee: the CSA gives 10 to 100 metres at 2.4 GHz, and 1 km or more with sub-GHz Zigbee, now branded Suzi.
• Thread: OpenThread says low-power Thread devices can sleep and run on batteries for years. On 2.4 GHz its range per hop is in the same class as 2.4 GHz Zigbee and depends on the hardware.
• Bluetooth Mesh: Low Power nodes save energy by letting Friend nodes hold messages for them.
• Matter has no radio of its own, so its range and battery life are those of Thread, Wi-Fi or Ethernet underneath.

Every mesh extends coverage by relaying, so a home with mains-powered routers or repeaters spread through it reaches further than any single-hop figure. Z-Wave Long Range is the exception, because it is a star, not a mesh.

Matter is not replacing Zigbee and Z-Wave as of October 2026. All three are still being developed, and Matter brings the other two in through bridges.

• The CSA answers in its own FAQ that Matter and Zigbee are different protocols, giving product makers different options. It announced Zigbee 4.0 in November 2025, backward compatible with Zigbee 3.0, together with Suzi for sub-GHz Zigbee.
• The Z-Wave Alliance publishes a 2026A specification package, released a Long Range specification for Europe in February 2024, and certifies backward and forward compatibility.
• Matter keeps adding device types, such as cameras and closures in Matter 1.5 in November 2025.

Matter’s answer to a home full of Zigbee or Z-Wave devices is the bridge, not a replacement. The choice that has changed is the one a maker faces for a new device, covered next.

Choose by who has to control the device and how it is powered.

• Matter over Thread for battery devices sold to consumers, such as sensors, locks and buttons, that should work with every major ecosystem. The Thread Group suggests Thread for low-bandwidth battery devices.
• Matter over Wi-Fi for mains-powered devices that move more data, such as cameras and appliances. Matter over Ethernet for fixed bridges and hubs.
• Zigbee for products that must join existing Zigbee hubs, need sub-GHz range, or should be controllable from a phone over Bluetooth LE with Zigbee Direct.
• Z-Wave for products sold into Z-Wave hubs and professional installers, or that need Z-Wave Long Range’s distance.
• Bluetooth Mesh for commercial lighting and building control commissioned from phones, with no hub.

Budget for certification either way. As of October 2026, the lowest CSA tier that certifies is Adopter at $7,500 a year, with certification from $2,000 to $3,000 per product. The Z-Wave Alliance lists Contributor at $7,500 a year as its lowest tier that certifies. Bluetooth SIG Adopter membership is free, and every Bluetooth product must be qualified. The Thread Group runs its own membership and certification, and Apple notes that calling a border router “Thread” is subject to the Thread Group’s trademark and certification policies.

None of the four connects the people, phones, apps, gateways and agents that work around the devices. Offline Protocol is an SDK for that layer: apps discover each other, verify each other’s identity, and share encrypted messages, documents and service calls over Bluetooth LE, the local network or a relay. It is not a Matter controller, it does not speak Matter, Thread, Zigbee or Z-Wave, and it does not replace them. A site can run a smart home or building standard for its devices and Offline Protocol for the apps beside them, as How do devices coordinate locally beyond the smart home? and Offline Protocol vs Matter describe.