Verkada RTSP: a private-network camera stream

Check camera model and private addressing first

The RTSP documentation excludes CR63-E and CR63-TE Remote Cameras. For a supported camera, the receiving application connects to the camera on the local network rather than receiving a general public cloud URL. Confirm the model and approved network route before changing the streaming setting.

Verkada specifies RFC1918 private camera addresses: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16. A camera addressed outside those private ranges does not satisfy the documented RTSP prerequisite. A reachable administration interface alone is not evidence that the stream configuration meets this requirement.

Enable RTSP with an authorized account

1. Have a Site Admin confirm that the selected camera and its private-network address meet the RTSP prerequisites.
2. In Command, open Cameras, select the camera, then Settings > Device and enable Real Time Streaming Protocol.
3. Create a unique RTSP username and password. Store the password securely because the documentation says it is not displayed again.
4. Copy the provided SQ or HQ URI, substitute the actual password for its placeholder privately, and test it from an allowed local client.

Stream limits depend on the camera model

The documented limit for an ordinary single-camera model is two concurrent RTSP streams. Multisensor CY63-E and CY53-E allow four in total, while CH63-E, CH53-E and CH52-E allow eight, with two per camera thread. Check the current model matrix rather than applying one limit to every camera. Standard-quality and high-quality limits are not additive; count existing viewers and recorders before diagnosing capacity.

The standard-quality and high-quality choices reflect the camera settings in Command. Review the configured codec and image quality when a connection succeeds but the receiving application cannot decode the picture. The availability of RTSP does not automatically establish ONVIF discovery or control.

Port 8554 is not permission to publish the camera

Verkada documents RTSP on port 8554 and restricts the feature to local access. Keep external access blocked and use the available client IP restrictions where appropriate. Do not port-forward the camera to turn the local URI into a public link. Stream credentials embedded in an address can leak through screenshots, copied logs or shared viewer configuration, so redact them before requesting help.

Separate permissions from playback problems

If the toggle is unavailable, check the operator role and supported model. If the URI times out, check private addressing, client restrictions and the approved LAN route. If it authenticates without video, inspect codec settings and concurrent sessions. Reviewed on 2026-10-18 against the official RTSP and camera permissions articles. No physical-camera testing or range-wide compatibility certification is implied.

Check each feature independently

Start on the same local network with the exact model, firmware and account permissions. A working video stream does not prove support for ONVIF discovery, pan or tilt, two-way audio, events, or every recording feature. Test the features you need in your installed SmartRTSP app.

Keep camera credentials private. Do not expose camera ports to the public internet just to test local viewing. Manufacturer cloud accounts, device accounts and generated sharing links are not interchangeable.

Official sources and scope

Read the documentation for the exact model before changing settings. Manufacturer menus, firmware and service availability can change. These sources explain the published connection conditions, not independently verified SmartRTSP hardware compatibility.

• Verkada low-latency RTSP streaming
• Verkada camera roles and permissions