Matter, Thread, Zigbee and Wi-Fi: Which One You Need
Matter is not a radio. It is a language, and it is spoken over one of two radios —
Thread or Wi-Fi. Almost every confusing thing about buying smart home gear in 2026 comes from
that one fact being left out of the box copy. “Matter” on a package tells you how a device talks, not
how it connects, and those are separate purchases of your attention.
Thread and Zigbee are radios. Wi-Fi is a radio. Matter sits on top. Once you can sort any product
into “which radio, which language”, the compatibility questions answer themselves.
What each name actually is
| Name | What it is | Needs a hub? | Best for |
|---|---|---|---|
| Matter | Application layer — a shared language | Yes, a Matter controller | Cross-ecosystem control |
| Thread | Low-power mesh radio (802.15.4, IPv6) | Yes — a Thread border router | Battery sensors, locks, buttons |
| Zigbee | Low-power mesh radio (802.15.4) | Yes, a Zigbee hub | Same jobs, far bigger device catalogue |
| Z-Wave | Low-power mesh radio, sub-GHz | Yes, a Z-Wave hub | Range, and avoiding 2.4GHz congestion |
| Wi-Fi | High-bandwidth radio you already have | No | Cameras, speakers, anything mains-powered |
| Bluetooth / BLE | Short-range radio | Phone, usually | Setup and pairing, rarely operation |
The distinction that explains everything
Thread and Zigbee use the same underlying radio standard, 802.15.4. The difference is what
runs on top: Thread devices carry IPv6 addresses, the same kind of address your router hands out, so
they are directly addressable on your network. Zigbee devices are not — they speak a proprietary
protocol and need a hub to translate.
That is the whole technical case for Thread, and it is a real one. It removes a translation layer,
which removes a class of failure and a vendor dependency. It also explains why “Matter over Thread” is
the combination people talk about: an IP-addressable radio underneath a standard language on top means
no proprietary anything in the chain.
What it does not do is make Thread automatically better to buy today. A translation layer that
works is not a problem you have.
You may own a Matter hub and still have no Thread network
Thread requires a border router — a mains-powered device that bridges the Thread mesh
to your home network. Most Thread border routers are also Matter controllers, but plenty of Matter
controllers are not border routers. This trips up more people than any other part of the
setup.
In practice the border router is usually something you already bought for another reason: an Apple
TV 4K, a Nest Hub, certain Wi-Fi routers. If you own none of those and you buy a Matter-over-Thread
sensor, it will not connect to anything, and nothing in the packaging will have told you why.
The check before buying any Thread device is therefore one question: what in my house is the
border router? If you cannot name it, buy the Wi-Fi version of the device instead, or buy the
border router first.
Zigbee and Z-Wave are not obsolete, and the catalogue proves it
Thread’s device selection still trails Zigbee and Wi-Fi substantially in 2026. If you want
a specific, unusual sensor, there is a good chance it exists in Zigbee and does not exist in
Thread.
Zigbee’s advantage is fifteen years of accumulated hardware. Z-Wave’s is the radio band: it runs
below 1GHz rather than at 2.4GHz, so it does not compete with Wi-Fi, microwaves and Bluetooth for
spectrum, and it tends to hold up better in dense apartment buildings.
Matter does not retire either of them, and it does not automatically make your existing Zigbee gear
work with a new ecosystem. Existing devices need a bridge — a hub that presents them to Matter
— and whether your particular hub does that depends on the manufacturer, not the standard. If
you already run a working Zigbee or Z-Wave setup, “everything is Matter now” is not a reason to
replace it.
Why a mesh gets better or worse as you add devices
In a Thread or Zigbee mesh, not every device relays traffic. Mains-powered devices act as
routers and pass messages along for their neighbours; battery-powered devices are end devices and do
not relay, because staying awake to listen is exactly what would drain the cell.
This has a consequence almost nobody is told at the point of sale. Add a mains-powered device
— a plug, a switch, a bulb — and your mesh gets more reliable, because you have added a
relay. Add another battery sensor and the mesh gets slightly worse, because you have added a
dependent with nothing given back.
So the common experience of “it worked fine with three devices and became flaky at fifteen” is
usually not interference or a faulty hub. It is a network where the battery-powered devices
outnumbered the relays, leaving sensors at the edges of the house several hops from anything that
could carry their traffic.
The practical fix costs nothing extra if you sequence it right: install the mains-powered
devices first, and spread them out. A smart plug in a far bedroom is doing two jobs —
switching a lamp, and giving the door sensor down the hall something to talk to. It is also why the
first battery sensor you add at the edge of coverage is the one most likely to keep dropping off, and
why moving a plug can fix a sensor that seemed unrelated to it.
What Matter covers in 2026, and what it still does not
The specification and the products on shelves are different timelines, and the gap is
usually one to two product cycles. A standard finalising this year shows up in things you can
buy considerably later.
The original specification covered the obvious categories: bulbs, switches, plugs, locks, sensors,
blinds, thermostats, HVAC controllers, garage door controllers and media devices. Later revisions
added energy management, water leak sensors and better robot vacuum support. Video cameras
were the conspicuous omission and were slated to arrive with Matter 1.5 during 2026 —
but a device type entering the spec is the start of the process, not the end of it.
So the honest reading of any “Matter 1.5 supports cameras” headline is: the standard will describe
how a camera should behave, and camera manufacturers will implement it on their own schedule, in
firmware, on future models. Do not buy a camera today on the strength of a specification revision.
Why this matters more in 2026 than it did in 2024
The reason to care about protocol independence right now is not the protocols. It is that
the assistant layer above them has churned harder in the last year than at any point since it
existed.
Amazon’s Alexa+ became generally available in early 2026 and moved to a paid tier for people
without Prime. Google replaced Assistant with Gemini for Home, and that migration runs one way —
there is no going back to the previous behaviour. Google also ended production of its Nest Mini and
Nest Audio speakers in mid-2026. Apple’s overhauled Siri has still not shipped.
None of that changes what a light bulb does. But it changes the risk profile of buying devices that
only speak to one assistant. A device that speaks Matter keeps working when you change your
mind about the voice assistant; a device tied to one vendor’s cloud is a bet on that vendor’s
roadmap — and 2026 has been an unusually bad year for those bets. Our
smart speaker guide
goes through what each of those changes actually did to the devices people already owned.
What to actually buy
Three rules cover nearly every purchase, and none of them requires you to pick a
side.
- Mains-powered and simple? Wi-Fi is fine. A smart plug or a bulb near the router
does not benefit from a mesh radio. Buying Matter here is cheap insurance against changing
ecosystem, not a functional upgrade. - Battery-powered? Avoid Wi-Fi. This is the one place the radio genuinely decides
the outcome. Wi-Fi sensors have short battery life because the radio is expensive to run. Thread,
Zigbee or Z-Wave will run for a year or more on the same cell. - Bandwidth-hungry? It will be Wi-Fi regardless. Cameras, speakers and displays
are not going onto a low-power mesh, whatever the spec sheet eventually says.
And one rule about hubs: count your border routers before you buy Thread, and if
the answer is zero, either change the device or change the plan. The cheapest smart home mistake is a
sensor that never joins a network.
How this page was compiled
Protocol definitions and device-type coverage come from the published Matter and Thread
specifications and from manufacturers’ own documentation. Ecosystem changes are dated to their public
announcements during 2026. We do not claim hands-on testing of these devices, and where a
specification revision has not yet reached shipping products this page says so rather than treating
the standard and the market as the same thing. Last reviewed: 8 August 2026.
Frequently asked questions
Is Matter a replacement for Wi-Fi or Zigbee?
No. Matter is an application layer — a shared language — that runs over Thread or Wi-Fi.
It does not replace a radio. A Matter device is always also a Thread device or a Wi-Fi device, and the
packaging often does not make that clear.
Do I need a hub for Matter?
Yes, you need a Matter controller, and if the device uses Thread you additionally need a Thread
border router. Many products serve as both, but not all Matter controllers are border routers, which
is the most common reason a new Thread device fails to connect.
What is the difference between Thread and Zigbee?
They use the same 802.15.4 radio, but Thread devices carry IPv6 addresses and are directly
addressable on your network, while Zigbee uses a proprietary protocol that requires a hub to translate.
Zigbee still has a considerably larger catalogue of available devices.
Will Matter make my existing Zigbee devices work with any ecosystem?
Not on its own. Existing Zigbee or Z-Wave devices need a bridge that presents them to Matter, and
whether your hub provides one depends on its manufacturer. A working Zigbee setup is not a reason to
replace anything.
Does Matter support security cameras?
Camera support was slated to arrive with the Matter 1.5 revision during 2026, but a device type
entering the specification is the beginning of the process. Manufacturers implement it on their own
schedule and usually on newer models, so do not buy a camera today based on a spec revision.
Should I avoid Wi-Fi smart home devices?
Only for battery-powered ones. Wi-Fi radios consume significantly more power, so Wi-Fi sensors need
recharging or new cells far more often. For mains-powered devices such as plugs and bulbs, Wi-Fi is
perfectly adequate and needs no hub.
Related guides
- Smart home buying guides — the full hub
- Best smart speakers — what Alexa+ and Gemini for Home actually changed
- Best smart plugs for energy savings
- Best Wi-Fi mesh systems for large homes — several double as Thread border routers
- What your always-on gadgets actually cost — hubs and border routers run 24/7
- How the deal calendar works — Prime events are genuinely the best window for Amazon’s own hubs
