RTSP URL List: Stream Address Formats for Major Camera Brands

How an RTSP URL is structured

Every camera RTSP address follows the same skeleton: a scheme (rtsp://, or rtsps:// when the camera supports TLS), the camera's IP address or hostname, a port, and a vendor-specific path. Port 554 is the conventional default, but it is not universal—many Foscam models serve RTSP on port 88, GeoVision devices default to 8554, and UniFi Protect issues rtsps:// URLs on port 7441.

The path is where brands diverge. It usually encodes which channel to open—a standalone camera, or one channel of a recorder—and which quality level to use: the high-bitrate main stream or the lighter sub stream. The table below consolidates the formats these vendors document. Treat each entry as a starting point rather than a guarantee, because paths change across models, firmware versions, and regional variants.

RTSP URL list by camera brand

The examples use placeholder credentials (user:pass) and a placeholder address (CAMERA_IP). In an NVR that provides separate username and password fields, leave the credentials out of the URL and enter them in the protected fields instead.

If a documented format fails, do not iterate through other brands' paths against the same camera. Repeated failed logins can lock the account, and a wrong-but-accepted path may silently open a different channel than you intended.

How to find the URL for an undocumented model

1. Check the manual for the exact model. Search the vendor's support site for the full model number and the word RTSP. A similar-looking sibling model is not evidence—paths differ within product lines.
2. Ask the camera through ONVIF. An ONVIF client can request the camera's media profiles and their stream URIs, which returns the exact URL the firmware actually serves. This is the most reliable method because nothing is guessed. OmniNVR's ONVIF discovery does this automatically on Mac, iPhone, and iPad.
3. Look in the camera's own interface. Many web interfaces and vendor configuration tools display the active RTSP address, or at least the configured RTSP port and stream names.

If none of these produce a URL, the camera may simply not expose RTSP. Cloud-only cameras, many battery models, and some regional variants have no local stream to find, and no list can supply a path the firmware does not serve.

Why embedding credentials in the URL is risky

A URL that contains user:pass@ is easy to leak: it appears in player logs, shell history, screenshots, shared notes, exported configurations, and support tickets. Special characters in the password also need percent-encoding inside a URL, which is a common source of authentication failures that look like wrong-path errors.

Prefer an application with separate credential fields—OmniNVR stores camera credentials in the Apple Keychain rather than in a plain-text URL. Use a dedicated camera account with viewing permissions only, never the administrator or cloud-app login. And regardless of how credentials are stored, do not forward a camera's RTSP port to the public internet; exposed camera services are a recurring subject of security advisories.

Validate the URL in an NVR before relying on it

First prove the URL in a generic player such as VLC (Media, then Open Network Stream) or ffplay. A player confirms that the scheme, host, port, path, and credentials produce decodable video. It does not confirm that the stream can be recorded reliably.

Then add the same URL to the NVR and test the full pipeline: several minutes of stable live video, a short recording, timeline playback, and a reconnect after briefly interrupting the network. Repeat with the sub stream if you plan to record it continuously. Only after those steps should a URL from any list—including this one—be treated as verified for your camera.