An RTSP camera is an IP camera that offers its live video through the Real-Time Streaming Protocol, so any compatible recorder, player or analytics platform can pull the stream from a network address, usually on port 554. That single fact explains why RTSP shows up in almost every camera datasheet: it is the common doorway that lets a camera from one maker work with software from another. Argu’s vision agents use that doorway to add AI to cameras a site already owns, with no camera swap.
Key takeaways
- RTSP was developed by RealNetworks, Netscape and Columbia University, and was published as RFC 2326 in 1998. RTSP 2.0 followed as RFC 7826 in 2016 and is not backwards compatible with version 1.0.
- The default RTSP port is 554, for both TCP and UDP, and the video itself is normally carried by the Real-time Transport Protocol (RTP).
- An RTSP address has four parts you must get right: the scheme rtsp://, the login, the camera IP address with its port, and a stream path that differs by manufacturer.
- Most security AI platforms, Argu included, read RTSP or ONVIF Profile S/T/G streams at 1080p to 4K and 15 to 30 frames per second.
What Is an RTSP Camera?
An RTSP camera is a network camera that answers requests in the Real-Time Streaming Protocol. The protocol works like a remote control for a media stream. A client asks the camera to describe its streams, sets one up, and then sends commands such as play and pause, while the video itself travels separately. According to Wikipedia’s article on RTSP, most RTSP servers send that video with RTP, together with the Real-time Control Protocol (RTCP).
The first RTSP drafts were submitted to the IETF in October and December 1996, and the standard appeared as RFC 2326 in 1998. Because the protocol is more than 25 years old and openly documented, nearly every IP camera, NVR and video management system supports it, which is why a mixed estate of cameras bought years apart can still share one recording or analytics layer.
RTSP is not the same as ONVIF
RTSP moves the video. ONVIF is a separate industry standard for discovering cameras and controlling them in a common way. Many cameras support both, and the two are often used together. Our guide to RTSP vs ONVIF explains when each one matters.
How Is an RTSP Camera URL Built?
An RTSP camera URL has the form rtsp://username:password@camera-ip:554/stream-path. Every part except the stream path is the same on all brands, and the stream path is the part you take from the camera’s own documentation.
| Part of the URL | Typical value | Where it comes from |
|---|---|---|
| Scheme | rtsp:// | Fixed by the protocol |
| Login | username:password@ | An account you create on the camera, not the admin account |
| Host | The camera’s IP address | The camera’s network settings or your DHCP list |
| Port | 554 by default | Camera settings, changed on some sites for security |
| Stream path | Varies by manufacturer and model | The manufacturer’s integration guide |
Cameras usually publish at least two streams. A main stream carries full resolution for recording, and a sub stream carries lower resolution for live viewing. Pick the stream that matches the job: analytics generally work best from a stream at 1080p or higher with a steady frame rate, as covered in our explainer on what bitrate is.
How Do You Connect an RTSP Camera to an NVR or AI Platform?
You connect an RTSP camera by giving the recorder or platform the camera’s RTSP address and login, then confirming that a picture appears and keeps flowing. The same four steps apply whether the receiver is an NVR, a video management system or an AI analytics platform.
Step by step
- Put the camera on a network the receiver can reach, and give it a fixed IP address.
- Create a dedicated viewer account on the camera instead of sharing the admin login.
- Find the stream path in the manufacturer’s documentation, then build the URL.
- Test the URL in a media player first. If it plays there, the camera side is correct.
- Add the URL to the NVR or platform and check that the frame rate and resolution match what you set on the camera.
Why RTSP is the usual way AI is added to existing cameras
An analytics platform that reads RTSP does not need to be installed in the camera. It watches the same stream a recorder would, so a site can add detection without replacing hardware. Argu reads RTSP and ONVIF Profile S/T/G streams at 1080p to 4K and 15 to 30 frames per second, and an operator describes a situation in plain language to turn it into a live agent in about 30 seconds. Our guide to DVR vs NVR shows how recorders and cameras fit together.
Why Does an RTSP Stream Fail or Stutter?
An RTSP stream usually fails for one of five reasons, and each can be checked in a few minutes. A wrong stream path, a wrong login, a blocked port, too little network capacity and a codec the receiver cannot decode cover almost every case.
| Symptom | Likely cause | What to check |
|---|---|---|
| Connection refused or timeout | Port 554 blocked, or wrong IP | Firewall rules and the camera’s address |
| 401 unauthorized | Wrong username or password | The viewer account on the camera |
| 404 not found | Wrong stream path | The manufacturer’s integration guide |
| Picture freezes or smears | Not enough bandwidth or lost packets | Bitrate and the network between camera and receiver |
| Black screen with audio | Codec the receiver cannot decode | H.264 versus H.265 support |
Codec choice also changes storage and bandwidth. If a receiver cannot decode H.265, switching the camera to H.264 usually restores the picture at the cost of a higher bitrate, a trade-off we cover in H.265 vs H.264.
Security basics for RTSP cameras
An RTSP address with a weak password and an exposed port is an open door to a live feed. Keep cameras on a separate network segment, do not forward port 554 to the internet, and change default logins before a camera goes live. Version 2.0 of the protocol is not backwards compatible with 1.0, so confirm which one each device speaks before mixing them.
What Can You Do Once the Stream Is Flowing?
Once a camera’s RTSP stream reaches a platform, the video can be searched and watched by software instead of only recorded. With Argu, an operator can ask a plain-language question about footage with natural language video search, or describe a situation to watch for. Other agents read the same stream for license plates, queues and perimeter events. The camera does not change; only what reads its stream does.
Frequently Asked Questions
What is an RTSP camera?
An RTSP camera is an IP camera that shares its live video through the Real-Time Streaming Protocol. Any recorder, player or analytics platform that supports RTSP can request the stream from the camera’s network address.
What port does an RTSP camera use?
The default RTSP port is 554, for both TCP and UDP. Some installers change it, so check the camera’s network settings if a connection on 554 is refused.
How do I find my RTSP camera URL?
Build it as rtsp://username:password@camera-ip:554/stream-path. The first four parts are standard, and the stream path comes from the manufacturer’s integration guide for that model.
Is an RTSP camera the same as an IP camera?
Not exactly. An IP camera sends video over a network, and RTSP is one common way it offers that video. Most modern IP cameras support RTSP, but a few only offer proprietary streams.
Can I use an RTSP camera with AI video analytics?
Yes. A platform that reads RTSP streams can analyze an existing camera without hardware changes. Argu reads RTSP and ONVIF Profile S/T/G streams at 1080p to 4K and 15 to 30 frames per second.
Is RTSP secure?
RTSP itself does not make a camera safe. Security depends on strong credentials, a separate network segment and never exposing port 554 to the internet.
RTSP is the reason an AI layer can sit on top of cameras you already run. Argu connects to those streams and lets your team describe what to watch for in a sentence. Talk to Argu about the cameras on your site.
Last updated: October 2026
