FOR CONSTRUCTION SITES, FIELD PROJECTS, AND PUBLIC PROGRESS PAGES

Put a live construction site 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 a project page, investor update page, or field-status microsite.

Preview before you publish Embed after playback verification Best fit for public progress updates
Start with RTSP URL Check fit and limits

This flow fits public project updates, not private surveillance or site governance systems.

What you should have before you start

This scenario works best when these basics are already true:

  • You want to show a live construction site or field-project view on a website, status page, or stakeholder update page.
  • 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 project surveillance platform.

Why this use case fits RTSP.RUN

Fast rollout for progress pages

Use it when you need to show live progress without building a custom browser streaming stack for the project website.

Stakeholder-friendly browser output

Clients, partners, or the public can open the stream in a browser instead of dealing with a vendor viewer.

Simple path from stream to embed

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

Clear limits before launch

Best fit for publicly reachable live updates, not for recording, analytics, or controlled 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 update cadence are suitable for a public-facing project page.

3. Copy the embed code

If the stream works well, continue to the embed step and place the iframe on the construction site page or stakeholder update page.

Where this use case is a good fit

Good fit when

  • you want a live browser view on a construction, infrastructure, or field-project page
  • the stream is intentionally public or at least publicly reachable for website visitors or stakeholders
  • you need quick playback plus embed, not a project monitoring platform

Poor fit when

  • the camera must stay on a closed internal network only
  • the rollout needs recording, retention, analytics, or stronger operational guarantees
  • you are looking for a site-security or enterprise CCTV platform instead of a browser-ready public live view

Want to show a live construction site 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 project page your visitors or stakeholders will see.

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

Open embed flow Check fit and limits