Embed a live camera on a WordPress website

Verify a public RTSP/RTSPS stream in the browser and then place the prepared iframe on a WordPress page, post, or landing page.

This is the fast path when you need a live camera on a company website without building your own player or relying on a vendor viewer.

What to prepare before a WordPress embed

  • A publicly reachable RTSP or RTSPS stream that can be verified in the browser.
  • A WordPress page, post, or block where custom HTML / iframe embed is allowed.
  • A clear public-facing page where the live image should appear.
Put a camera on your website See if public RTSP fits

What this changes for a WordPress team

Less extra build work

You do not open a custom player project just to place one public live view on a website.

Faster website handoff

Once the stream is validated, the next step is a clear iframe action for the editor, page builder, or HTML block.

Lower rollout risk

Playback is confirmed first, so the CMS placement and visitor-facing launch happen on top of a real browser result.

Where this usually fits in a WordPress rollout

  • when you already have a page, post, or landing page and need one clear live-camera block on it
  • when you want browser playback confirmed first and only then move to Gutenberg, custom HTML, or a page-builder block
  • when you do not want a custom player project just to place one public live view on a website

What usually blocks the WordPress rollout

  • the stream is not publicly reachable yet, so the real blocker is RTSP availability rather than WordPress itself
  • the team is trying to solve embed before there is a verified browser-ready output
  • the use case actually needs recording, access control, or a different delivery model than a public iframe embed

What a clean handoff to the web team looks like

  • validated player output first, iframe snippet second, CMS placement third
  • a named owner for stream availability, RTSP URL changes, and camera-side adjustments
  • a clear decision on which public URL will show the camera and in what context

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.