ONVIF is the reason a camera from one manufacturer can record to a VMS from another. It is also one of the most carelessly specified words in the industry, because “supports ONVIF” can mean almost anything. The unit of meaning is the profile.
What the profiles mean
A profile is a fixed bundle of capabilities that both the camera and the VMS implement, so conformance on both ends guarantees the bundle works between them.
Profile S is the workhorse: video and audio streaming, PTZ control, relay outputs. If a camera and VMS both conform to S, live video will flow.
Profile G covers recording and retrieval on the edge device: cameras or encoders with onboard storage, and the VMS’s ability to search and pull that footage. If the design uses SD-card fallback recording, G is what makes it retrievable.
Profile T is the modern streaming profile: H.265 support, imaging configuration, motion and tamper event handling, bidirectional audio. New multi-vendor designs should generally specify T alongside S.
Profile M covers metadata and analytics events: how a camera’s analytics (objects, classifications, events) publish to consuming systems. As analytics move to the edge, M is what keeps them portable across VMS platforms.
What conformance does not guarantee
ONVIF guarantees the profile’s bundle, nothing more. The manufacturer’s smart features, their proprietary analytics dashboards, their camera-side configuration niceties: none of that is in scope, and a camera driven over ONVIF often exposes less than the same camera under its native driver. That is the trade-off to design around: native integrations where the feature depth matters, profile conformance as the floor that protects the owner from vendor lock-in and product discontinuations.
Verify claims rather than trusting datasheets. ONVIF maintains a public conformant products database; a product that is not in it is not conformant, whatever the brochure says. Membership in ONVIF is not conformance either.
Specifying it properly
Write profiles into the specification by letter: “cameras shall conform to ONVIF Profiles S and T; edge-recording devices to Profile G; analytics-publishing devices to Profile M,” and require listing in the conformant products database. Then commission against it: confirm streams, events, and PTZ under the ONVIF connection actually used, not the native driver the integrator demoed with. The gap between the two is where the callbacks live.
How it fits
Profiles define the application-layer contract between camera and VMS. The VMS selection guide covers where open-platform conformance should outweigh native-feature depth, and the plant underneath still has to meet TIA-568 for any of it to matter.
Related guides
- ANSI/TIA-568: Structured Cabling for Security Systems
- SIA OSDP (IEC 60839-11-5): OSDP: Open Supervised Device Protocol
References
Last updated 2026-07-24.