FOR EVENTS, TEMPORARY CAMPAIGNS, AND LIVE STATUS PAGES

Put a live event camera on a website.

Use RTSP.RUN when you need to verify a public RTSP or RTSPS stream first and then publish a browser-ready live view on an event page, festival microsite, conference page, or temporary campaign.

Preview before the event goes live Embed after playback verification Best fit for public live event pages
Start with RTSP URL Check fit and limits

This flow fits public event pages, not private venue security or recording-heavy event production setups.

What you should have before you start

This scenario works best when these basics are already true:

  • You want to show a live event, venue, conference, or temporary campaign view on a website or microsite.
  • The camera exposes a public RTSP or RTSPS stream that can be reached from the internet.
  • You need lightweight browser playback and embed, not a full live production workflow.

Why this use case fits RTSP.RUN

Fast path for event pages

Use it when you need to get a live view online quickly without building a custom browser streaming stack for the event website.

Simple browser experience for visitors

Attendees, sponsors, or remote viewers can open the stream in a browser instead of dealing with a vendor viewer.

One flow for test and publish

Verify the stream first, then continue directly to embed for the event page or microsite.

Clear limits before launch

Best fit for public live updates, not for recording, production switching, or closed internal monitoring.

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 public event page or temporary microsite.

3. Copy the embed code

If the stream works well, continue to the embed step and place the iframe on the event page, venue page, or campaign microsite.

Where this use case is a good fit

Good fit when

  • you want a live browser view on an event, venue, conference, or campaign page
  • the stream is intentionally public or at least publicly reachable for visitors and stakeholders
  • you need quick playback plus embed, not a live production platform

Poor fit when

  • the stream must stay on a closed internal network only
  • the rollout needs recording, analytics, production switching, or stronger operational guarantees
  • you are looking for an event-production or enterprise streaming platform instead of a browser-ready public live view

Want to show a live event 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 or stakeholders will actually see.

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

Open embed flow Check fit and limits