ONVIF (Open Network Video Interface Forum) is the industry standard that lets cameras and video software from different manufacturers talk to each other. Before it, every camera maker spoke its own protocol, so mixing brands meant custom integration for each one. ONVIF defines a common language — built on web-services (SOAP/XML) — for discovery, streaming setup, PTZ control, recording, events, and analytics, so a conformant VMS can operate a conformant camera without vendor-specific code.
Crucially, ONVIF works through Profiles: named bundles of features a device or client can claim conformance to. Profile S covers live streaming, G covers recording and storage, T adds advanced streaming (including H.265) and richer events, and M carries analytics metadata. A camera and a VMS interoperate on the features of the profiles they both support — that shared profile is the real contract, not the ONVIF logo alone.
The pitfall is the "ONVIF just works" assumption. ONVIF guarantees a baseline, not full feature parity: conformance means the standardised functions work, but a camera's advanced or unique features (fine PTZ behaviour, special imaging modes, proprietary analytics) often still require the manufacturer's SDK. Read "ONVIF-conformant" as "the basics are guaranteed", and verify the specific profile and version rather than trusting the badge.
