Embed a live camera in a Webflow page

Use RTSP.RUN as the fast path from a public RTSP stream to browser-ready playback and an iframe embed for Webflow.

This works well for microsites, company pages, event pages, and public camera rollouts where you do not want a custom streaming stack.

What to prepare before a Webflow embed

  • A public RTSP/RTSPS stream that you can verify in the browser.
  • A Webflow page or component where an Embed block is allowed.
  • A public section of the site where the live camera should be visible.
Put a camera on your website See if public RTSP fits

What this changes for a Webflow rollout

Faster launch path

The team can touch the Embed block only after playback is confirmed instead of debugging every layer at once.

Less integration noise

It becomes obvious whether the blocker is the RTSP stream itself or the website layer.

Lean website delivery

A public live-camera block does not need a custom streaming stack or dedicated player project.

Where this usually fits in a Webflow rollout

  • when you need a live-camera section in a microsite, company page, or event page without a custom video stack
  • when a web team wants to confirm playback first and only then work with an Embed block
  • when the goal is a fast public launch rather than a broad custom streaming project

What usually blocks the Webflow rollout

  • the stream is not really browser-ready yet, so Webflow is not the actual point of failure
  • the live camera belongs to a sensitive or internal use case where a public RTSP model is the wrong fit
  • there is no clear owner for stream availability and future RTSP or camera changes

What to align before internal or client handoff

  • which page will carry the embed, who inserts it, and who approves the public use context
  • whether the next step is self-service embed, assisted rollout review, or a stop because the fit is wrong
  • how the team will react if the RTSP URL, framing, or reachability changes after launch

Common questions before you embed a live camera

Before you think about blocks, CMS fields, or iframe wrappers, verify that you have a publicly reachable RTSP/RTSPS stream and working browser playback.

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_stream

Not 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.x will 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.

Yes, if the camera provides audio. We attempt to play the sound (usually AAC codec). Some browsers restrict automatic audio playback – enable it manually if necessary.