If you are shopping for a home camera and you see the Matter logo on the box, two short documents from the group that runs the standard are the most detailed public description of what that logo covers. I read both, the release note for Matter 1.5 from 20 November 2025 and the maintenance note for Matter 1.5.1 from 31 March 2026, with one question in mind: what does a certified Matter camera have to do?

The documents answer a slightly different question. They say what the specification can describe. They do not say which of those things a particular camera has to implement before it gets certified, and that gap is where most of a buyer's real questions sit.

What Matter 1.5 says it added

Matter is the smart home standard maintained by the Connectivity Standards Alliance. Before version 1.5 it covered lights, plugs, locks, sensors and similar devices, and cameras were the obvious missing category. The release note puts the change in one sentence: "Developers can now build and certify cameras that interoperate directly with Matter-enabled ecosystems, without the need for custom APIs or integrations."

The next paragraph is the technical summary, and it is worth reading slowly:

"Matter cameras support live video and audio streaming using established WebRTC technology, enabling two-way communication and both local and remote access via standard STUN and TURN protocols."

Then comes the feature list:

"The specification also defines support for multi-stream configurations, pan-tilt-zoom controls, detection and privacy zones, and flexible storage options, including continuous or event-based recording to local or cloud destinations."

Read as a shopper, that second sentence sounds like a list of things a Matter camera does. Read as a specification summary, it is a list of things the standard has a way to express. Those are different claims, and the wording is careful to make the second one. The phrase "defines support for" means the standard contains a defined way for a camera to offer pan-tilt-zoom, or privacy zones, or recording to a local destination. It does not say every camera must offer them.

Some of the list cannot be mandatory, for physical reasons. A fixed camera with no motor cannot pan or tilt, and nobody would expect the standard to refuse it certification on that ground. So at least part of the list is a menu. Which parts are on every plate is the question the public text leaves open.

The sentence that keeps room for the maker's own app

One more line from the release note matters for anyone hoping a standard would end the era of one app per camera brand. It describes the release as enabling device makers to build Matter cameras "without limiting their ability to innovate through their own apps and services".

That is a reasonable design goal for a standard that needs manufacturers to sign up. It also means a Matter camera can still come with its own app and its own services, and that some features may be offered only there. The release note does not say which features a maker is allowed to hold back from the shared interface, and I would not guess.

Streaming: WebRTC, STUN and TURN

The streaming description is the most concrete part of the announcement, and it names real, widely used protocols. WebRTC is the same family of technology that browsers use for video calls. STUN and TURN are the two helpers WebRTC leans on when the two ends of a connection sit behind home routers.

STUN lets a device learn the public address its router presents to the internet, so two devices can try to reach each other directly. TURN is the fallback when a direct path cannot be made: the media is relayed through a server that both ends can reach.

That relay is the detail I would want to know about for a camera that points at the inside of my home. The release note says remote access works "via standard STUN and TURN protocols". It does not say who operates the relay server for a given camera or controller, whether the stream through it is encrypted end to end, or how often a typical home network falls back to it. Those are questions for the maker of the camera and the maker of the home app, not for the standard's press release, and I could not answer them from the public text.

For viewing inside the house, the picture is simpler. The same sentence names "local" access alongside remote access, which is the property many people want most from a camera: watching it on the home network without the footage leaving the building.

Four months later: what Matter 1.5.1 changed for cameras

The second document is a maintenance release, and it is unusually specific about cameras. Its own summary says the changes include bug fixes and refinements, "many focused on the newly introduced camera functionality from the 1.5 release". That is a normal thing for a first version of a big feature, and it is useful information for a buyer: early cameras built against 1.5 and later ones built against 1.5.1 may not behave the same way.

Here is what the note lists.

Multiple streams. The 1.5.1 note opens its camera section with this: "One of the most significant enhancements in Matter 1.5.1 is support for multi-stream video and audio delivery." It gives examples of streams a camera could deliver at once, including "A high-resolution stream for recording or storage" and "A lower-resolution stream optimized for mobile viewing".

This is the part that confused me. The 1.5 note had already listed "multi-stream configurations" among the things the specification defines support for. The 1.5.1 note describes multi-stream delivery as a new enhancement, and says that previously "multiple independent streams might need to be established" when several viewers or services wanted the same camera. My reading is that 1.5 could describe a camera with several streams, and 1.5.1 added a better way to deliver them together. That is a reading of two press releases, not of the specification, and I could be wrong about where the line falls.

Snapshots in HEIC. The note says "Snapshot images can now be delivered using the HEIC image codec", and compares it with JPEG on quality and size. For anyone who pulls snapshots from a camera into another tool, a format change like this is worth checking before it reaches your setup.

Recorded video upload. The note adds "full support for HLS and DASH streaming upload using the CMAF Interface-2 profile". HLS and DASH are the formats most video streaming services use. In plain terms, the standard now has a defined way for a camera to send recorded video somewhere in a format that common media and cloud platforms already understand. It does not tell you where a given camera will send it.

Recording validation. The note includes "fixes to recording configuration validation to prevent certain invalid recording setups". It does not list which setups were invalid. If you buy an early Matter camera and its recording settings behave oddly, this line suggests the specification itself was still being tightened in that area.

What the documents do not let me settle

I want to be direct about the limits of this reading, because the gaps are the useful part.

The full specification is not something I read for this. The 1.5 note says "The Matter 1.5 specification, SDK, and test tools are now available to Alliance Members." Both notes also point developers to a request form for the specification documents. I did not fill it in, so everything above comes from the two public notes. The answer to which camera features are mandatory for certification is presumably in the specification and the test plans, and I have not seen it.

I also have not checked which home apps and hubs display Matter cameras as of this writing, or how complete their support is. Coverage I found while searching disagreed on dates and details, and none of it was from the platforms themselves. The Connectivity Standards Alliance keeps a public list of certified products on its site, and each platform's own release notes are the place to confirm support, rather than a roundup.

And the documents say nothing about phones. Neither note mentions a handset used as a camera, so nothing here changes what a spare phone on a shelf can or cannot do.

Questions worth asking about any home camera

The feature list in the 1.5 note is still useful, just not as a promise. It works well as a list of questions, and the questions apply to any setup, with or without a logo on the box.

  • Where does recording go? The note lists "local or cloud destinations" as options the standard can describe. For a specific camera, ask which one it uses by default, and whether the local option works without an account.
  • Can I watch it on my home network with the internet unplugged? Local access is named in the streaming sentence. Whether a particular camera and app still work when the internet connection is down is a test you can run in a few minutes.
  • What relays the stream when I am away? If remote viewing goes through a relay, someone runs that server. Ask who.
  • How many people can watch at once, and at what quality? That is the problem the 1.5.1 multi-stream change was written for.
  • Which version was it certified against? A camera certified on 1.5 and one certified on 1.5.1 sit on different sides of a release whose fixes were mostly about cameras.

None of these has a universal answer, and a logo does not supply one. The value of a standard is that a camera can now be asked these questions in a shared vocabulary. The answers still have to come from the people who make the camera.

Try it: Background Camera RemoteStream on Google Play turns a spare Android phone into a camera that records with the screen off. Setup notes and other write-ups are at superfunicular.com.

Sources. The Matter 1.5 release announcement and the Matter 1.5.1 release announcement, both from the Connectivity Standards Alliance. Quotations are verbatim from those pages as read in November 2026.