ONVIF explained: what it does, what it doesn't and how to mix camera brands

"It's ONVIF, so it will work" may be one of the most expensive sentences in this trade. ONVIF is a real and useful standard, and it makes multi-brand systems possible. But it doesn't guarantee that every feature on a camera will work on another company's recorder. Installers who understand the difference can design mixed systems confidently, and they avoid being surprised on site.

What ONVIF is

ONVIF, the Open Network Video Interface Forum, is an industry organisation that publishes specifications for how IP security products talk to each other. It was founded in 2008 by Axis, Bosch and Sony, and many manufacturers have since joined.

Instead of every recorder needing custom code for every camera, ONVIF defines shared ways for devices to be discovered, configured and streamed. This gives customers more choice. They can use one brand's cameras with another's recorder or software, in theory at least.

Profiles: the part that matters most

ONVIF groups features into profiles. A product and a client that both conform to the same profile should be able to work together for the features in that profile.

Profiles and their details change over time, and some have been retired. Check the current list on the ONVIF website.

Two details trip people up:

• Both sides need the same profile. An excellent Profile T camera is no use for Profile T features if your recorder only handles Profile S.
• Conformance is claimed for specific products and firmware. A line in a data sheet isn't the same as a listing on ONVIF's site.

Check the conformant products list

ONVIF publishes a list of conformant products. Before relying on a mixed design, look up both the camera and the recorder or software by their exact model, and check:

• which profile is listed
• which firmware version is covered
• whether the listing is current

If a product isn't listed, it might still work, but it's not officially conformant. Ask the manufacturer to explain why.

What ONVIF usually gives you

With a correctly matched setup, you can generally expect:

• device discovery on the network
• a video stream
• basic configuration, such as resolution and frame rate
• PTZ control
• motion events, in many cases

What ONVIF often doesn't give you

Here's where the problems begin.

• Vendor-specific analytics. Line crossing, intrusion areas, face detection and so on may only be available through the manufacturer's own recorder. Even if they're passed along, the rules may need to be set directly on the camera.
• Advanced compression options. Smart codecs can behave differently, or may not be supported.
• Dual stream handling. A recorder might not select the sub stream correctly.
• Two-way audio. It may work, or it may need extra configuration.
• Camera-side storage retrieval. This needs Profile G support on both sides, and may still have limits.
• Fisheye and multi-sensor layouts. De-warping and multiple channels may not work as expected.
• Device management. Firmware updates and bulk changes usually need the vendor's own tool.
• Smart search. Search by motion or object type might not work at all across brands.
• Plug-and-play setup. Same-brand cameras often appear automatically with a single password. Mixed systems may need more manual steps.

If your customer's main reason for buying a camera is a certain analytics feature, test that specific feature. Don't assume that it will carry across.

RTSP: the simpler fallback

Many cameras also provide RTSP streaming, a common way to pull video. Video software can usually record an RTSP stream with just a URL and a password. It's useful when ONVIF discovery fails, but RTSP alone gives you video, and often no events or PTZ control. Treat it as a last resort rather than a design choice.

Keep security in mind too. Set strong passwords and avoid sending credentials in the clear, and don't expose these streams to the internet.

Common ONVIF problems and fixes

The authentication problem is very common. Many cameras separate their web login from their ONVIF login, and an installer who changes the web password might assume that's the end of it. A clock mismatch is equally common and easy to miss.

Security settings

Be careful about how you enable interoperability.

• Enable ONVIF only when needed, and only on the required network.
• Create a separate, strong password for ONVIF users.
• Disable anonymous discovery where you can.
• Keep cameras on a separate network or VLAN.
• Keep firmware up to date.

See our cyber security guide.

When mixing brands makes sense

• Upgrading in phases. Keep working cameras, and replace the recorder or add new models.
• Specialised needs. A thermal camera or number plate camera may not be available from your main brand.
• Using video management software. VMS platforms typically have strong support for many brands, often beyond plain ONVIF, using dedicated drivers.
• Avoiding vendor lock-in. Some customers want an open approach.
• Compliance. Replacing certain cameras while keeping others, where the rules for that customer allow.

When to stick with one brand

• Small systems, where simplicity matters more than flexibility
• Projects relying on brand-specific analytics or smart search
• Teams without much networking experience
• Tight timelines with little room for testing

One-brand systems tend to install faster and be easier to support. Our brand selection guide goes into how to choose.

Test before you commit

A short test can prevent a costly job. Before you quote a mixed system at scale:

1. Get one sample of each camera model and the recorder or software.
2. Update them to the firmware you plan to use.
3. Check their ONVIF listing.
4. Add each camera. Note how long it takes.
5. Check main and sub streams, frame rate and bitrate.
6. Trigger motion and any analytics that matter.
7. Test recording and playback, including a restart.
8. Test PTZ, audio and remote viewing, if they're in the scope.
9. Leave it running for a day or more.
10. Write down the settings that made it work.

Save those notes for your team. They become your internal compatibility list, which is far more useful than any data sheet.

What to put in your quote and contract

When proposing mixed systems, be open about the limits. For example:

"These cameras connect to the recorder using ONVIF. Live view, recording, playback and motion recording have been tested. The camera's advanced analytics will run on the camera itself and aren't available through the recorder's search."

For existing systems, say that you'll test existing cameras and that compatibility isn't guaranteed until you do. It protects you if an old camera doesn't work with the new recorder, and it sets a fair expectation for the customer. Our quoting guide explains how to set out assumptions.

Keeping it working

Firmware updates can break or change compatibility, so don't update one brand on a mixed system without testing. Keep a record of the versions that work, and test any update on one device first. On a maintenance contract, include this as part of your scheduled review.

ONVIF is a very valuable tool. Treat it as a good starting point for compatibility, not a promise that everything will work. A little testing will separate what's possible from what's merely printed on a data sheet.