RTSP URL: Find Your IP Camera Stream (2026)

Albert BarnosellEditor and publisher of Tecnoyfoto

Updated August 5, 2026 · Brand paths verified against current manufacturer documentation.

An RTSP URL is the local network address used by VLC, an NVR, Frigate or Home Assistant to open an IP camera’s live stream. In most cases you need four things: the camera’s IP address, RTSP port, stream path and a camera account. The exact path depends on the brand and sometimes the model.

Quick answer: the RTSP URL format

rtsp://USERNAME:PASSWORD@CAMERA_IP:554/STREAM_PATH

Example with placeholders: rtsp://USERNAME:PASSWORD@192.168.1.120:554/Streaming/Channels/101. Do not paste real credentials into websites, comments or screenshots. Use the safe builder below to obtain the structure, then enter or replace the credentials locally in your player.

RTSP URLs by camera brand

These are the most common current paths. They are starting points, not a guarantee for every model or firmware. Enable RTSP or ONVIF in the camera first when the manufacturer requires it, and reserve its IP address in your router so the URL does not change.

Brand	Main stream path	Sub-stream path	Important note
Hikvision / HiLook	`/Streaming/Channels/101`	`/Streaming/Channels/102`	The last two digits select main stream 01 or sub-stream 02.
Dahua	`/cam/realmonitor?channel=1&subtype=0`	`/cam/realmonitor?channel=1&subtype=1`	Channels start at 1. The default RTSP port is normally 554.
Reolink	`/Preview_01_main`	`/Preview_01_sub`	RTSP/ONVIF ports are disabled by default on many models. NVR, Home Hub and multi-lens paths can differ.
TP-Link Tapo	`/stream1`	`/stream2`	Create a separate Camera Account in the Tapo app. Most battery models do not support RTSP.
Amcrest IP camera	`/cam/realmonitor?channel=1&subtype=0`	`/cam/realmonitor?channel=1&subtype=1`	Amcrest NVR/DVR paths can use a different format.
Axis	`/axis-media/media.amp?camera=1`	Model/profile dependent	The endpoint accepts parameters for codec, resolution and transport.

Paths checked August 5, 2026. Preserve capitalization: RTSP paths can be case-sensitive.

Tapo dual-lens exception: on current examples such as the C246D and C840, the wide lens uses stream1/stream2, while the telephoto lens uses stream6/stream7. For EZVIZ, Foscam and white-label cameras, paths vary enough that the model manual or ONVIF discovery is safer than a single universal URL.

Manufacturer references: Hikvision, Dahua, Reolink, Tapo, Amcrest and Axis.

Practical ONVIF and RTSP integration with Home Assistant.

What RTSP does—and what it does not do

RTSP (Real Time Streaming Protocol) is the control layer for a media session. It handles actions such as setup, play and teardown; RTP usually carries the actual video and audio packets. This separation is why RTSP can provide low latency without being a video codec itself.

The URL identifies the camera, port and requested stream, but it does not determine image quality on its own. Resolution, frame rate, bitrate, H.264/H.265 codec and audio settings come from the selected camera profile. If a URL opens but the quality is wrong, adjust that profile in the camera or choose its other stream.

How to find your camera’s RTSP URL

1. Confirm that the camera supports RTSP

Search the model’s specifications for RTSP or ONVIF. Cloud-only and many battery-powered cameras cannot maintain a continuous third-party stream. Do not assume that two cameras from the same brand behave identically.

2. Enable RTSP or ONVIF

Open the manufacturer’s app or camera web interface and look under Network, Advanced, Server Settings or Port Settings. Reolink requires the RTSP/ONVIF switches on many models; Tapo requires a separate Camera Account rather than your cloud-login password.

3. Find and reserve the camera IP

Check the router’s connected-device or DHCP list, then create a DHCP reservation. A reservation is usually easier to maintain than setting a manual address inside the camera. Hostnames such as camera.local can work, but an address reservation is more predictable for an NVR.

4. Choose main stream or sub-stream

The main stream gives the highest resolution and bitrate, ideal for recording. The sub-stream reduces bandwidth and decoding load, making it useful for dashboards, mobile previews and multi-camera grids. A common setup records the main stream while using the sub-stream for detection or live tiles.

Safe RTSP URL builder

This builder runs locally in your browser. It asks only for an IP address or hostname, port and brand preset—never for your real username or password. The result deliberately contains USERNAME:PASSWORD placeholders.

URL structure:

Replace the placeholders only on your trusted local device. Some players let you enter credentials in a separate authentication dialog.

Test the RTSP stream in VLC

Connect the computer to the same local network as the camera.
Open VLC and choose Media → Open Network Stream or press Ctrl+N.
Paste the complete RTSP URL. Enter the camera account when VLC requests it, if supported.
Select Play. Allow several seconds for a high-resolution stream to start.

If VLC works but your NVR or Home Assistant does not, the URL is probably correct. Check the target application’s transport, codec and authentication settings next. H.265 can be more efficient but is less universally supported than H.264.

Using the stream in Home Assistant, Frigate or an NVR

Validate the URL in VLC first, then add it to the destination system. For Frigate or a multi-camera NVR, a practical design is to record the main stream and use the sub-stream for detection. This reduces CPU/GPU decoding work without sacrificing recorded detail. Home Assistant dashboards also tend to start faster with the sub-stream.

Keep credentials outside configuration files whenever the application supports a secret store or protected credential field. If a service needs the complete URL, restrict access to that configuration and its backups. Our guide to protecting Home Assistant passwords with secrets.yaml explains the same principle for smart-home configuration.

RTSP commonly runs over UDP for minimum latency or TCP for easier firewall traversal and more reliable delivery on imperfect networks. If the picture breaks up despite adequate bandwidth, try RTSP over TCP in the client before lowering resolution.

RTSP vs ONVIF: use both when possible

RTSP controls a media streaming session; RTP normally carries the audio and video. ONVIF is a broader interoperability standard that can discover the camera, retrieve profiles and stream URIs, receive events and expose PTZ controls. They are complementary rather than competing technologies.

For a new camera in 2026, look for ONVIF Profile T. ONVIF will end support for new Profile S conformance submissions on March 31, 2027; existing Profile S equipment will continue to work, but Profile T adds modern authentication options, H.265 and richer capabilities. Check the exact model in the official ONVIF conformant-products database instead of trusting a marketplace badge.

RTSP security: what actually matters

The RTSP standard includes authentication and RTSP over TLS (rtsps://), but many consumer cameras expose a conventional RTSP/RTP stream without transport encryption. Treat camera video and credentials as sensitive.

Never expose port 554 directly to the internet. Use a VPN for remote access. See our DNS and VPN guide.
Create a dedicated viewer account with the minimum permissions supported by the camera.
Use a strong unique password and current firmware. Do not weaken the password merely to make it fit a URL.
Put cameras on an isolated network or VLAN. Our home network segmentation guide explains the design.
Prefer RTSPS, HTTPS transport or ONVIF Profile T when both endpoints genuinely support them.

If a password contains reserved characters such as @, :, # or %, the user-info portion may require percent-encoding. A better option, when available, is to let the player request credentials separately so they do not sit in the URL, clipboard or recent-items history.

Troubleshooting: why an RTSP URL does not work

Symptom	Most likely checks
Connection refused	Enable RTSP, confirm the port, test from the same LAN and check the camera firewall.
401 / repeated login	Use the camera account—not necessarily the cloud account—and check reserved characters or account permissions.
Timeout	Verify the current IP, DHCP reservation, VLAN rules and Wi-Fi signal. Do not troubleshoot through an internet port forward.
Audio but no video	Try the sub-stream or H.264. The client may not decode the camera’s H.265 profile.
Stuttering or delay	Use Ethernet, reduce bitrate/frame rate, try RTSP over TCP and use the sub-stream for dashboards.
Works in VLC only	Review the NVR/app transport, codec, authentication and channel settings; the URL itself is already validated.

Frequently asked questions

Can I open an RTSP URL in a web browser?

Usually not directly. Standard browsers do not natively play most RTSP streams. Use VLC, an NVR, a VMS or a gateway that converts the stream to a browser-friendly format.

Is the RTSP port always 554?

554 is the standard and most common port, but it can be changed and some devices use another default. Confirm it in the camera’s network or port settings.

Why does my battery camera not provide RTSP?

A continuous local stream prevents the camera from sleeping and drains its battery. Some wired-doorbell modes are exceptions, but support must be verified per model.

Should I record the main stream or the sub-stream?

Record the main stream when image detail matters. Use the sub-stream for previews, detection or multi-camera dashboards when you need lower bandwidth and decoding load.

An RTSP URL remains one of the simplest ways to keep camera video local, low-latency and independent of a cloud subscription. Start with the verified brand path, test it in VLC, and then integrate the same stream into your trusted NVR or smart-home system.