Help Based on What You Need Right Now

Need to play a stream, place a camera on a website, or quickly decide whether this is the right path? Start with the shortest useful route.

This page is for website owners, public information websites, agencies, and delivery teams working on a client rollout.

Start from your situation

  • Already have a public RTSP or RTSPS URL? Start by playing the stream in the browser.
  • Need to put the camera on a website? Go straight to the website workflow.
  • Working on a client, a bigger rollout, or an uncertain use case? Open deployment assessment or agency support.

Start here

The shortest paths when you already have a concrete task and need to move quickly.

Online RTSP Player for IP Cameras | Play RTSP in a Browser | rtsp.run

Paste a public RTSP or RTSPS URL and quickly see whether the stream plays in the browser and is ready for a public website or a client website.

Deployment assessment

Use this when you still need to decide whether this is the right solution and what the next step should be.

Agency and delivery support

For web teams and agencies that need to get live video onto a client website with fewer detours.

Requirements, errors, and decisions

Use these when you need the right RTSP URL, need to understand an error, or want to clarify the conditions first.

How to find an RTSP URL

Use this when you know you have the camera but still need the right URL or are unsure about public reachability.

Why the stream does not start

The most common errors and what to check when the camera does not open in the browser.

How to go from camera to website

The order of steps from the first playback check to placing the camera on a website.

Frequently asked questions about playing the stream

Here you can find what a public RTSP or RTSPS address should look like, what the most frequent messages from the application mean, and when RTSP.RUN is the right path for your website.

You need a direct public RTSP or RTSPS address to verify. A link to a manufacturer viewer, cloud sharing page, or internal address that only works on the local network is not enough.

Typical format:

rtsp://username:password@camera-address-or-domain:554/stream-path

If you are a website operator, agency, or integrator, ask the camera supplier for this exact address. If you are a technical administrator, also verify that the stream is reachable from the public internet.

First you check if the stream is reachable and if it really plays in the browser. Only then does it make sense to deal with web embedding, client handoff or the next rollout step.

When playback works, you can proceed to embed. If not, the application returns a specific message and you know that the problem is with the stream, address or public availability, not the site itself.

This message means that the stream did not pass the first start. Most often, the problem is in one of the following areas:

  • the address is incomplete or in the wrong form,
  • the camera is not available from the public Internet,
  • the credentials do not match,
  • the target stream or the host refused the connection.

Mainly follow the specific message returned in the application, for example "The RTSP address is invalid or incomplete", "Target stream not found" or "The guest stream cannot be reached from the public internet".

Yes. The current product flow assumes that the camera or stream is publicly accessible from the Internet. If the camera works only in the local network, in the manufacturer's viewer or behind a VPN, the default path in RTSP.RUN is not suitable for it.

This is especially important for website operators, agencies and technical gatekeepers: first confirm public availability, then solve the web, design or embed.

RTSP.RUN is for public live playback in a browser and eventual web embedding. It's not the way to go if you actually need:

  • internal CCTV or non-public monitoring,
  • recording, archiving or analytics,
  • access control, VMS or enterprise governance layer,
  • a consumer plug-and-play solution without working with an RTSP address.

In other words: yes for a public live camera on the web, no for a wider camera system.

In both cases, the problem is in the address itself. Most often, the stream path is wrong, the channel is wrong, or the full URL is not in the right format.

Typical format:

rtsp://username:password@camera-address:554/stream-path

Examples by brand:
Hikvision: rtsp://user:pass@camera-address:554/Streaming/Channels/101
Dahua: rtsp://user:pass@camera-address:554/cam/realmonitor?channel=1&subtype=0
Axis: rtsp://user:pass@camera-address:554/axis-media/media.amp

If you are an agency or website operator and someone else supplied the address, go back to the camera vendor and ask for the exact public RTSP or RTSPS address, not just a confirmation that the camera can stream.

How to find out the RTSP address