Installer checking mixed-brand cameras beside recorder

ONVIF: Verify Model, Firmware, and DoC Before Mixing Camera Brands

ONVIF is an open industry standard that lets IP cameras, recorders, and software from different brands talk to each other. Devices from different manufacturers can work together when both support the same ONVIF profile and the firmware matches the listed Declaration of Conformance. Always check the exact model and firmware on the official conformant products list before you assume compatibility.

TL;DR:

  • Verify each camera and recorder by exact model and firmware in ONVIF’s conformant products list; confirm both declarations name the profile you need.
  • Use Profile S or T for live video, Profile G for recording search and replay, and Profile M when analytics metadata must reach client software.
  • A shared profile guarantees only its required baseline; optional features, vendor analytics, and smart search may still need integration from the manufacturer.
  • ONVIF handles discovery and setup, while video travels over RTSP; test the stream, intended events, and credentials with the actual recorder before permanent installation.
Safes and Security Solutions
Choose Cameras With Confidence
Explore security cameras and systems with detailed product listings to help you compare options for your property or business.
Browse security products

Table of Contents

What ONVIF is and what it covers

ONVIF, short for Open Network Video Interface Forum, is a global industry organization founded in 2008 that defines standardized interfaces for IP-based physical security products. The goal is simple: a camera from one maker should be manageable by a recorder or software from another.

ONVIF does not make hardware. It publishes network interface specifications, and manufacturers build products that follow them. Its three cornerstones are standardized communication, interoperability regardless of brand or deployment style, and openness to any company.

Here is what the specifications handle:

  • Device discovery: finding cameras and recorders on a network.
  • Device management: configuring network settings, users, and time.
  • Events: motion alerts, tamper alarms, and similar notifications.
  • Media endpoints: telling a client where and how to pull video.

Features are grouped into profiles, so you can match a product to your use case. Member companies maintain the standard, but conformance is declared per product, per model, and per firmware version.

How ONVIF works under the hood

ONVIF is built on ordinary web technology. According to the ONVIF Core Specification, its interfaces use XML, SOAP, and WSDL web services carried over HTTP, with discovery based on WS-Discovery. ONVIF reuses existing standards to help clients communicate with devices from different manufacturers.

The key building blocks:

  • WS-Discovery: a mechanism for discovering devices on the network.
  • Web-service APIs: commands for device management, events, PTZ control, and media configuration over HTTP or HTTPS.
  • Stream endpoints: ONVIF tells the client where video lives, while the video itself usually travels over RTSP.

That last point trips people up. ONVIF handles communication about setup and capabilities, while video streaming uses a separate mechanism.

ONVIF’s core specification defines device discovery, device management, event handling, media configuration, and PTZ control, giving every vendor the same blueprint to build against.

Camera and recorder linked by shared interface

ONVIF profiles: which one do you need?

Profiles are where ONVIF becomes practical. The official profiles page explains that each profile defines a fixed set of mandatory and conditional features, so two products carrying the same profile share a known baseline.

  • Profile S: video streaming. Live view and basic stream control. This is the classic camera-to-recorder profile.
  • Profile T: advanced video. Newer codecs, higher resolutions, and more capable streaming.
  • Profile G: recording. Storage control, search, and replay between recorders and clients.
  • Profile M: metadata and analytics. Lets devices pass analytics data, such as object detection, to a client.
  • Profile C: check the official profiles page for the features it supports.

A typical home or small business setup needs Profile S or T on the cameras and the same profile on the recorder. If you plan to use recorded video search from third-party software, look for Profile G. Analytics-heavy projects should check for Profile M on both sides.

Can devices from different manufacturers really work together?

Yes, with a caveat that matters. The ONVIF conformance FAQ states that conformance is tied to a specific product model and firmware version. A box that says “ONVIF compatible” is not proof. Joining ONVIF as a member does not equal conformance either, because conformance means a product passed the test tool for one or more profiles, as the ONVIF conformance webinar explains.

To verify a device:

  1. Write down the exact model number and installed firmware version.
  2. Search the ONVIF conformant products database for that model.
  3. Open the Declaration of Conformance and confirm the profile and firmware listed.
  4. Repeat for the recorder or software that will manage the camera.

Common reasons integrations fail include firmware that differs from the tested version, optional features a vendor never implemented, and older devices where the ONVIF password is separate from the web interface login. Watch for that last one: a camera can accept your admin password in a browser and still reject it over ONVIF.

Ports and protocols you will run into

Network details cause a lot of confusion, so here is the short version:

  • HTTP and HTTPS: ONVIF services typically answer on port 80 or 443, though there is no single mandated port and devices can be set to use others.
  • RTSP: ONVIF can provide the client with the stream address.
  • Vendor ports: some manufacturers open proprietary ports for their own tools. Port 37777, for example, shows up in some Dahua documentation. It serves vendor-specific functions and sits outside the open ONVIF standard.

If a firewall rule works for one brand and fails for another, check which port each is actually using before blaming ONVIF itself.

Checklist: confirming a multi-vendor setup will work

Run through these steps before you buy or install:

  1. Record the exact model and firmware, then look both up in the ONVIF conformant products database.
  2. Confirm the camera and the recorder or software both support the same profile your use case requires.
  3. Run discovery with an ONVIF client or discovery tool to retrieve each device’s service address and stream endpoint.
  4. Check which credentials ONVIF services use, since some older units keep separate ONVIF passwords, and prefer HTTPS where available.
  5. Test live RTSP streaming, plus any events or analytics you intend to rely on, before mounting anything permanently.

Pro Tip: Test one camera on your bench first. A trial with the actual recorder can catch firmware and password quirks before you have cable pulled through a ceiling.

For help to compare complete kits, see our security camera system buyer’s guide.

Benefits and honest limits of ONVIF

The benefits are real:

  • Brand freedom: you can mix cameras and recorders rather than being locked to one maker.
  • Less custom work: integrators avoid writing a separate driver for every camera.
  • Easier upgrades: replacing one device does not mean replacing the whole system.
  • Wide choice: the official database lists over 35,000 conformant products as of mid-2026.

The limits are just as real. Conformance does not mean identical features. Advanced functions, such as a maker’s special analytics or smart-search tools, may still need vendor-specific integration. That is why the profile match and the DoC check matter more than any claim on the box.

Our perspective on buying ONVIF-capable systems

We stock camera systems, and we recommend reading the spec sheet for profile listings before you order. Our buying guide for home and business covers what to compare. If you are unsure about a profile or firmware question, contact our support team before purchase and we will help you sort it out.

— Safes and Security Solutions

Ready-to-deploy camera systems from our catalog

If you would rather start with hardware that is built to work as a set, look at our 8-channel PoE system with true-color night vision, or our Amcrest 4K 16-channel NVR with 8 PoE ports and a preinstalled drive. Check each product’s spec sheet for ONVIF and profile support, and ask us to confirm compatibility.

Safes and Security Solutions

FAQ

What port does ONVIF use?

ONVIF has no single required port. Its web services usually run over HTTP or HTTPS on ports 80 or 443, but a device can be configured for others. Check the camera’s network settings and test with a discovery tool.

What is port 37777 used for?

Port 37777 is a proprietary vendor port that appears in some Dahua documentation. Manufacturers use ports like this for their own non-ONVIF functions, so it is separate from the open ONVIF standard.

How do I configure an ONVIF camera?

Enable ONVIF in the camera’s settings and create or confirm the ONVIF user, since older units may use a password separate from the web login. Then run discovery from your recorder or software to find the device and its stream address.

Which cameras are supported by ONVIF?

Any camera whose exact model and firmware appear on the official ONVIF conformant products list is supported for the profiles listed. Look up the specific combination rather than relying on a general label.

Back to blog