RTSP is the protocol that carries a camera’s video stream, while ONVIF is the standard that lets devices from different makers discover each other, be configured and hand out that stream, so they are complements and not rivals. A camera that supports ONVIF will tell software where its RTSP address is; RTSP then delivers the pictures. In the RTSP vs ONVIF question, knowing the difference saves hours when you connect cameras to a recorder or to analytics. If you are planning to add detection to cameras you already own, our guide to AI cameras explains why open streams are the key requirement.
Key takeaways
- RTSP (Real Time Streaming Protocol) was published as RFC 2326 in 1998 and uses TCP port 554 by default.
- ONVIF was founded in 2008 by Axis, Bosch and Sony to standardize how IP security devices work together.
- ONVIF defines profiles: S for live streaming, T for advanced streaming including H.265, G for storage and retrieval, and M for analytics metadata.
- RTSP moves the video. ONVIF handles discovery, configuration and control, and tells you the stream address.
- Most existing IP cameras can feed analytics without replacement if they expose either one.
RTSP vs ONVIF: What Is the Difference?
RTSP is a transport protocol and ONVIF is an interoperability standard. They work at different layers, which is why a camera can be described as supporting both without any contradiction.
What RTSP does
RTSP lets a client ask a camera to start, pause or stop a stream. The video itself usually travels over RTP, and many cameras expose an address that looks like a web link beginning with rtsp://. The protocol was defined in RFC 2326 in 1998 and revised as RTSP 2.0 in 2016, though most cameras in the field still use the first version. By default it listens on TCP port 554, but the exact port and path vary by manufacturer and should be checked in the camera’s own documentation.
What ONVIF does
ONVIF is a set of specifications maintained by an industry group. It defines how a client finds cameras on a network, reads their capabilities, changes settings such as resolution, and requests a stream address. A recorder that follows ONVIF can add a camera from another brand without a custom driver. The standard is organized into profiles, each covering a set of features, so that you can check compatibility by profile letter and not by product name.
RTSP vs ONVIF Compared
| Question | RTSP | ONVIF |
|---|---|---|
| What is it? | A streaming protocol | An interoperability standard |
| Year introduced | 1998 (RFC 2326) | 2008 (founding of ONVIF) |
| Carries video? | Yes, controls the stream | No, it provides the stream address and control |
| Finds cameras on the network? | No | Yes, through discovery |
| Configures settings? | No | Yes, such as resolution and codec |
| Default port | TCP 554 | Set by the device, often an HTTP port |
| Typical use | Pull a live feed into any player or analytics tool | Add a camera to a recorder or VMS from any brand |
What Do the ONVIF Profiles Mean?
A profile is a promise about features. Choosing cameras and recorders that share the profile you need is more reliable than trusting a generic claim of ONVIF support.
- Profile S covers basic live video streaming and is the profile found on most IP cameras.
- Profile T adds support for advanced streaming, including H.265 compression.
- Profile G covers recording, storage and retrieval, which matters when a recorder and camera share storage duties.
- Profile M covers analytics metadata, so detection results can be shared between devices.
Compliance varies in practice. Some manufacturers reserve certain functions for their own software even when a camera claims conformance, so test the specific features you need. For how this affects recorder choice and vendor lock-in, see our guide to DVR vs NVR.
Which Do You Need to Connect Cameras to Analytics?
You need a stream address, and that is what both give you. If a camera exposes an RTSP address you can read the video directly. If it supports ONVIF, software can find the camera, authenticate and request the address automatically. In practice a camera that supports ONVIF Profile S or T nearly always offers RTSP as well. Our guide to the RTSP camera shows how to build the stream address.
A short checklist before you connect
- Confirm the camera streams over RTSP or supports ONVIF Profile S or T.
- Note the resolution and frame rate you plan to use, typically 1080p to 4K at 15 to 30 frames per second.
- Check the codec: H.264 or H.265. Our comparison of H.265 vs H.264 covers the trade-offs.
- Use a dedicated read-only account for the analytics service, and keep the camera network separate from the office network.
- Test one camera end to end before you add the rest.
How Argu uses these standards
Argu’s Vision Agents platform connects to existing RTSP or ONVIF Profile S, T or G streams, IP cameras and NVRs, rather than requiring detector-specific hardware. Feeds run at standard 1080p to 4K and 15 to 30 frames per second over H.264 or H.265. That is why many sites can add detection such as intrusion detection without replacing a camera. Equipment sourcing rules matter too, so if you buy new cameras see our overview of NDAA compliance.
Why Does a Camera Connect in One Tool but Not Another?
When a stream works in a recorder but fails in a second tool, the cause is usually one of 4 things, and each takes a few minutes to check.
The 4 usual causes
- Wrong path or port. The default RTSP port is 554, but the stream path differs by manufacturer, and a path that works on one brand returns an error on another.
- Credentials. Some cameras require a separate stream user, and an ONVIF account may not be the same as the web interface account.
- Codec or profile mismatch. A client that decodes only H.264 cannot show an H.265 stream, which usually appears as a black picture with no error message.
- Connection limits. Many cameras allow only a small number of simultaneous streams, so a recorder, a viewer and an analytics service can run out of slots.
A habit that prevents most problems
Keep a simple sheet for each camera with its model, firmware version, stream address, codec, resolution and the profile it supports. When something changes after an update, you can see what moved. It also makes onboarding a new analytics service a matter of copying a row, not rediscovering each device.
Frequently Asked Questions
Is RTSP the same as ONVIF?
No. RTSP is a protocol that streams video. ONVIF is a standard that defines how devices discover each other, configure settings and share stream addresses.
Does ONVIF use RTSP?
Usually yes. An ONVIF client asks the camera for its stream address, and the address it receives is normally an RTSP address.
Which ONVIF profile do I need?
Profile S for basic live streaming, Profile T if you need H.265 or advanced streaming, Profile G for recording and retrieval, and Profile M for analytics metadata.
What port does RTSP use?
TCP port 554 by default, although many cameras use a different port or path. Check the manufacturer’s documentation.
Can I use analytics with cameras that do not support ONVIF?
Often yes, if they provide an RTSP stream. Without either, you may need an encoder or a replacement camera.
Do I need new cameras for AI video analytics?
In most cases no, as long as the existing cameras stream in a standard format and offer enough resolution for the task.
If you are not sure what your cameras expose, a short stream check usually settles it. Talk to Argu about the cameras and recorders you already run.
Last updated: October 2026
