FOR STOREFRONTS, VENUES, RECEPTIONS, AND PUBLIC-FACING PAGES

Put a live storefront or venue camera on your website.

Use RTSP.RUN when you want to show a public-facing live view on a storefront page, venue page, public camera page, or similar visitor-facing website without building your own player.

Simple browser playback first Embed after you verify the view Works best for intentionally public streams
Start with RTSP URL Check fit and limits

This flow is strongest when the camera is meant to be shown publicly, not when the rollout belongs inside a private CCTV environment.

What you should have before you start

This scenario works best when these basics are already true:

  • You want to show a live view from a storefront, venue, reception area, resort, or similar visitor-facing location.
  • The camera exposes a public RTSP or RTSPS stream that can be reached from the internet.
  • You need a lightweight browser player and embed path, not a full monitoring platform.

Why this use case fits RTSP.RUN

Made for public-facing pages

Use it when the goal is simply to show visitors what is happening right now on a website.

No vendor app for visitors

Your audience gets a browser-ready live view instead of instructions to install or open a camera vendor viewer.

Quick path from camera to website

Verify the stream first, then continue to embed without building a custom browser video stack.

Clear product fit up front

The flow works best for public live views, not for recording-heavy or access-controlled surveillance rollouts.

See what you publish after the check

The practical result is always the same: first you verify the live player, then you take the prepared embed code.

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.

How this rollout usually works

1. Confirm the public RTSP stream

Start with the browser player and make sure the stream is really reachable and stable before you publish it.

2. Review the live browser output

Check whether the image, framing, and behavior are suitable for a visitor-facing page.

3. Copy the embed code

If the stream works well, continue to the embed step and place the iframe on the storefront, venue, or public camera page.

Where this use case is a good fit

Good fit when

  • you want a live browser view on a storefront, venue, tourism, or visitor-facing page
  • the stream is intentionally public and can be reached from the internet
  • you need quick playback plus embed, not a surveillance platform

Poor fit when

  • the camera must stay private or inside a closed internal network
  • the rollout needs recording, retention, analytics, or stronger operational guarantees
  • you are looking for a consumer plug-and-play camera portal instead of a public RTSP flow

Want to show a live public-facing camera on your website?

Start by verifying the RTSP stream in the browser. If the live view works, continue directly to the embed step and place it on the page your visitors will actually see.

If you are still unsure whether a public RTSP stream is the right model for your location or audience, use the fit-check contact flow first.

Open embed flow Check fit and limits