Why start with this embed path
Built for simple website rollout
Use it when the main goal is to get a working live camera onto a website without building your own browser streaming stack.
Preview first, publish second
Verify the stream in the player before you place it on a company page, venue page, tourist page, or temporary campaign site.
Useful for web integrators and lean teams
Move from RTSP validation to website embed without opening a full custom player project.
Clear fit before rollout
Best fit for public live views and browser-ready pages, not for access-controlled monitoring or enterprise CCTV programs.
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
- 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
<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 page is usually used
1. Start with the public RTSP URL
Open the embed flow and verify that the stream can really be played in a browser.
2. Review the live browser output
Check whether the framing, stability, and page fit are good enough before you embed anything on a public website.
3. Continue to the embed step
If the stream works, copy the iframe and place it on the website. If it fails, fix the stream or use fit-check instead of guessing.
Where this use case is a good fit
Good fit when
- you want a live camera on a website, landing page, branch page, venue page, or public information page
- the stream is intentionally public or at least publicly reachable from the internet
- you need quick playback plus embed, not a full monitoring or video platform
Poor fit when
- the camera must stay private or only work inside a closed internal network
- the rollout needs recording, analytics, retention, or stronger access controls
- you are looking for a managed enterprise video program rather than a simple website embed flow
Want to put a live camera on a website?
Start with the embed flow, verify the RTSP stream in the browser, and continue directly to the website-ready step only after playback works.
If you are still not sure whether public RTSP is the right model for your website or client rollout, start with fit and limits first.