Play public RTSP streams in your browser and put them on your website.

RTSP.RUN turns a publicly reachable RTSP or RTSPS stream into something you can open in a regular browser. Verify the stream online and get an embed for your website after the playback test succeeds.

No vendor app required Playback verification and embed in one flow

Start with your RTSP URL

Enter a public RTSP or RTSPS URL that is reachable from the internet.

Need help? Check the Frequently Asked Questions section for instructions and examples.

How it works

1. Enter stream URL

RTSP or RTSPS, e.g. rtsp://your-camera

2. We convert it

The stream is made browser-friendly instantly.

3. You watch

Start watching in your browser on any device.

Don't know your RTSP URL?

See working RTSP examples, common errors, and the steps to make your camera reachable from the internet.

Find your RTSP URL

Put a live camera on your website

First verify browser playback, then take the prepared embed code for a company website, storefront, or public page.

Put a camera on your website

Before you use it in production

RTSP.RUN is built for publicly reachable RTSP/RTSPS streams and for live playback or embed, not for internal CCTV, recording, or analytics.

Working on a client or business use case? Contact [email protected].

See what you get before you start

RTSP.RUN first opens a browser player. If the stream works, the same flow gives you an embed-ready output for your website.

Browser output

A live player opens in the browser

rtsp.run / player.html
Preview first
Live player ready for verification
Browser-ready playback Desktop • tablet • mobile
  • Check that the stream loads correctly before you share it anywhere else.
  • Open the same output on desktop, tablet, or mobile.
  • Use the verified stream for direct watching or the next embed step.

Website output

Embed code is ready for your page

Sample iframe
<iframe
  src="https://rtsp.run/embed.html?streamUrl=YOUR_STREAM_ID"
  width="640"
  height="360"
  style="border:0;"
  allowfullscreen
  referrerpolicy="origin">
</iframe>
  • Copy a prepared iframe after successful playback.
  • Use it for a company website, storefront, public camera, or event page.
  • You do not need to build your own browser player for the website.

When RTSP.RUN is a good fit

It works best for people who need to get a publicly reachable IP camera into a browser and, if needed, onto a website without building their own player.

Good fit when

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

Not a fit when

  • the camera is not reachable from the internet or you do not want to expose the stream publicly
  • you need recording, archive, analytics, or a full VMS
  • you need an enterprise compliance layer or a closed internal CCTV platform
  • you expect a plug-and-play consumer tool for a non-technical home user

Built for fast camera access

Live playback in seconds

Paste a public RTSP or RTSPS URL and the stream becomes browser-ready without vendor software.

📱
Works wherever a browser works

Use the same player on phone, tablet, desktop, reception display, or a temporary monitoring screen.

🧩
Share or embed it

Use the player for remote viewing or put a live camera on your website with the built-in embed flow.

Where it makes the most sense

The strongest use cases are the ones where you need a browser-ready output and a clean embed path without building your own video stack.

🏢 Live camera on a company website

Show a storefront, facility, reception area, or outdoor view directly on your website.

🏗️ Construction site or field project

Share a live view of progress with clients, partners, or the public.

📍 Storefront, venue, or event page

Show what is happening right now without a vendor app and without building a custom player.

🧑‍💻 Web integrator delivering for a client

Verify the stream, take the iframe, and finish the rollout on the client website quickly.

Common camera brands and compatibility

RTSP.RUN works best when the camera exposes a standard publicly reachable RTSP or RTSPS stream. These are the brands that appear most often in our help content and real use-case inquiries.

Camera brands mentioned most often

Hikvision Dahua Axis Reolink Tapo / TP-Link Uniview Amcrest Annke Ezviz

What actually determines compatibility

The brand alone is not enough. What matters is whether the specific model exposes the correct RTSP/RTSPS URL and whether the stream is reachable from the internet. If you are unsure, start with the RTSP URL guide or a fit-and-limits check.

Frequently Asked Questions

The RTSP address is the URL your camera uses to share video over the internet. You can find it in the user manual, in the camera settings, or on the manufacturer’s website.

Typical format:

rtsp://user:password@IP-address:554/path_to_stream

Not sure? Search for your camera model together with the phrase RTSP URL or contact the manufacturer.

This is usually caused by an incorrect address, an unreachable camera, or a blocked connection.

  • Make sure the camera is powered on and RTSP is enabled in its settings.
  • For access from the internet, the stream must be publicly accessible (private IPs like 192.168.x.x will not work externally).
  • If the camera is behind a router, set up port forwarding (typically port 554).
  • Check that the connection is not blocked by a firewall or your internet provider.

This error means that the camera does not understand the entered address. Usually, a part of the path that specifies the video channel is missing or incorrect.

Correct address format:

rtsp://user:password@camera_address:554/path_to_stream

Examples by manufacturer:
• Hikvision: rtsp://user:[email protected]:554/Streaming/Channels/101
• Dahua: rtsp://user:[email protected]:554/cam/realmonitor?channel=1&subtype=0
• Axis: rtsp://user:[email protected]:554/axis-media/media.amp

What to do: Check the exact format in your camera’s manual or on the manufacturer’s website – each model uses a different “path”.

The camera responds, but the requested stream path does not exist. The address is almost correct, but the last part (channel/stream) is invalid.

Try these options:

  • Main stream (higher quality): /Streaming/Channels/101
  • Substream (lower bitrate): /Streaming/Channels/102

Examples:
rtsp://user:[email protected]:554/Streaming/Channels/101
rtsp://user:[email protected]:554/Streaming/Channels/102

If you use paths like /live, /h264, or /1 and the camera returns an error, your model simply does not support them. You can find the correct path in the manual or using ONVIF tools.

The application tried to connect, but the camera did not respond in time. It might be turned off, incorrectly connected, or not accessible from the internet.

  • Check the camera’s power and network connection.
  • Verify that you are using the correct address, for example: rtsp://user:[email protected]:554/Streaming/Channels/101.
  • If the camera is on another network, port 554 usually needs to be forwarded on your router.
  • The connection may be blocked by a firewall or your internet provider.

The player does not know how to reach the camera. This is not an issue with the last part of the address, but a network problem.

  • Internal IPs (e.g. 192.168.1.10) do not work from the internet – for external access you need a public IP or a hostname (DDNS).

You need to configure port forwarding on your router (typically port 554) to the internal IP address of the camera.

  • Instructions for your specific router can be found online.
  • Use strong passwords and disable unnecessary services on your camera.

Yes. If your IP address changes occasionally, use a free Dynamic DNS service (for example No-IP, DuckDNS, Dynu).

  • You will get a hostname that automatically updates to your current IP address.
  • Most routers and cameras support DDNS directly in their settings.

You can check your public IP address on whatismyipaddress.com or in your router’s administration panel.

Note: With mobile or shared connections, your IP address might be shared with other users.

Yes. Open multiple tabs or windows with different RTSP addresses – each stream will play independently.

Yes, if the camera provides audio. We attempt to play the sound (usually AAC codec). Some browsers restrict automatic audio playback – enable it manually if necessary.

Technical details

  • Supports only rtsp:// and rtsps:// URLs.
  • Must be publicly accessible – private/internal IPs are not allowed.
  • Make sure the camera or stream is accessible from the internet.
  • Other protocols (e.g. HTTP, HTTPS, files) are not supported.
  • Streaming starts when the player is loaded and stops when you leave.

We currently do not support stream recording or analytics. This service is focused purely on live playback.

About RTSP.RUN

RTSP.RUN helps turn publicly reachable RTSP and RTSPS streams into browser playback and website embeds.

It is built for technically capable users, web teams, and businesses that need to verify a live stream quickly and publish it without building a custom player.

Where it fits best

Use RTSP.RUN when you need live playback or an embed for a publicly reachable stream. It is not a recording platform, VMS, or analytics product.

The goal is simple: make browser playback and website embed practical while keeping the technical limits explicit.

For product questions, feedback, or business use, contact [email protected].

RTSP.RUN is focused on live browser playback and website embed for publicly reachable RTSP and RTSPS streams.

Do you already have a public RTSP stream?

Verify it in the browser and, if it works, use the prepared output for sharing or website embed.

For publicly reachable RTSP/RTSPS streams only. No recording or analytics.