The camera app that came with your IP camera is rarely the software you actually want to run it on. Maybe you want local recording with no cloud subscription, smart object detection through Frigate, or a single dashboard across mixed brands in Blue Iris. The bridge that makes all of that possible is RTSP, the Real Time Streaming Protocol, and almost every IP camera quietly exposes its video over it whether the marketing mentions it or not.

Quick Answer

You access a camera's RTSP stream by building a URL from four pieces: the login credentials, the camera's IP address, the RTSP port (usually 554), and a brand-specific stream path. A typical result looks like rtsp://admin:[email protected]:554/Streaming/Channels/101. Test that URL in VLC first, and once it plays, paste the same URL into Frigate, Blue Iris, or any NVR software.

What RTSP Is And Why It Matters

RTSP is the standard way IP cameras hand their live video to other software. It is not a recording format or an app; it is a session protocol that lets a client ask the camera to start sending its stream and then carries that stream over the network. Because it is an open standard, any recorder that speaks RTSP can pull from any camera that serves it, regardless of brand.

That is the whole point. Instead of being locked into the manufacturer's app and cloud, you point open-source or third-party software at the RTSP stream and own the footage on your own hardware. Frigate, Blue Iris, Synology Surveillance Station, and Home Assistant all work this way, using the camera's RTSP feed as their source.

Main Stream Versus Sub-Stream

Most cameras serve at least two streams. The main stream is full resolution at full frame rate, ideal for recording the footage you might actually need later. The sub-stream is a lower-resolution, lower-bitrate version that is far lighter on your CPU, which is exactly what you want for live detection and motion analysis. A well-configured recorder usually records the main stream and runs detection on the sub-stream, so plan to grab both URLs while you are at it.

Building Your RTSP URL Step By Step

Work through these five pieces in order and you will end up with a URL that just works.

  1. Find the camera's IP address. Check your router's connected-devices list, or use the camera's own app, which almost always shows the local IP somewhere in its settings.
  2. Confirm the RTSP port. It is 554 on the vast majority of cameras. A few use a different port, so check the camera's web interface if 554 does not respond.
  3. Get the credentials. This is the username and password you set when you first configured the camera, not your cloud account login. Many recorders recommend creating a dedicated viewer account on the camera for this.
  4. Find the brand's stream path. This is the part that varies. Hikvision uses paths like /Streaming/Channels/101, Dahua uses /cam/realmonitor with channel and subtype parameters, and Reolink commonly uses /h264Preview_01_main for the main stream and _sub for the sub-stream.
  5. Assemble and test. Combine everything as rtsp://user:pass@ip:port/path and open it in VLC under Media, then Open Network Stream. If it plays, the URL is correct.

Finding The Stream Path When The Manual Is Useless

The stream path is where most people get stuck, because manufacturers document it inconsistently. There are three reliable ways to find it. First, check the camera's own web interface; many list the RTSP path directly under their network or stream settings. Second, use ONVIF discovery, which is a companion standard most cameras support that lets software find the camera and its streams automatically without you typing a path at all. Third, look up the exact model in a community RTSP path database, since the format is almost always consistent across a brand's range.

ONVIF is worth understanding here because it complements RTSP rather than replacing it. ONVIF handles discovery and control, finding the camera and listing what it offers, while RTSP carries the actual video. Many recorders let you add a camera by ONVIF and then pull its RTSP stream automatically, which saves you building the URL by hand.

Feeding The Stream Into Your Recorder

Once VLC confirms the URL, the rest is straightforward. In Frigate you add the camera under its config file with the RTSP URL as an input, and Frigate can even re-broadcast the feed to other apps as a tidy rtsp://frigate-host:8554/camera-name address. In Blue Iris or Synology you paste the URL into the camera-add dialog. The recorder handles the rest, from continuous recording to motion-triggered clips to object detection, all driven off that one stream you set up.

If you are still choosing cameras and want ones that play nicely with open recorders, a good filter is to look for explicit RTSP and ONVIF support in the spec sheet. Models that list both are the ones that drop straight into third-party software. Evetech's smart home and camera range is a sensible place to compare which devices advertise that compatibility before you buy.

A Few Things That Trip People Up

Wrong credentials are the most common failure, usually because people use their cloud account instead of the camera's local login. Firewalls and VLANs can block port 554 between the camera and the recorder, so confirm the two devices can actually reach each other. Some cameras disable RTSP by default for security, meaning you have to switch it on in the camera's settings first. And if the stream stutters, you are probably pulling the main stream where the sub-stream would do, so swap to the lighter feed for live viewing. To round out a self-hosted setup, the popular accessories list covers the cabling and storage a local recorder needs.

Frequently Asked Questions

Does every IP camera support RTSP?

Most do, but not all. The vast majority of standalone IP cameras expose an RTSP stream, while some cloud-only consumer cameras lock their feed to the manufacturer's app on purpose. If RTSP and ONVIF support matter to you, check the spec sheet before buying.

What is the default RTSP port?

Port 554 is the standard and works on the large majority of cameras. A small number use a different port, so if 554 does not respond, check the camera's web interface for the correct one.

Why does my RTSP URL fail in VLC?

The usual causes are wrong credentials, an incorrect stream path for that brand, RTSP being disabled on the camera, or a network rule blocking the port. Check those four in order, since the URL itself is usually correct once each piece matches the camera.

What is the difference between the main stream and the sub-stream?

The main stream is full resolution and frame rate for quality recording, while the sub-stream is a lighter version for live viewing and motion detection. Recording the main stream and analysing the sub-stream is the standard way to keep CPU use sensible.

Do I need ONVIF if I already have the RTSP URL?

No. If you have a working RTSP URL, you can use it directly. ONVIF simply makes setup easier by discovering the camera and its streams automatically, so it is convenient rather than required.

Planning a self-hosted camera setup with no cloud subscription? Choose hardware that exposes RTSP and ONVIF so it drops straight into the recorder you want. Browse the Evetech smart home and camera range and build a system you actually control.