How to find the correct RTSP or RTSPS URL

Use this page when you already have the camera but still do not know the exact URL format, the correct stream path, or whether the camera is truly reachable from the internet.

The goal is to get you from a camera model and a local preview to a concrete public URL you can paste straight into rtsp.run. If one of the steps below is still missing, the problem is not in the player yet. It is in the input or in public reachability.

What to prepare before you start looking for the URL

  • the camera model, or at least the brand and exact device name
  • access to the web admin, NVR, or app where RTSP is often enabled
  • the username and password intended for RTSP access
  • a way to test the camera from a different network than the one it is physically connected to
Play the stream Deployment assessment

Three things must be true before rtsp.run can help

The URL format must be correct

Knowing the camera IP is not enough. You also need the right protocol, port, and the exact stream path.

The camera must be reachable from the public internet

The camera has to be accessible from a different network than the one it runs on. Local playback at home is not enough.

The public setup must be intentional and safe

A public stream is a conscious decision. You need a separate account, a strong password, and a clearly limited access scope.

What a correct RTSP or RTSPS URL looks like

The key is to distinguish the protocol, credentials, host, port, and the exact stream path. The IP address alone is not enough. Without the correct stream path, the camera still will not play.

What each part means

  • `rtsp://` or `rtsps://` is the protocol.
  • `USERNAME:PASSWORD` are the credentials for RTSP access, not necessarily the camera admin account.
  • `HOST` is a public IP address or DDNS hostname, not a local `192.168.x.x`, `10.x.x.x`, or `172.16–31.x.x` address.
  • `PORT` is often `554`, but it can be different.
  • `STREAM_PATH` is the exact path for the main or secondary stream and differs by brand and model.

Basic format without credentials

Use this only if the camera or RTSP layer truly does not require a username and password.

Typický tvar
rtsp://HOST:554/STREAM_PATH
  • HOST can be a public IP or a DDNS hostname.
  • Port `554` is common, but not mandatory.
  • Without the correct stream path, the URL still will not work.

The most common format with username and password

This is the usual variant for IP cameras and NVRs that require a dedicated RTSP login.

Typický tvar
rtsp://USERNAME:PASSWORD@HOST:554/STREAM_PATH
  • Use an account that actually has access to the stream.
  • Do not use the admin account unless there is no other option.
  • The public port may differ from the internal camera port.

The safer variant over RTSPS

Use this only if the camera truly supports it. Not every device understands `rtsps://`.

Typický tvar
rtsps://USERNAME:PASSWORD@HOST:322/STREAM_PATH
  • The port is often different from `554`.
  • If the vendor does not explicitly document RTSPS, do not assume that changing the protocol is enough.
  • If RTSPS is not available, handle security through a strong password and a narrowly limited access scope.

How to find the URL by manufacturer

The examples below are common patterns, not universal truth for every model. First confirm that the camera supports RTSP at all and whether the stream must be enabled first in the admin panel or app.

Hikvision

A common format for the main stream. The secondary stream often ends with `102` instead of `101`.

Častý vzor
rtsp://USERNAME:PASSWORD@HOST:554/Streaming/Channels/101
  • Look for a Video, Stream, or RTSP section.
  • Check main versus secondary stream and the channel number.

Dahua and common OEM variants

A typical format for Dahua and for some brands that reuse Dahua-based models.

Častý vzor
rtsp://USERNAME:PASSWORD@HOST:554/cam/realmonitor?channel=1&subtype=0
  • `subtype=0` is usually the main stream, `subtype=1` the secondary one.
  • On NVRs, the channel number may depend on the wiring.

Axis

Axis often uses a shorter and cleaner stream path than many other manufacturers.

Častý vzor
rtsp://USERNAME:PASSWORD@HOST:554/axis-media/media.amp
  • Also verify the stream profile and any custom RTSP port.
  • If the URL does not work, check the documentation for the exact model.

Reolink

Reolink often distinguishes the main and secondary stream directly in the path name.

Častý vzor
rtsp://USERNAME:PASSWORD@HOST:554/h264Preview_01_main
  • The secondary stream is often marked `sub` instead of `main`.
  • RTSP support differs by model, so do not start with a generic forum post.

Tapo / TP-Link

With Tapo, RTSP often has to be enabled first in the app or in NVR mode.

Častý vzor
rtsp://USERNAME:PASSWORD@HOST:554/stream1
  • Not every Tapo model supports standard RTSP.
  • If the device is cloud-only, you will not get a public RTSP URL out of it.

Uniview, Amcrest, Annke, Ezviz, and others

For these brands, both support and the exact stream path vary by model and firmware.

Častý vzor
Do not rely on one universal format unless the exact model is confirmed.
  • First confirm that the device supports standard RTSP.
  • Then look for the official vendor guide or an exact pattern for the specific model.

How to make sure the camera is reachable from the internet

This is the most common blocker. The camera works at home in the local app or in VLC, but rtsp.run cannot see it because it is not reachable from the public internet.

Minimum public setup

1. Confirm the correct URL inside the local network

Before you deal with the internet, confirm the correct URL format and stream path inside the local network or in the vendor documentation.

2. Give the camera a stable local address

Use a DHCP reservation or a fixed local IP on the router so port forwarding does not break after a restart.

3. Expose the RTSP port from the internet

Map a public port on the router to the local RTSP port of the camera or NVR. The public port does not have to match the internal one.

4. Use a public IP or DDNS hostname

The final URL must use a public IP or DNS name, not a local LAN address.

5. Test it from a different network

Use mobile data or another internet connection. Testing from the same Wi-Fi proves almost nothing.

Where it most often breaks

  • the camera only works through the vendor app or cloud, not through standard RTSP from the internet
  • your ISP uses CGNAT and you do not have a real public IPv4 address
  • port forwarding points to the wrong internal host or port
  • the DDNS name resolves correctly, but the public port is closed or blocked

How to tell that you are ready for rtsp.run

  • the final URL uses a public hostname or public IP
  • the username and password in the URL are valid for RTSP access
  • the port is reachable from the internet from a different network
  • the camera returns a real live stream, not just a redirect into the vendor app

If you do not have a public IP

  • DDNS alone is not enough. If you are behind CGNAT, port forwarding from the internet never reaches the camera.
  • You need a real public IP from your ISP or another public layer you can expose safely.
  • If you do not want to solve this, you will not use rtsp.run for that camera in public mode.

How to do it safely

A publicly reachable camera is a conscious decision. Do not expose more to the internet than you really need for the live stream.

What to do

  • create a separate user only for RTSP playback, not the admin account
  • use a long unique password and do not reuse the admin password
  • if the camera supports `rtsps://`, prefer it over unencrypted `rtsp://`
  • consider a separate network or VLAN for cameras you expose to the internet
  • expose only what is needed for the stream, not the full web admin of the camera

What to avoid

  • do not expose a camera that is meant only for internal CCTV or sensitive operations
  • do not assume the vendor cloud or mobile app automatically means public RTSP
  • do not use default vendor accounts or a weak password just because it is "only a camera"
  • do not publish the camera before you are clear about who should have access and why

Before you paste the URL into rtsp.run

If you can answer yes to everything below, it makes sense to move straight to stream playback.

  • I have the complete URL in `rtsp://` or `rtsps://` format.
  • I am using a public hostname or public IP, not a local address.
  • I know the stream is reachable from a different network than the one the camera runs on.
  • I am using an account intended for RTSP access, not full admin access to the camera.
  • I am sure the camera is supposed to be publicly reachable and that this operating model makes sense.
Play the stream Deployment assessment

Common questions about the RTSP URL and public reachability

Resolve these questions before you start looking for the problem in the player itself.

A correct URL has a complete format, typically rtsp://USERNAME:PASSWORD@HOST:PORT/STREAM_PATH or rtsps://.... Knowing only the camera IP is not enough. You also need the right port and, above all, the correct stream path.

In rtsp.run, use a public hostname or public IP address, not a local 192.168.x.x, 10.x.x.x, or other internal address.

Start with the official documentation for the exact model, the web admin of the camera, the NVR settings, or the app where RTSP often has to be enabled first. The most reliable combination is the exact model plus the official vendor guide.

If you only have the brand name and not the exact model, expect wasted time guessing.

No. Seeing the camera in the vendor app or cloud does not mean you have a standard RTSP stream reachable from the internet.

For rtsp.run, you need a concrete public RTSP or RTSPS URL that you can open outside the local network, not just access through a closed vendor app.

Not by itself. DDNS only gives you a name instead of a changing IP address. You still need a real public IP, correct forwarding, and an open port pointing to the right camera or NVR.

If you are behind CGNAT, DDNS alone will not help because traffic from the internet still cannot reach your camera.

Always test from a different network than the one the camera runs on, usually mobile data or another connection. A test from the same Wi-Fi can be misleading.

If the final URL uses a public hostname or public IP, the correct port, and valid RTSP credentials, you are close. If it only works at home or only leads to a local address, you are not ready for rtsp.run yet.

The public RTSP model is not a good fit for internal CCTV, closed company networks, recording, analytics, or situations where the camera must not be exposed to the internet at all.

If the real requirement is internal-only access, recording, or a stricter security and operations model, open the deployment assessment instead of forcing this public model where it does not belong.