BLE mesh vs Thread vs Matter vs Zigbee

BLE mesh, Thread, Zigbee, and Matter work at different layers of the connected-device stack, so they are not four competing products. BLE mesh and Thread are network technologies that carry data between devices, Zigbee is a full stack from the mesh up to a shared device language, and Matter is an application-layer interoperability standard that runs over networks such as Thread and WiFi. BLE mesh floods messages over Bluetooth Low Energy, Thread and Zigbee route over IEEE 802.15.4 radios, and Matter defines how devices from different brands understand each other.

Layer
BLE mesh
Thread
Zigbee
Matter
Phone-native meshOffline Protocol
ApplicationWhat the devices say to each other
Lighting and control models
None. IP applications sit above it
Zigbee Cluster Library, a shared set of device commands
Device types, commissioning, cross-brand control
Your app. Messaging, identity, discovery, shared documents
NetworkHow a message finds the right device
Managed flooding, multi-hop
IPv6 mesh routing, self-healing
Mesh routing through always-on routers, self-healing
None. Runs over Thread or WiFi
Routed multi-hop, up to 8 hops, failover across radios
RadioWhat carries the bits
Bluetooth Low Energy
IEEE 802.15.4 at 2.4 GHz
IEEE 802.15.4 at 2.4 GHz and in sub-GHz bands
Whatever the network uses
BLE and direct Wi-Fi, already in phones
On a phoneCan the phone be a node
Through a proxy node over GATT. The mesh stack is uncommon on phones
No. The phone talks through a border router
No. Through a hub, or Zigbee Direct over Bluetooth LE
As a commissioner and controller
Yes, as a full relaying node

Does the work at this layerPresent, but limitedRelies on another layer Matter lives at the top and borrows a network. BLE mesh and Thread live in the middle and bottom, and Zigbee spans all three layers on its own radio. A phone-native mesh covers all three on the radios a phone already has.

How do BLE mesh, Thread, Matter and Zigbee compare?

They differ first by layer. BLE mesh, Thread and Zigbee move data between devices, and Matter decides what that data means, so Matter runs over Thread or WiFi instead of competing with them.

AspectBLE meshThreadZigbeeMatter
LayerNetwork, over Bluetooth LENetwork, over 802.15.4Full stack, network to application, over 802.15.4Application and interoperability
RadioBluetooth Low EnergyIEEE 802.15.4 at 2.4 GHzIEEE 802.15.4 at 2.4 GHz and in sub-GHz bandsRuns over Thread, WiFi, or Ethernet
RoutingManaged flooding, multi-hopIPv6 mesh routing, self-healingMesh routing through always-on routers, self-healingDefined by the underlying network
Hub or routerNo central controllerA border router to reach WiFi, phones, and the internetA coordinator forms each networkA controller to commission and run devices
Typical useSmart lighting, building controlLow-power home devices, sensors, locksSmart home devices, smart meters, commercial buildingsCross-brand smart-home interoperability
On phonesThrough a proxy node over GATT; the mesh stack is uncommon on phonesNo 802.15.4 radio; the phone reaches devices over IP through a border routerNo 802.15.4 radio; through a hub, or Zigbee Direct over Bluetooth LEThe phone commissions and controls devices

The most common confusion is treating these as alternatives. You can run Matter over Thread, but you cannot swap Matter for Thread, because they do different jobs. BLE mesh spreads messages by managed flooding and is common in smart lighting. Thread forms an IPv6 mesh over 2.4 GHz radios with a border router bridging to the home network. Zigbee is the closest like-for-like rival to Thread, since both use IEEE 802.15.4 radios, but it carries its own device language where Thread carries IPv6 for an application layer such as Matter. Matter standardises device types and commissioning so a device from one brand works with a controller from another, over whichever network carries it, and its bridges bring Zigbee devices along.

Z-Wave is a separate smart-home mesh on its own sub-GHz radio, at 908.42 and 916 MHz in the United States according to the Z-Wave Alliance, and Matter reaches Z-Wave devices through bridges too. For the pairs in more depth, see Matter vs Thread, Thread vs Zigbee, and Zigbee vs Bluetooth Mesh.

Sources, checked 21 October 2026: Thread Group, Thread benefits; Thread Group FAQ; OpenThread, node roles; CSA, Zigbee; CSA, Zigbee FAQ; CSA, Zigbee Direct; CSA, Zigbee 4.0; Silicon Labs, Zigbee node types; CSA, Matter FAQ; Apple, Matter support in iOS; Bluetooth SIG, Mesh; Bluetooth SIG, Mesh technology overview; Z-Wave Alliance.

Where does a phone mesh fit?

A phone mesh fits where the devices are the phones people carry, coordinating with each other in the field. All four standards above target fixed devices in a home or building. Thread and Zigbee need 802.15.4 radios that phones lack, the Bluetooth Mesh stack is uncommon on phones, and Matter assumes a controller and a home network.

A phone-native mesh is a separate category. It uses the Bluetooth LE and Wi-Fi radios already in phones, WiFi Direct on Android and peer-to-peer Wi-Fi on iPhone, forms a routed multi-hop mesh with no border router, and works with no internet, which suits field coordination, events, and disaster response rather than home automation.

Offline Protocol is the phone-native option. Its mesh combines BLE, WiFi Direct, and the internet with automatic failover, relays up to 8 hops, and moves messages and files up to 100 MiB on ordinary iOS and Android phones with no hub. Sessions use MLS and peers authenticate with Ed25519 identities. See Bluetooth LE mesh for the profile itself, or the transport in depth.

Frequently asked questions

Is Matter a replacement for Thread?

No. Matter is an application-layer interoperability standard and Thread is a network protocol. Matter runs over networks such as Thread or WiFi, so they work together rather than replacing each other.

Which is best for offline field coordination among phones?

None of the four, since BLE mesh, Thread, Zigbee, and Matter all target fixed home and building devices. A phone-native mesh such as Offline Protocol, which uses the phone’s own BLE and WiFi Direct radios and works with no infrastructure, fits that case.

Is Zigbee being replaced by Matter?

No. The Connectivity Standards Alliance, which maintains both, calls them different technologies that will likely co-exist in the same home, and Matter includes specifications for bridges that bring Zigbee devices into a Matter system. The Alliance announced Zigbee 4.0 in November 2025, fully backward compatible with Zigbee 3.0.

Do I need a hub for Thread or Zigbee?

For Thread, you need a border router to connect the Thread network to WiFi, your phone, or the internet; the Thread Group calls it a function rather than a device, and some WiFi access points have it built in. For Zigbee, a coordinator forms each network, and Zigbee Direct lets a phone reach devices over Bluetooth LE, which the Alliance says can reduce the need for additional hubs.

Can a phone join Thread or Bluetooth Mesh directly?

A phone cannot join Thread as a mesh node because it lacks an 802.15.4 radio; it acts through a border router. The Bluetooth Mesh profile is uncommon on phones. Phones do run app-level BLE and WiFi Direct meshes, which is how Offline Protocol works.

A mesh on the phones you already have. 350,000+ devices, 140+ countries.