Get a Public RTSP Stream onto a Website Without Custom Development.

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.

Play a Public RTSP Stream

Paste a public RTSP or RTSPS URL. RTSP.RUN will try to play it in the browser and show whether it is usable on a website.

Works for publicly reachable RTSP/RTSPS streams. Before you start, you can review the deployment assessment or the RTSP URL guide.

How to find an RTSP URL
  • For public websites and client websites
  • Play first, then place it on the site
Marshall Golf Club

Verified Use Cases

Where Live Video on a Website Actually Helps

The biggest value appears where people need to see current conditions or make a fast decision. That is where live video earns its place on the website.

Destinations and venue operators

Helps people decide whether to come or book

For beaches, golf clubs, and leisure sites, a live view reduces uncertainty before the visit. People do not see a curated gallery. They see the real situation right now.

  • faster decisions about coming, booking, or postponing
  • more trust than static copy and older photos
  • more reasons to return to the site again

Examples

Lido Beach Cervia Marshall Golf Club Kraina Dobrej Energii

Public and information websites

Helps people quickly understand what is happening on site

For marinas, airfields, or traffic portals, the value is practical utility. People get a current visual overview without another app, and the website becomes genuinely useful.

  • a quick overview before travel, arrival, or another decision
  • more practical value for visitors and the public
  • a reason to come back for up-to-date information

Examples

Bay City Yacht Club Aeroclub du Quercy P-SAT / Palindo Traffic Monitoring

Agencies and partners

Helps deliver live video to a client website without wasted detours

When you are solving a specific client assignment, you need to know quickly whether this is the right approach, what is still missing, and what the next step should be.

  • faster decisions without avoidable extra development
  • a clearer next step for your team and the client
  • less risk of heading down the wrong path

Related pages

For agencies Camera on a website Deployment assessment

Do You Already Have a Public Camera URL?

If yes, play it right away. If you are still unsure whether this is the right path for your website or your client, get a recommendation for the next step first.

I have the camera URL

I want to play it now

I need to see whether the camera plays in the browser and can be used on a website.

Works for publicly reachable RTSP/RTSPS streams. Before you start, you can review the deployment assessment or the RTSP URL guide.

I need to decide first

I want to confirm whether this is the right path first

I need to clarify whether this approach fits, what is still needed, and what the next step should be.

This is useful when you are working on a client website or a bigger public launch.

You quickly get clarity on whether this is the right path and what should happen next.

Get a recommended next step

Is It a Good Fit for Your Use Case?

RTSP.RUN makes sense when you need to get a publicly reachable camera into a browser and, if needed, onto a website. If you are building a broader video system, a different path is usually better.

It makes sense when

  • you need to play a public RTSP or RTSPS stream in a browser quickly
  • you want to place live video on a website without building your own player
  • you already have the public stream URL or know who can provide it
  • you understand that the stream must be reachable from the public internet

It is not a good fit when

  • the camera must not be publicly reachable from the internet
  • you need recording, archive, analytics, or a full VMS
  • you are looking for an internal CCTV system or a stronger compliance layer
  • you expect a ready-made consumer product for home users
Requirements and limits Check deployment suitability
Place a camera on a website Deployment assessment Agency rollout support

Frequently asked questions about playing the stream

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 an RTSP URL

Only for publicly available RTSP/RTSPS streams. Without recording and analytics.

Play RTSP stream Deployment assessment