Key points
- Both form self-healing, low-power meshes on IEEE 802.15.4 radios, and both work locally with no internet connection.
- Thread carries IPv6. Every device has an IP address, a border router connects the mesh to Wi-Fi or Ethernet, and the application layer comes from elsewhere, usually Matter.
- Zigbee is a full stack, including its own application language. It reaches IP networks through a hub or gateway, and since Zigbee 4.0 phones can onboard and control devices over Bluetooth LE with Zigbee Direct.
- Zigbee also runs on sub-GHz bands, now branded Suzi, for longer range. The Thread Group describes Thread on the 2.4 GHz spectrum.
Thread and Zigbee interoperability
Thread and Zigbee devices cannot join each other’s networks because the radio is the only part they share. OpenThread describes Thread as an IPv6 networking protocol on IEEE 802.15.4, made up of 6LoWPAN, MAC security, Mesh Link Establishment and mesh routing. The Connectivity Standards Alliance (CSA) describes Zigbee as a complete stack, from the mesh network to the universal language that lets smart objects work together. Two devices on the same 802.15.4 channel with different network layers cannot form one mesh.
The same split shows up with Matter. The CSA says there is no native interoperability between Matter and Zigbee devices, and that Matter supports bridges so Zigbee devices can take part in a Matter ecosystem. See what a Matter bridge is for how that works and its limits.
Thread vs Zigbee comparison table
| Thread | Zigbee | |
|---|---|---|
| Governed by | Thread Group | Connectivity Standards Alliance |
| What it defines | IPv6 mesh network | Mesh network and application layer |
| Radio | IEEE 802.15.4 at 2.4 GHz | 2.4 GHz worldwide; sub-GHz (Suzi) in Europe and North America |
| IP | Native IPv6 | Not IP; bridged by hubs, gateways or controllers |
| Reaching other networks | Border router, a function that can live in many devices | Hub, gateway or controller |
| Phones | Over IP through a border router; a phone can commission devices | Zigbee Direct over Bluetooth LE |
| Scale | Up to 32 routers and 511 end devices per router | Hundreds of devices per network; coordinators can be linked |
| Security | All devices authenticated, all traffic encrypted | AES-128 encryption and authentication, certificates, elliptic-curve cryptography |
| Works without internet | Yes | Yes |
| Latest release | Thread 1.4 | Zigbee 4.0 (announced November 2025) |
Thread border routers and Zigbee hubs
Thread connects to other networks with IP. OpenThread says a Thread network requires a border router to connect to other networks, and the border router routes IP traffic both ways and bridges service discovery. The Thread Group stresses that a border router is a function, not a device, so smart speakers, hubs and Wi-Fi routers often include one, and a network can have several.
Zigbee connects to them with translation. The CSA describes the bridging capability as built into hubs, gateways and controllers, which turn Zigbee messages into something an IP network or app can use. That hub is usually where Zigbee devices are paired and automations run.
Phone access to Thread and Zigbee devices
Neither standard expects the phone to be a mesh node with an 802.15.4 radio.
- Thread: the Thread Group says Thread does not need to be in your phone, because the phone and the Thread devices are on the same IP network once a border router links them. OpenThread adds that a phone can act as the external commissioner that joins a new device to the network.
- Zigbee: the CSA’s Zigbee Direct feature lets Bluetooth LE devices such as phones onboard and control Zigbee devices directly. With Zigbee 4.0, the CSA says Zigbee Direct is built in and users can onboard and control devices over Bluetooth LE without a hub.
Thread and Zigbee network size limits
OpenThread’s primer gives Thread’s limits: one Leader, up to 32 routers, and up to 511 end devices per router. The CSA’s Zigbee FAQ describes networks of hundreds of nodes, with multiple network coordinators linked together to support very large networks, and its Zigbee overview calls the mesh scalable to thousands of nodes. In both, mains-powered devices relay and battery devices sleep.
Thread 1.4 and Zigbee 4.0 changes
Thread 1.4 focuses on homes with border routers from several makers. The Thread Group lists credential sharing protected by DTLS, Thread over infrastructure, network diagnostics, commissioning at scale and direct cloud connectivity, and says Thread 1.4 is fully backward compatible.
Zigbee 4.0, announced in November 2025, is backward compatible with Zigbee 3.0 and Smart Energy. The CSA lists built-in Zigbee Direct, security updates including cryptographic agility, and sleepy-to-sleepy communication using Coordinated Sample Listening for low-power exchanges between devices. The same announcement introduced Suzi, the brand for sub-GHz Zigbee mesh networking, with certification planned to open in the first half of 2026.
Choosing Thread or Zigbee for a new product
- Choose Thread if the product will be a Matter device, if it should be reachable over IP from phones and controllers through any border router, or if you want the open-source OpenThread stack, which Google publishes under the BSD 3-Clause license.
- Choose Zigbee if the product must join existing Zigbee installations or a Zigbee hub’s ecosystem, if you need sub-GHz range, or if phone control over Bluetooth LE through Zigbee Direct matters more than IP.
- Use both in a hub or bridge that has to serve both kinds of devices.
For sub-GHz reach outside Zigbee, Z-Wave is the other established smart home mesh, with a hub-controlled network and a Long Range mode.
If Z-Wave and Matter are also on the list, Matter vs Zigbee vs Z-Wave vs Thread compares all four, with Bluetooth Mesh alongside.
Offline Protocol alongside Thread and Zigbee
Thread and Zigbee connect fixed, low-power devices inside a home or building. Offline Protocol works at a different level, as an SDK inside apps on phones, computers and gateways that lets them discover each other, verify identity and exchange encrypted messages, shared documents and service calls over Bluetooth LE, the local network or a relay. It uses neither radio. On microcontrollers, its no_std leaf component runs beside whatever radio stack the firmware already uses, which supplies the transport.