What Matter is, in plain terms
It is a language devices speak, not a network they join. Almost every myth about Matter comes from getting that backwards.
Matter is a layer, and layers stack#
Every connected device in your house is doing three separate jobs at once, and people collapse them into one word.
| Layer | The question it answers | Examples |
|---|---|---|
| Radio and wiring | How do bits become signals? | Wi-Fi at 2.4 and 5 GHz, IEEE 802.15.4 at 2.4 GHz, an Ethernet cable |
| Network | How does a packet reach the right device? | IPv6 over Wi-Fi, IPv6 over Thread, IPv6 over Ethernet |
| Application | What is this thing, and what can I ask it to do? | Matter, the Zigbee cluster library, a vendor's cloud API |
Matter lives only on the top row. It never touches the bottom row. That is why "Matter vs Wi-Fi" makes as much sense as "English vs telephone": one is what you say, the other is how the sound gets there.
The practical version of this is short. There is no Matter radio. You cannot buy a Matter chip that replaces a Wi-Fi chip. When a box says "Matter", look for the second word next to it: Matter over Wi-Fi or Matter over Thread. That second word is the thing that determines battery life, range and what extra hardware you need.
The three transports, and what each one costs you#
| Transport | Extra hardware | Battery devices | Where it fits |
|---|---|---|---|
| Wi-Fi | None beyond your router | Poorly, Wi-Fi radios are power hungry | Plugs, mains-powered lights, appliances, cameras |
| Thread | A Thread border router your ecosystem trusts | Yes, sensors run for years on a coin cell | Sensors, locks, buttons, low-power lights |
| Ethernet | A cable | Not applicable | Hubs, bridges, TVs, anything already wired |
Bluetooth LE belongs in this discussion but not in this table. Matter uses Bluetooth to get a device onto a network during setup, and then stops using it. It is a setup channel, not a control channel, which is covered in Bluetooth and BLE in the smart home and in Matter pairing explained.
The trade between the first two rows is the whole radio decision, and it does not go away because a device is Matter certified. Which radio for which job is the decision table, and Thread vs Wi-Fi for smart devices covers the battery and latency arithmetic.
What Matter actually guarantees#
These are the promises the specification makes, and they are worth something:
- Any certified controller can drive any certified device. The device describes itself in a standard way, so a controller supports a device class rather than a specific product.
- One setup flow. Scan the code in whichever app you like. No vendor hub in the middle, no account required for the device itself.
- Multi-admin. The same physical device can be commissioned into several ecosystems at once, each with its own credentials. Devices are required to support at least five of these security domains, called fabrics. Sharing a Matter device across ecosystems has the steps per platform.
- A path that stays on your LAN. Commands travel over IPv6 on your own network. Nothing in the protocol requires a round trip to a vendor server.
- Real device identity. Every certified device carries a manufacturer-installed certificate that a controller checks against a root published by the alliance before it will trust the device. That is a genuinely higher bar than most of what came before.
What it does not guarantee#
This is the part that decides whether you are happy six months later.
It does not guarantee local control. The alliance's own guidance is explicit that a Matter-only device needs an internet-connected controller for control from outside the home. Worse, some ecosystems process even in-home commands in the cloud. Google Home's local Matter control covers lights, plugs and switches only. Alexa maps Matter clusters onto its own cloud-side capability interfaces. Local vs cloud control traces the five places a command can be processed.
It does not guarantee feature parity with the vendor app. Matter standardizes the boring, universal part of a device. A color bulb with animated effects presents as on, off, brightness and a solid color. A robot vacuum presents as start, stop and a run mode; maps, no-go zones, schedules and consumable life are not in the specification at all. What Matter still cannot do is the complete list.
It does not guarantee your controller implements the device type. The specification defines 92 device types as of Matter 1.6. No consumer ecosystem is close to that, and the lag is measured in years rather than months. Every Matter version and what shipped in each has the dates.
It does not guarantee firmware updates. Over-the-air updates through Matter are optional. Some vendors publish firmware through the alliance's compliance ledger and some do not, and a device behind a bridge never gets one over Matter at all.
It does not guarantee quality. Certification proves a sample passed a test suite. Three shortcut paths exist, certification by similarity, product family certification and certification transfer, under which only the original product is actually lab tested. The clearest recent example was IKEA's Matter over Thread line in early 2026, where owners and reviewers reported repeated pairing failures on certified hardware.
Who runs Matter, and why it exists#
Matter is developed by the Connectivity Standards Alliance, the organization that was the Zigbee Alliance until 2021 and that still owns Zigbee. Matter 1.0 was published on 4 October 2022, IPv6 only from day one, with Wi-Fi, Thread and Ethernet as transports and Bluetooth LE for commissioning.
The alliance reported 940 member companies at its June 2026 event, with about 300 actively working on the specification, and more than 1,200 distinct certified Matter products as of the same month. Certification records run several times higher than that, because rebadges, regional versions and certification-by-similarity descendants each generate a record. Any headline claiming many thousands of Matter devices is counting paperwork.
The reason it exists is the previous decade. Every vendor built its own cloud and its own hub, and the standards that were meant to unify them, including the wave described in twenty years of smart home standards, each solved one layer and left the others proprietary. Matter's bet is that standardizing the application layer, and only that, is the piece that actually unlocks the others.
What the logo on the box means#
There is no alliance "Works with Matter" badge. Only certified devices carry the Matter logo itself. The "works with" logos you see on packaging, Works with Apple Home, Works with Google Home, Works with Alexa, Works with SmartThings, are ecosystem programs that test the experience on that platform. They are useful, but they are not Matter conformance, and a device can carry one without being a Matter device at all. Works with Matter vs Matter certified shows exactly what to look for.
A buying rule that holds up#
- Decide the transport first. Battery device or something far from the router: Thread, and confirm you have a border router your ecosystem recognizes. Mains-powered and close to the router: Wi-Fi is fine and simpler.
- Check that your controller implements the device type, not just that the device is certified. A certified water heater is useless if your app has never heard of water heaters.
- Assume the vendor app still exists. If a feature sold you on the product and it is not on, off, brightness, color, position, temperature or a lock state, plan on using the vendor app for it.
Is Matter a protocol or a standard?
Both words fit, but the useful description is that Matter is an application layer protocol plus a certification program. It defines the data model devices expose and the messages controllers send, and the alliance runs the testing that lets a product carry the logo. It does not define a radio or a network.
Is Matter better than Wi-Fi?
The question does not resolve, because they are different layers. A Matter over Wi-Fi device uses both at once. If the real question is whether a Matter device is better than a cloud-connected Wi-Fi device from a single brand, then usually yes, because it works with more apps and it can run on your LAN.
Do Matter devices need the internet?
Not for the protocol itself. Control from inside the home can be entirely local, and automations stored on a local hub keep running. Remote control from outside the home needs an internet-connected controller, and several ecosystems route more traffic through their cloud than Matter requires them to.
Will Matter work with my old Zigbee and Z-Wave devices?
Not directly. Those are different application layers on different radios. A hub can act as a Matter bridge and present them to a Matter controller, which works well for basic control and drops the advanced features. Matter bridges and what you lose through one is specific about what gets dropped.
Does Matter replace Thread?
No, it uses Thread. Thread carries IPv6 packets over a low-power mesh; Matter is the language inside those packets. A Thread device that is not a Matter device is possible, and a Matter device that uses Wi-Fi instead of Thread is common. Matter vs Thread settles it in one sentence and then proves it.
Should I wait for Matter to mature before buying?
For lights, plugs, switches, contact and motion sensors and most thermostats, no. Those categories are well covered by every major controller today. For appliances, energy hardware, cameras and closures, the specification is ahead of the controllers by a long way, so buy for what the product does in its own app right now.
Primary sources
Specification and vendor documentation we checked while writing this page. Where a claim depends on firmware behaviour rather than a published spec, the page says so inline.