BLE mesh vs Thread vs Matter

BLE mesh, Thread, and Matter are three different layers of the connected-device stack, not three competing products. BLE mesh and Thread are network technologies that carry data between devices, while 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 routes over dedicated low-power radios, and Matter defines how devices from different brands understand each other.

Layer
BLE mesh
Thread
Matter
Phone-native meshOffline Protocol
ApplicationWhat the devices say to each other
Lighting and control models
None. IP applications sit above it
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
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
Whatever the network uses
BLE and WiFi Direct, already in every phone
On a phoneCan the phone be a node
Rarely. The mesh profile is uncommon on phones
No. The phone talks through a border router
As a controller only
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. A phone-native mesh covers all three on the radios a phone already has.

Side by side

AspectBLE meshThreadMatter
LayerNetwork, over Bluetooth LENetwork, over 802.15.4Application and interoperability
RadioBluetooth Low EnergyIEEE 802.15.4, sub-GHz and 2.4 GHzRuns over Thread, WiFi, or Ethernet
RoutingManaged flooding, multi-hopIPv6 mesh routing, self-healingDefined by the underlying network
Typical useSmart lighting, building controlLow-power home devices, sensors, locksCross-brand smart-home interoperability
On phonesBLE present, the mesh profile uncommonNo 802.15.4 radio, phone acts via a border routerPhone acts as a controller

The most common confusion is treating these three 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 dedicated radios with a border router bridging to the home network. Matter standardises device types and commissioning so a device from one brand works with a controller from another, over whichever network carries it.

Where a phone mesh fits

All three target fixed devices in a home or building. None is designed for the phones people carry coordinating in the field with no infrastructure. Thread needs 802.15.4 radios that phones lack, the Bluetooth Mesh profile is uncommon on phones, and Matter assumes a controller and a home network.

A phone-native mesh is a separate category. It uses the BLE and WiFi Direct radios already in every phone, 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 MB 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 three, since BLE mesh, Thread, 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.

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.