适用于网站、门店页面和公开展示页面

把实时摄像头放到你的网站中。

从公开可访问的 RTSP 或 RTSPS 地址开始,先在浏览器中确认视频流,再在下一步复制嵌入代码。

先确认播放器效果 下一步获取嵌入代码

开始之前

先准备好这三项:

rtsp.run / player.html
先验证
可供验证的实时播放器
浏览器中打开的实时播放器 可直接放到页面里的嵌入代码
  • 可从互联网访问的摄像头或视频流
  • 可用的 RTSP 或 RTSPS 地址
  • 网站上用于放置播放器的位置

Choose the fastest next step for website rollout

Either verify a public stream for embed right away, or request rollout review first for a client, team, or more sensitive launch.

从这里开始

先验证流,再进入嵌入流程

当你已经有公网 RTSP 或 RTSPS 地址,并且需要尽快得到可用于网站的输出时,使用内置流程。

用你的 RTSP 地址开始

Assisted path

Rollout review and client handoff

Use the assisted path when you need to confirm scope, next step, ownership, or website rollout for a client or internal team.

Request rollout review

Business proof

Confirmed public rollout patterns

RTSP.RUN is already used in several public live-camera scenarios. Use the self-service path when the stream is ready, and use rollout review when the fit is still unclear.

Confirmed use-case types

Road traffic, water-flow monitoring, and construction progress.

Concrete public example

One operator embedded roughly 15 public cameras on a single page.

Named reference

Lido Beach Cervia uses a live beach camera as a conversion layer, while Bay City Yacht Club uses live marina cameras as a retention and utility layer.

Clear next step

Ready stream = self-service validation. Unclear fit = rollout review.

🏢 在公司网站添加直播摄像头

从公开 RTSP 地址开始

粘贴你准备在网站上使用前先验证的公开 RTSP 或 RTSPS 视频流。

如果你还没准备好,可以先查看 RTSP 地址指南,或申请 适配检查

嵌入流程如何工作

1. 从摄像头地址开始

粘贴公开的 RTSP 或 RTSPS 地址,并在浏览器中打开视频流。

2. 先检查实时播放器

在发布到其他页面之前,先确认视频流能够正确加载。

3. 复制嵌入代码

使用播放器内置的嵌入选项,把代码放到您的网站或活动页面中。

投入生产前先确认

RTSP.RUN 适用于公开可访问的 RTSP 和 RTSPS 流,以及实时播放或网站嵌入,不适用于内部 CCTV、录制或分析。

为网站上线选择下一步

Embed 流程并不是单一路径。你可以根据现在是准备验证、还在判断适配性,还是已经接近上线来选择下一步。

从这里开始

先验证流,再进入嵌入流程

当你已经有公网 RTSP 或 RTSPS 地址,并且需要尽快得到可用于网站的输出时,使用内置流程。

用你的 RTSP 地址开始

发布前确认

上线前确认是否适合

当公网可达性、产品限制或安全边界还需要先判断时,先使用 fit-check。

确认公网 RTSP 是否适合

客户或团队交接

验证后获取上线支持

当流已经工作正常,但你还需要 embed rollout、客户交接或上线前复核支持时,使用辅助路径。

沟通上线方案

先看看验证后你会发布什么

实际结果始终一样:先验证实时播放器,再拿到已经准备好的嵌入代码。

浏览器输出

浏览器中打开的实时播放器

rtsp.run / player.html
先验证
可供验证的实时播放器
浏览器可播放输出 桌面端 • 平板 • 手机
  • 先确认流可以正确加载,再决定是否分享。
  • 同样的输出可在桌面端、平板和手机上打开。
  • 验证通过后既可直接观看,也可进入下一步嵌入。

网站输出

可直接放到页面里的嵌入代码

示例 iframe
<iframe
  src="https://rtsp.run/embed.html?streamUrl=YOUR_STREAM_ID"
  width="640"
  height="360"
  style="border:0;"
  allowfullscreen
  referrerpolicy="origin">
</iframe>
  • 播放成功后即可复制准备好的 iframe。
  • 可用于企业网站、门店展示、公共摄像头或活动页面。
  • 不需要自己开发网页播放器。

为什么使用这个嵌入流程

无需自建播放器

您不必自己实现 HLS 播放、排查编解码问题,或把厂商专用查看器接入网站。

适合公开展示

可用于门店橱窗、办公室、农场、工作室、活动现场或临时宣传页面。

一个来源,多种用途

从一个公开的 RTSP 或 RTSPS 地址开始,同一视频流可同时用于直接观看、分享以及网站嵌入。

常见摄像机品牌与兼容性

当摄像机提供标准且可从公网访问的 RTSP 或 RTSPS 流时,RTSP.RUN 才最有价值。下面这些品牌最常出现在我们的帮助内容和真实咨询里。

最常被提到的摄像机品牌

Hikvision Dahua Axis Reolink Tapo / TP-Link Uniview Amcrest Annke Ezviz

真正决定兼容性的因素

仅有品牌并不够。关键在于具体型号是否提供正确的 RTSP/RTSPS 地址,以及该流是否能从互联网访问。如果你还不确定,请先查看 RTSP URL 指南或做适配性与限制确认。

典型适用场景

这些是 RTSP.RUN 最常匹配产品能力和业务预期的场景。

这里展示的是适用场景,不是企业级案例背书,也不是对录制、分析或内部 CCTV 的承诺。

企业网站上的直播摄像头

当你想先验证一个公开 RTSP 流,然后把实时画面放到公司网站、门店页面或活动落地页上时,RTSP.RUN 很合适。

最适合需要浏览器播放加网页嵌入,而不是完整监控平台的场景。
查看此场景

门店、场馆或公开直播页面

当你想把门店、场馆、前台或其他面向访客的位置的实时画面直接放到网站上时,可以使用 RTSP.RUN。

最适合页面只需要简单实时画面,并且该流本来就应该可从互联网访问的场景。
查看此场景

临时项目、活动或状态页面

适用于项目页面、工地进度页、活动 microsite 或其他公共状态页面,无需自己搭建播放器链路。

最适合速度比高级监控、留存或合规功能更重要的场景。
查看此场景

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.

It shows where RTSP.RUN fits well today: public live visibility on a website, not a broader video platform.
View case study

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.

This fits public information or utility-style use cases where browser playback and simple embed are more important than advanced monitoring.
View case study

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.

This is a good fit when rollout speed and simple live visibility matter more than recording or complex monitoring workflows.
View case study

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.

It shows that a live camera can work as a conversion tool for tourism websites, not only as a technical website add-on.
View case study

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.

It shows a different business impact from the same stack: not conversion-first, but retention, utility, and stronger membership value.
View case study

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.

It shows a hybrid business effect: lower decision friction plus a stronger local marketing edge.
View case study

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.

Best for fast website rollout, public stream validation, and simple embed delivery.

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.

Better for internal or ad-hoc access, not for a public website output.

Custom stack

This fits when you need full control over playback, distribution, integration, and other layers beyond the current product scope.

Better for teams that intentionally want to own custom development, infrastructure, and operational complexity.

RTSP.RUN 是什么,不是什么

这个部分帮助你快速判断,你需要的是浏览器播放器和网页嵌入工具,还是另一类视频产品。

RTSP.RUN 适合

  • 验证公共 RTSP 视频流是否可以在浏览器中播放。
  • 分享网页播放器或把生成的嵌入代码放到网站中。
  • 排查常见的 RTSP URL 和可达性问题。

RTSP.RUN 不适合

  • 它不是 VMS、NVR 或 CCTV 管理平台。
  • 它不是为录像、保留或分析而设计的。
  • 在默认公共流程下,它不适合封闭的内部摄像网络。

What is stored, what is not, and when to stop

RTSP.RUN is not a zero-data black box. Contact inquiries and basic product events are written locally, active stream metadata exists while playback is running, and the service is not built as a video archive.

What is used for 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 storing as a media 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 be a fit-check, not a self-service start

  • 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

常见问题

RTSP 地址是您的摄像机用于通过互联网传输视频的 URL。您可以在摄像机说明书、摄像机设置或制造商网站上找到它。

常见格式:

rtsp://用户名:密码@IP地址:554/视频路径

不确定?请搜索您的摄像机型号并添加关键词 RTSP URL,或联系制造商。

这通常是由于地址错误、摄像机无法访问或连接被阻止造成的。

  • 确保摄像机已开启,并在设置中启用了 RTSP。
  • 要从互联网访问,流必须是公开可访问的(私有 IP,如 192.168.x.x,无法从外部访问)。
  • 如果摄像机位于路由器之后,请设置端口转发(通常为端口 554)。
  • 检查防火墙或您的互联网服务提供商是否阻止了连接。

您需要在路由器上配置端口转发(通常是端口 554),指向摄像机的内部 IP 地址。

  • 您可以在网上找到针对特定路由器的教程。
  • 请使用强密码,并禁用摄像机上不必要的服务。

常见问题