Key points
- Matter over Wi-Fi joins the Wi-Fi network you already have. It needs no border router and has far more bandwidth, but Wi-Fi radios use more power.
- Matter over Thread joins a low-power IPv6 mesh on IEEE 802.15.4 radios at 2.4 GHz. It needs a Thread border router, often built into a smart speaker, streaming box or router, and it is designed for battery devices.
- Matter is the same on both: the same device types, the same setup codes, the same local control and the same apps.
Wi-Fi and Thread as Matter networks
Matter over Wi-Fi and Matter over Thread differ in the network under Matter, not in Matter itself. The Connectivity Standards Alliance (CSA) says Matter uses Wi-Fi, Thread and Ethernet for connecting devices and Bluetooth LE for setup. Home Assistant puts it plainly: Matter has no radio protocol of its own and runs on top of the existing network.
A Matter over Wi-Fi device connects to your Wi-Fi access point like a laptop does. A Matter over Thread device connects to a Thread mesh, where mains-powered devices relay for each other, and a Thread border router links that mesh to your Wi-Fi or Ethernet network. The Thread Group calls Thread complementary to Wi-Fi: 802.15.4 was designed for low-power, low-bandwidth control, while Wi-Fi is designed for high-bandwidth data such as video and audio. For more on how the two standards divide the work, see Matter vs Thread.
Matter over Wi-Fi vs Thread comparison
Thread wins on power and on resilience through its mesh; Wi-Fi wins on bandwidth and on needing nothing extra.
| Matter over Wi-Fi | Matter over Thread | |
|---|---|---|
| Network | Your Wi-Fi access points | Thread mesh on IEEE 802.15.4, 2.4 GHz |
| Extra hardware | None beyond the Wi-Fi network | A Thread border router near the devices |
| Bandwidth | Orders of magnitude more than Thread (Google) | 250 kbps at the radio, about 125 kbps in practice (Google) |
| Power | Higher; suits mains power | Low; battery devices can sleep and last years (OpenThread) |
| Topology | Star around each access point | Self-healing mesh with no single point of failure (Thread Group) |
| Scale | Limited by your access points; Matter 1.4.2 network infrastructure must support 100 associations | Up to 32 routers and 511 end devices per router (OpenThread) |
| Setup | Bluetooth LE, or Wi-Fi only since Matter 1.4.2; the commissioner provides the Wi-Fi network | Bluetooth LE; the commissioner provides the Thread network |
| Best for | Cameras, appliances, devices that move more data | Sensors, locks, buttons, battery devices |
Thread border router for Matter
Matter over Thread needs a border router. A Thread network cannot reach any other network without a border router, and Home Assistant says that to add a Matter device based on Thread you need a Thread border router near the device. The border router configures IPv6 routes between Thread and your home network, and Google’s primer explains that it also publishes discovery records on behalf of Thread devices so controllers on Wi-Fi can find them.
You may already own one:
- Apple says Thread accessories need a Thread-enabled home hub such as Apple TV 4K, HomePod (2nd generation) or HomePod mini, or a compatible third-party Thread border router.
- Google lists the Google Home Speaker (2026), Nest Hub (2nd gen), Nest Hub Max, Nest Wifi Pro and Google TV Streamer (4K) as hubs that support Thread, and says Wi-Fi-only hubs are not Thread border routers.
- Amazon lists several Echo and eero models with Thread border routers, among them Echo Hub, Echo Show 8 (3rd gen) and eero 6 and 7 models.
Matter over Wi-Fi needs no border router, but it still needs a controller. Google, for example, requires a Matter-enabled hub on your home network to add Matter devices and control them locally, whichever network they use.
The Thread Group adds that border routers are a function, not a device, and that adding more border routers to the same network makes the mesh stronger, farther reaching and more reliable. Matter 1.4 (November 2024) defined home routers and access points that combine a Wi-Fi access point and a Thread border router with secure storage for Thread credentials, so new devices join one existing Thread network instead of starting separate ones.
Wi-Fi and Thread speed and latency
Matter over Wi-Fi is faster than Matter over Thread for data, by a wide margin. For everyday control, both are responsive. Google’s Matter primer gives Thread’s bandwidth as 250 kbps at the IEEE 802.15.4 radio and about 125 kbps typical once retransmissions and overhead are counted, which it calls orders of magnitude less than Wi-Fi. The same page says Thread pings on a local network typically take under a few tens of milliseconds round trip, and the Thread Group describes Thread as low latency.
Turning on a light or reading a sensor needs very little data, so Thread’s bandwidth is rarely the limit. Streaming video is a different job: Matter 1.5 (November 2025) added cameras with live video and audio over WebRTC, and full support for TCP transport for high-bandwidth devices, which is Wi-Fi or Ethernet territory.
Best network for battery-powered Matter devices
Thread is the better network for battery-powered Matter devices. OpenThread says low-power Thread devices can sleep and operate on battery power for years, and the Thread Group says the 802.15.4 radio was designed for low-power, low-bandwidth control applications. A sleepy Thread end device keeps its radio off and wakes now and then to collect messages from its parent.
That makes Thread the natural fit for door and window sensors, locks, buttons and other battery devices. The Thread Group describes Wi-Fi as designed for high-bandwidth data, so Wi-Fi suits devices on mains power: plugs, switches, appliances and cameras.
Thread and Wi-Fi reliability
Matter over Thread is built to tolerate failures differently from Matter over Wi-Fi. The Thread Group says Thread networks have no single point of failure and can heal themselves, rerouting through other devices if one fails. OpenThread’s primer explains that a router keeps its radio on at all times while a sleepy end device does not, so the routes through a Thread mesh run through always-on devices, usually ones on mains power.
A Wi-Fi device depends on reaching an access point. In a home with good Wi-Fi coverage that is usually fine; at the edge of coverage, a Wi-Fi device has no neighbour to relay through. Thread’s weak point is the border router: without one, Thread devices cannot reach controllers on Wi-Fi, which is why the Thread Group recommends more than one.
Both can share the 2.4 GHz band. The Thread Group says Thread uses the 2.4 GHz spectrum, Home Assistant notes that Matter devices often use 2.4 GHz Wi-Fi, and OpenThread says Thread uses spread-spectrum techniques to provide immunity to interference.
Matter network settings
Matter needs IPv6 on your local network and devices on the same network as their controllers, whichever radio they use:
- IPv6 on. Google warns that without IPv6 on your home network, setup may appear to succeed but control eventually fails. Home Assistant says IPv6 multicast traffic must flow freely to the host, and that no IPv6 internet connection or DHCPv6 server is required.
- Leave multicast alone. Home Assistant warns that a router or access point setting that “optimises” multicast traffic can harm Matter’s discovery traffic.
- Primary network, not guest. The CSA says Matter devices are designed to talk directly to each other and to controllers, and that a guest network blocks this.
Choosing Wi-Fi or Thread per device
Choose by power and data, and buy the network you are missing last:
- Battery devices that send little data (contact and motion sensors, locks, buttons): Thread, if you have or will add a Thread border router.
- Devices that move video or audio (cameras, doorbells with video): Wi-Fi or Ethernet.
- Mains-powered control devices (plugs, switches, bulbs): either. Thread versions also strengthen the Thread mesh; Wi-Fi versions need no border router.
- Fixed equipment with a cable run (hubs, bridges): Ethernet.
If a product comes in both versions, Thread is the better long-term choice in a home that already has a Thread border router, and Wi-Fi is simpler in one that does not.
Offline Protocol and transport-independent apps
Matter shows a useful split: one application layer that does not care which network carries it. Offline Protocol makes the same split for apps on phones, computers and gateways, not smart home devices. Its engine carries messages, shared documents and service calls over Bluetooth LE, a phone Wi-Fi peer stream (Wi-Fi Direct on Android, Network framework on iOS), an internet relay, Reticulum and Nostr, and picks among them as conditions change. It does not run over Thread, is not a Matter implementation and does not control Matter devices.