ONVIF vs RTSP for Security Cameras: What Is the Difference?

If you have configured an IP camera, you have probably seen the terms ONVIF and RTSP. They are sometimes presented as competing choices, but that is misleading. ONVIF is primarily about interoperability between network-video devices and software; RTSP is a protocol used to establish and control media streaming sessions.

In many camera systems, the two are used together: software uses ONVIF services to discover a camera or obtain media information, then receives the actual video through an RTSP stream.

What ONVIF does

ONVIF is an industry standardization initiative for interoperability between IP-based physical security products. Instead of every camera vendor inventing a completely different integration method, ONVIF defines common services and profiles that compatible devices and client software can implement.

For video systems, ONVIF profiles define sets of interoperable features. For example, Profile T is intended for advanced video streaming and includes features such as H.264/H.265 streaming, imaging settings, motion/tampering events, metadata, and other capabilities depending on the device and client.

In practical camera setup, ONVIF can help software find a camera and learn how to communicate with it. Security Eye's IP camera wizard scans the local network for UPnP and ONVIF devices, which can make setup easier than manually entering every camera parameter.

What RTSP does

RTSP stands for Real Time Streaming Protocol. It is used to establish and control streaming sessions. A camera may expose a URL such as an RTSP address that a compatible client uses to request its media stream.

RTSP itself is not a camera-discovery standard and it does not mean a device supports every feature of a surveillance platform. Think of it as the route to a media stream once the client knows where that stream is and how to authenticate.

Security Eye added RTSP support for IP cameras in version 3.4. When a camera is not found automatically, a manually configured stream or camera profile can sometimes provide another way to connect, depending on the camera's capabilities.

How ONVIF and RTSP fit together

ONVIF's own Profile S specification illustrates the relationship clearly: a client can request media profiles and a stream URI from the device, then stream the selected media over RTSP. In other words, ONVIF can tell the software what stream is available and how to request it, while RTSP participates in the actual streaming session.

This is why asking “Should I use ONVIF or RTSP?” is often the wrong question. A better question is:

• Can the software discover and configure the camera through ONVIF?
• If not, does the camera provide an RTSP stream that the software can use directly?
• Are the camera's codec, authentication, and stream settings compatible with the client?

What does ONVIF Profile S deprecation mean?

ONVIF announced that support for Profile S will end on March 31, 2027 and recommends Profile T for new products. This does not mean existing Profile S cameras suddenly stop streaming on that date. ONVIF states that users can continue using Profile S, but the organization is moving away from it because its mandated username-token authentication is no longer aligned with current cybersecurity recommendations.

If you are buying new cameras in 2026 or later, it is sensible to check current ONVIF conformance and prefer modern security capabilities rather than choosing hardware solely because an old specification name appears on the box. You can read ONVIF's Profile S deprecation Q&A and Profile T overview for the current status.

When automatic ONVIF discovery is the easiest path

Use automatic discovery first when:

• the camera and Windows PC are on the same local network;
• the camera has ONVIF enabled;
• network isolation is not blocking device discovery; and
• you want the setup wizard to identify the device rather than manually entering a stream address.

In Security Eye, select the camera discovered by the wizard, enter its credentials, and use Connect & Test. See How to Add an IP Camera to Security Eye for the full workflow.

When a direct RTSP approach may help

A direct RTSP stream can be useful when:

• the camera is not discovered automatically;
• the manufacturer documents a specific RTSP URL;
• you only need the video stream rather than a broader set of standardized device controls; or
• you are troubleshooting whether the problem is discovery/configuration or the media stream itself.

Do not guess RTSP paths from another camera model. Vendors can use different paths, stream numbers, channel identifiers, and authentication requirements. Use the camera manufacturer's documentation for the exact device and firmware version.

Compatibility checklist

• The camera is reachable from the Windows PC on the local network.
• The camera username and password are correct.
• ONVIF is enabled on the camera if you expect automatic ONVIF discovery.
• The camera's stream codec and profile are supported by the client you are using.
• If using RTSP manually, the stream URL is for the exact camera model/profile.
• Guest Wi-Fi, VLAN rules, firewalls, or client isolation are not blocking the connection.
• The camera firmware is current enough for the features and security mechanisms you intend to use.

Bottom line

ONVIF is the broader interoperability layer; RTSP is a streaming-session protocol. They commonly complement each other. For Security Eye, try ONVIF/UPnP network discovery first because it can simplify setup. If the device is not discovered, use the manual camera setup information provided by the manufacturer and verify the stream with the connection test.