Decide fit before you push a rollout
RTSP.RUN fits public RTSP and RTSPS streams that need browser playback or website embed. If the use case depends on internal CCTV, recording, or analytics, stop early and choose a different path.
Choose the next step for website rollout
The embed flow is not one-size-fits-all. Pick the path that matches whether you are ready to validate, still qualifying fit, or already moving toward launch.
Start here
Validate the stream and continue to embed
Use the built-in flow when you already have a public RTSP or RTSPS URL and need a website-ready output quickly.
Start with your RTSP URLPre-launch check
Confirm fit before you publish
Use fit-check when public reachability, product limits, or the security boundary still need a decision before you test.
See if public RTSP fitsClient or team handoff
Get rollout help after validation
Use the assisted path when the stream already works and you need help with embed rollout, a client handoff, or launch review.
Talk through your rolloutSee 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.
Why use this embed flow
No DIY browser video stack
You do not need to build HLS playback, troubleshoot codecs, or wire vendor-specific viewers into your website before launch.
Made for public viewing
Use it for storefront cameras, office views, farms, studios, venues, or temporary event pages.
Same source, more channels
Start from one public RTSP or RTSPS URL and reuse the player for direct watching, sharing, and website embedding.
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
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.
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.
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.
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.
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.
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.
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.
Lido Beach Cervia: live beach camera
The beach resort in Cervia uses RTSP.RUN for an embedded live stream on its website so visitors can see current conditions, atmosphere, and occupancy before deciding to come.
Bay City Yacht Club: live marina cameras
Bay City Yacht Club uses RTSP.RUN for multiple marina cameras so members and visitors can keep checking conditions on the water and return to the site as a daily utility.
Marshall Golf Club: live golf-course camera
Marshall Golf Club uses RTSP.RUN for a live course camera so players can quickly judge current conditions before deciding whether to drive out and play.
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.
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.
Custom stack
This fits when you need full control over playback, distribution, integration, and other layers beyond the current product scope.
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.
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
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_streamNot 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.xwill 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.
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.