INTEROPERABILITY / PROFILE GUIDE
ONVIF Profiles for IP Cameras: S, T, G and M Explained
ONVIF profiles for IP cameras describe defined interoperability capabilities, but they do not guarantee that every camera, NVR, VMS, firmware version, or workflow will behave the same way. Choose a profile by the job—streaming, recording, retrieval, metadata, or analytics—then verify the exact product and software version.
Updated 2026-08-31 · Interoperability
- PURPOSE
- Profile S is associated with basic video streaming and configuration. Profile T is aimed at more advanced video streaming and can include imaging, events, metadata, H.264/H.265, HTTPS, PTZ, and audio-related capabilities depending on the conformant device or client and the feature being tested.
- CONDITIONS
- Profile G addresses edge storage and retrieval: a conformant device can record video and a client can configure, request, or control recording. Profile M addresses analytics metadata and events, including metadata configuration and streaming, object classification, and event interfaces such as object counting or other supported analytics. A profile has a defined feature set with mandatory and conditional behavior. A device and a client may support different combinations of profiles, and a vendor may expose additional proprietary features outside the profile. Therefore, the question is not only whether two products show an ONVIF logo; it is whether the required workflow is supported by both sides.
- LIMITS
- This is a planning or editorial guide. It does not replace a site survey, current official source, legal review, or vendor acceptance test.
Match the profile to the job
Profile S is associated with basic video streaming and configuration. Profile T is aimed at more advanced video streaming and can include imaging, events, metadata, H.264/H.265, HTTPS, PTZ, and audio-related capabilities depending on the conformant device or client and the feature being tested.
Profile G addresses edge storage and retrieval: a conformant device can record video and a client can configure, request, or control recording. Profile M addresses analytics metadata and events, including metadata configuration and streaming, object classification, and event interfaces such as object counting or other supported analytics.
- Profile S — basic video streaming and configuration
- Profile T — advanced video streaming, imaging, events, and metadata
- Profile G — recording, retrieval, and recording control
- Profile M — analytics metadata, rules, and events
A profile is not a compatibility guarantee
A profile has a defined feature set with mandatory and conditional behavior. A device and a client may support different combinations of profiles, and a vendor may expose additional proprietary features outside the profile. Therefore, the question is not only whether two products show an ONVIF logo; it is whether the required workflow is supported by both sides.
For analytics, treat metadata and events as a separate acceptance scope. Confirm the object classes, event transport, rule configuration, image or metadata format, broker path if MQTT is involved, and how the VMS stores and searches the result. Avoid sending identifiable video or analytics data to an unapproved service.
Verify the product and firmware
Use the ONVIF conformant-products database as the starting point for a conformance claim, and match the listed product to its exact firmware or software version. Then test the target camera–VMS or camera–NVR workflow: discovery, authentication, media profiles, codec, HTTPS if required, recording, search, export, events, metadata, and PTZ when applicable.
Record the test result rather than copying a profile name into a specification. A device can be conformant for a profile while a particular client, firmware build, license, transport setting, or conditional feature still fails your operational requirement.
FIELD CHECKLIST
Record the result, not only the intention
- Write the required workflow before selecting an ONVIF profile.
- Check the exact product and firmware/software version in the official conformance database.
- Separate streaming, recording, retrieval, metadata, events, PTZ, and security tests.
- Verify conditional features, codec, transport, credentials, and vendor-specific limits.
- Record the integration result, firmware, settings, and failure evidence.
Sources to verify
- ONVIF profiles and specifications
Confirm the exact device profile, firmware, and conformance claim before integration.
- ONVIF Profile S
Official Profile S scope and current deprecation status.
- ONVIF Profile T
Official Profile T capabilities and feature overview.
- ONVIF Profile G
Official Profile G scope for edge recording and retrieval.
- ONVIF Profile M
Official Profile M scope for analytics metadata and events.
- ONVIF Conformant Products
Authoritative product and firmware/software conformance lookup.
FAQ / LONG-TAIL QUESTIONS
Frequently asked questions
Which ONVIF profile do I need for an IP camera?
Choose by the required workflow: streaming and configuration, advanced streaming, edge recording and retrieval, or analytics metadata and events. Check the exact device and client conformance records before selecting.
What is the difference between ONVIF Profile G and Profile T?
Profile G focuses on edge recording and retrieval workflows, while Profile T covers advanced video streaming and related capabilities. The exact mandatory or conditional features still depend on the conformant product and client.
Does ONVIF guarantee IP camera NVR compatibility?
No. A profile claim is an integration starting point. Verify the exact product, firmware, client, codec, transport, authentication, events, recording, search, export, and any vendor-specific or conditional feature.