Verify public RTSP streams in a browser and launch them on your website without building a player.

RTSP.RUN helps you test a publicly reachable RTSP or RTSPS stream, open it in a regular browser, and move to a website-ready embed only after playback works. That shortens rollout time and avoids a DIY browser video stack.

No vendor app required Playback verification and embed in one flow

Verify a public RTSP stream

Paste a public RTSP or RTSPS URL to check whether the stream is reachable and browser-ready.

rtsp.run / player.html
Preview first
Live player ready for verification
A live player opens in the browser Embed code is ready for your page

Need help before you test? Start with the RTSP URL guide or review the requirements and limits.

If playback works, you move into sharing, embed, or rollout decisions with a validated stream instead of guessing from camera specs alone.

Put a camera on your website Find your RTSP URL

Choose the fastest start based on what you already know

If you already have a public RTSP URL, move straight to validation. If fit, scope, or rollout ownership are still unclear, use the assisted path first.

Fastest path

Self-service validation

Use this when you already have a public RTSP or RTSPS URL and want a fast browser-ready answer before you build anything else.

Verify RTSP stream

Assisted path

Rollout review and client handoff

Use the assisted path when you need to confirm scope, next step, ownership, or website rollout for a client or internal team.

Request rollout review

Business proof

Confirmed public rollout patterns

RTSP.RUN is already used in several public live-camera scenarios. Use the self-service path when the stream is ready, and use rollout review when the fit is still unclear.

Confirmed use-case types

Road traffic, water-flow monitoring, and construction progress.

Concrete public example

One operator embedded roughly 15 public cameras on a single page.

Clear next step

Ready stream = self-service validation. Unclear fit = rollout review.

Request rollout review Who is behind RTSP.RUN

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.
Try your RTSP URL See website embed flow

Choose the path that matches your rollout

RTSP.RUN works in three practical layers depending on how ready your stream, website, and rollout decision already are.

Fastest path

Self-service validation

Use this when you already have a public RTSP or RTSPS URL and want a fast browser-ready answer before you build anything else.

Verify RTSP stream

Best before you test

Fit-check before rollout

Use this when public reachability, security limits, or product fit are still unclear and you need a quick pre-check before rollout.

See if public RTSP fits

Assisted path

Rollout help after validation

Use this when the stream already works and you need help with website embed, a client handoff, or the next rollout decision.

Talk through your rollout

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.

See if public RTSP fits Requirements and security

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.

See this use case
Construction site or field project

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

See this use case
Storefront, venue, or event page

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

See this use case
Web integrator delivering for a client

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

Typical supported scenarios

These are the situations where RTSP.RUN most often matches the product story and buyer expectations described across the site.

These are supported scenarios, not enterprise references or promises about recording, analytics, or closed internal CCTV.

Live camera on a company website

Use RTSP.RUN when you want to verify a public RTSP stream and then place a live view on a company website, branch page, or landing page.

Best fit when the goal is browser playback plus embed, not a full surveillance platform.
See this use case

Storefront, venue, or public-facing live page

Use RTSP.RUN when you want to show a live look at a storefront, venue, reception area, or another visitor-facing location directly on a website.

Best fit when the page only needs a simple live view and the stream is already meant to be reachable from the internet.
See this use case

Temporary project, event, or site update

Use it to show a live view on a project page, construction update, event microsite, or similar public status page without building your own player stack.

Best fit when speed matters more than advanced monitoring, retention, or compliance features.
See this use case
Embed a camera on your website See if public RTSP fits

Confirmed rollout patterns from real usage

These are not invented references or enterprise claims. They are anonymized use cases that have already been run through RTSP.RUN.

No customer names and no inflated outcome claims. Just confirmed scenarios that match the product as it exists today.

A public road-traffic camera page

One operator used the embed flow for a page with roughly 15 cameras showing road traffic across multiple locations.

It shows where RTSP.RUN fits well today: public live visibility on a website, not a broader video platform.

Water-flow monitoring with live cameras

Confirmed usage also exists for public live views of creeks, streams, outlets, and similar locations where simple browser access matters.

This fits public information or utility-style use cases where browser playback and simple embed are more important than advanced monitoring.

Construction progress and project updates

RTSP.RUN has also been used to show construction progress, where the value is a fast public or stakeholder-facing live view without building a custom player stack.

This is a good fit when rollout speed and simple live visibility matter more than recording or complex monitoring workflows.

When RTSP.RUN makes more sense than a vendor viewer or custom stack

The best path does not depend only on whether the camera can stream. It depends on whether you need public browser playback, a fast website rollout, or a fuller custom video solution.

RTSP.RUN

This fits when you need a public browser-ready live view and website embed without building your own player or video stack.

Best for fast website rollout, public stream validation, and simple embed delivery.

Vendor viewer

This fits when you only need to open the camera internally for a limited audience and do not need a public browser or website embed layer.

Better for internal or ad-hoc access, not for a public website output.

Custom stack

This fits when you need full control over playback, distribution, integration, and other layers beyond the current product scope.

Better for teams that intentionally want to own custom development, infrastructure, and operational complexity.
Compare simple embed with a custom stack Request rollout review

Ready to turn a public RTSP stream into a website-ready live view?

Verify the stream in the browser first. If it works, move straight to sharing or website embed with lower rollout risk and no custom player project.

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

Verify RTSP stream Request rollout review

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
Requirements and limits See if public RTSP fits

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.

Find your RTSP URL See if public RTSP fits

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.

What RTSP.RUN is and is not

Use this section to decide quickly whether you need a browser player and website embed utility, or a different class of video product.

RTSP.RUN is for

  • Verify that a public RTSP stream plays in a browser.
  • Share the browser player or use generated embed code on a website.
  • Troubleshoot common RTSP URL and reachability issues.

RTSP.RUN is not for

  • It is not a VMS, NVR, or CCTV management platform.
  • It is not built for recording, retention, or analytics.
  • It is not the right fit for closed internal camera networks in the default public flow.
Requirements and limits Security and fit

What exists in the product flow, what does not, and when to stop

RTSP.RUN is not a zero-data black box and it is not a surveillance archive. This block is here so the team can decide whether the real requirement still fits before launch work goes further.

What is part of normal operation

  • Contact form submissions are written to local inquiry storage so product and business requests can be answered.
  • Basic product events such as stream start attempts, embed opens, and contact submits are stored in local marketing metrics.
  • Active and recent stream metadata exists in application memory for playback, admin review, and troubleshooting.
  • These details are part of the product flow, not a promise of zero-data processing.

What RTSP.RUN is not offering as a media or governance product

  • RTSP.RUN is not a recording or media archive platform for your camera footage.
  • The public product flow is not sold as analytics, retention, or long-term surveillance storage.
  • The service is not positioned as a formal data-processing or audit platform for internal CCTV operations.
  • If you need contractual retention or governance guarantees, treat that as a separate requirement before rollout.

When this should become a stop-or-fit-check decision

  • you cannot accept a publicly reachable RTSP or RTSPS stream
  • the rollout depends on recording, retention, analytics, or internal-only CCTV governance
  • you need contractual security or data-handling guarantees before any live test
  • the team still needs to decide whether the camera belongs on a public website at all
Read privacy and data handling Review security and fit

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.

Verify RTSP stream