The badge is on almost every commercial camera, and it is doing far less work than buyers think. ONVIF’s own guarantee is between products conformant to the same named profile. “ONVIF compatible” on a datasheet is a different claim, and the distance between the two is where mixed-brand systems come apart.
An interoperability specification, not a quality mark
ONVIF states its own mission as being “to provide and promote standardized interfaces for effective interoperability of IP-based physical security products and services.” It was founded in 2008 by Axis Communications, Bosch Security Systems and Sony Corporation, and it says it now has more than 500 member companies across six continents. That membership figure is ONVIF’s own; we are repeating it, not counting it.
Read that mission statement carefully, because it says what it says and nothing more. ONVIF standardises interfaces. It is not a quality mark, not a security certification, not a durability rating and not a statement about who manufactured anything. A conformant camera can still be a bad camera. Those are separate questions and the badge answers none of them.
What it is genuinely for is the problem every building with more than one generation of equipment eventually has: a recorder from one manufacturer and cameras from another, or a system inherited from a previous tenant, previous owner or previous installer. Before anything like ONVIF, that combination usually meant a proprietary integration or a rip-out. The specification exists so it can mean neither.
The guarantee is per profile, not per badge
ONVIF publishes profiles. Each is a fixed set of features a conformant device and client must support. This is the part that decides whether two products will actually work together.
| Category | Profiles |
|---|---|
| Video | S, G, T |
| Access control | A, C |
| Both video and access control | D, M |
| Release Candidate status | V |
| Deprecated 1 April 2022 | Q |
Source: ONVIF, Profiles: onvif.org/profiles, and ONVIF, Mission: onvif.org/about/mission. Retrieved: 4 September 2026. This page lists profiles by letter and category only. What sits inside any individual profile is deliberately not restated here, because we did not verify the feature sets one by one and we are not going to summarise a specification from memory.
ONVIF’s own words on what conformance buys you: “An ONVIF profile has a fixed set of features that must be supported by a conformant device and client. It ensures that a client that conforms to Profile T, for example, will work with a device that also conforms to Profile T.” And, more bluntly: “Conformance to profiles is the only way that ensures compatibility between ONVIF conformant products.”
That second sentence is the whole page. The guarantee runs between two products conformant to the same profile. It does not run between two products that both have the word ONVIF printed somewhere.
Where it goes wrong
The four failures we actually see on site
- Two products, one word, no shared profile. A camera and a recorder both described as ONVIF, conformant to different profiles or to none. Video may well come up, because the basic stream is the part almost everything implements. Everything past that is where it stops.
- “Compatible” read as “conformant”. Conformance is a defined status against a named profile. “Supports ONVIF” is a sentence a marketing department can write. The words look interchangeable on a datasheet and are not.
- The features people care about are the ones outside the basic stream. Nobody mixes brands because they want a picture. They want the picture plus whatever else the system does, and that is exactly the territory where the profiles differ.
- Nobody checked before buying. The commonest version. Four cameras are ordered to match an existing estate on the strength of the badge, they arrive, and the question of which profile anything holds gets asked for the first time with the boxes open.
None of that is an argument against ONVIF, and we are not going to pretend it is. The specification does the job it describes. The failure is in reading a profile-specific guarantee as a general one, and it is an easy misreading to make, because the badge is printed as though it were general.
A boundary worth stating twice
ONVIF tells you nothing about Section 889
These two get conflated, and the consequences of conflating them are not symmetrical.
- Different questions entirelyONVIF describes how devices talk to each other. Section 889 is a procurement prohibition written about who produced a piece of equipment. One is an interface; the other is a supply chain. Neither is evidence of the other.
- Both can be true at onceA camera can be conformant to an ONVIF profile and be produced by an entity named in the statute. Conformance is open to members and testing is about interfaces, so nothing about it screens for the thing Section 889 is concerned with.
- The brand does not settle either oneThe name on the bezel does not identify the producer, which is the trap the Section 889 pillar is largely about. A relabelled product can carry an unfamiliar brand, a conformance listing and a covered producer at the same time.
- Answer them separately, in writingThe profile question is settled by asking which profile each end of the system holds. The Section 889 question is settled by written attestation from the manufacturer identifying the actual producer. Two questions, two answers, neither substituting for the other.
- Why the asymmetry mattersGetting the profile wrong costs you a feature and an argument with a supplier. Getting Section 889 wrong, if you hold or want a federal contract, is a procurement problem. They are not the same size of mistake.
- Where the detail isThe full treatment is on NDAA compliant security cameras, including why “NDAA compliant” is a marketing phrase, not a statutory term, and why no body certifies a camera as such.
What we do about it
Ask for the profile, in writing, before anything ships
The practical version of this whole page is one habit: when a product is offered as ONVIF, ask which profile it is conformant to, and check that against the profile the other end of your system holds. If the answer comes back as “it’s ONVIF” instead of a letter, you have not been given an answer.
On our own jobs we do not promise an integration before seeing what you run. Where a system is being extended instead of replaced, what is already installed decides what can be added to it, and that is established at survey against the actual equipment — never from a datasheet. We would rather tell you at survey that a mixed estate will not do what you were told it would than find out with the boxes open.
Taking over a system somebody else installed is a large part of what we do, and establishing what it actually is forms part of that. CCTV service and repair covers how an inherited system gets documented. Where an estate is being extended, the design work is under commercial camera installation, and what carries the traffic underneath it is under structured cabling.
Two boundaries, as on every page here. We work on commercial premises only and not on private residences. And we do not hold a C-10 or a C-16, so we do not work on fire alarm systems; that is coordinated with your own licensed fire alarm contractor.
ONVIF and interoperability questions
Does an ONVIF badge mean any camera will work with any recorder?
No, and this is the single most expensive misreading in the field. ONVIF publishes profiles, each with a fixed feature set, and the guarantee it states is between products conformant to the SAME profile: in ONVIF’s own words, a client that conforms to Profile T will work with a device that also conforms to Profile T. ONVIF is equally direct that conformance to profiles is the only thing that ensures compatibility between conformant products. So the useful question is never “is it ONVIF” but “which profile is it conformant to, and is that the same profile my recorder is conformant to”. Two products that both carry the name and share no profile have been sold to you on a word instead of on a specification.
What is the difference between “ONVIF conformant” and “ONVIF compatible”?
Conformance is a defined status against a named profile. “Compatible”, “supports ONVIF” and similar phrases on a datasheet are marketing descriptions with no fixed meaning, and a manufacturer can print them without the product having been through anything. In practice a product described that way often does implement part of the specification, and that part is often enough for a basic video stream and nothing more. It is a real distinction, not a pedantic one — the features people care about when they mix brands are usually the ones beyond the basic stream. Ask for the profile by letter and check it against the profile the other end of the system holds.
Does ONVIF conformance tell me anything about NDAA Section 889 compliance?
Nothing at all, and treating one as evidence of the other is a serious error. ONVIF is an interoperability specification: it describes how devices talk to each other. Section 889 is a procurement prohibition written about who PRODUCED a piece of equipment. A camera can be conformant to an ONVIF profile and be produced by an entity named in the statute, and a camera can be outside Section 889 entirely and hold no ONVIF conformance. The two questions do not overlap and must be answered separately. What Section 889 actually prohibits, and why the brand on the bezel does not tell you who produced a device, is set out on our Section 889 pillar page.
If we standardise on one manufacturer, does interoperability stop mattering?
It matters less on the day you buy and just as much later, which is the part that catches people. A single-manufacturer estate is genuinely simpler: the features work, the tools are consistent, and nobody is chasing which profile does what. The exposure is at replacement. A camera fails, a model is discontinued, a manufacturer changes direction or gets named in a procurement rule, and the question of what else your recorder can accept arrives at the worst possible moment. Knowing what your system is conformant to is worth establishing while nothing is broken, and it is one of the things we write down when we take over a system somebody else installed.