For the complete documentation index, see llms.txt. This page is also available as Markdown.

RTSP Camera URLs

Look up RTSP URL formats for major camera brands, choose main or substreams, and connect existing video equipment to Kilo Lens.

An RTSP URL identifies the video stream that Twin reads from an IP camera. Knowing the manufacturer's URL pattern helps you connect existing equipment across sites, even when the cameras come from different suppliers.

RTSP is the shared protocol; the stream path depends on the manufacturer, model, and firmware. This directory covers common commercial and residential camera brands. Each entry identifies a useful starting format and important variations. Confirm that the particular camera supports RTSP and that the service is enabled.

How do I build an RTSP camera URL?

rtsp://username:password@cameraip:port/path

Replace username and password with the camera's local streaming credentials, cameraip with its address reachable from the Twin host, and port with its configured RTSP port. These are camera credentials, separate from your Twin login and Lens pairing token. The examples use port 554; replace it when the camera uses a different port.

A main stream normally provides the higher-resolution picture. A substream provides a lighter alternative that can reduce processing and bandwidth requirements. Their exact quality depends on the camera's encoding settings.

Which RTSP URL does my camera brand use?

Tapo · Hikvision / HiLook · Dahua · Axis · Reolink · Amcrest · Avigilon · Bosch · EZVIZ · Foscam · Hanwha / Wisenet · i-PRO · VIGI · Uniview · VIVOTEK

What is the RTSP URL for a Tapo camera?

For RTSP-capable Tapo cameras:

Main: rtsp://username:password@cameraip:554/stream1
Sub:  rtsp://username:password@cameraip:554/stream2

Create a local Camera Account in the Tapo app under the camera's Device Settings → Advanced Settings → Camera Account. Use those credentials, not the TP-Link cloud account. Battery-powered models often lack RTSP; check the model's support details. Some dual-lens models use /stream6 and /stream7 for the second lens. See TP-Link's RTSP setup guide.

What is the RTSP URL for Hikvision and HiLook cameras?

The channel-one pattern is:

The final number combines the channel and stream: 101 means channel 1, main stream; 102 means channel 1, substream. A recorder's channel 2 uses 201 and 202. A standalone camera normally uses channel 1. These paths follow Hikvision's RTSP examples; the HiLook camera used in our Lens setup also streams through /Streaming/Channels/102.

Use the device's configured RTSP port. HiLook exposes port settings under Configuration → Network → Basic Settings → Port in the HiLook network camera manual; labels may differ with firmware.

What is the RTSP URL for a Dahua camera?

channel starts at 1. subtype=0 selects the main stream; subtype=1 selects the first extra stream. Change the channel when connecting through a recorder. See Dahua's RTSP reference.

What is the RTSP URL for an Axis camera?

Axis uses this default endpoint. For devices with multiple video channels, a parameter such as ?camera=2 selects another channel. Stream profiles and other parameters control the requested video settings; Axis does not use the Tapo stream1/stream2 naming pattern. See Axis's streaming guide and RTSP parameters.

Reolink's current reference uses Preview_01_main and Preview_01_sub for a standalone camera. Recorder channels use two-digit numbers such as 02. Check model compatibility and enable RTSP in the device's port settings. See Reolink's RTSP guide.

What are the RTSP URLs for other camera brands?

The following entries extend the reference to other common camera families. These are URL patterns, not a model-by-model Lens certification list. Use the camera’s configured port if it differs from the example.

Amcrest

IP camera example; supported extra streams use subtype=1. Recorder paths may instead use /h264Preview_01_main. Manufacturer reference.

Avigilon

Prefer the URI generated on Compression and Image Rate → RTSP Stream URI, especially for multisensor cameras. Manufacturer reference.

Bosch

BVIP devices select encoding stream 2 with inst=2; multichannel encoders also use line. Manufacturer reference.

EZVIZ

Published for C6N/TY1/TY2; RTSP availability is model-specific. See the password note below. Manufacturer reference.

Foscam

Use /videoSub for the substream. Many models use port 88; check the configured RTSP port. Manufacturer reference.

Hanwha Vision and Wisenet

Replace N with the configured profile number. Profile numbers select configured encodings, not universal main/sub quality. Manufacturer reference.

i-PRO

Current documented H.264/H.265 path; stream_2 selects stream 2. Older H.264 paths include /Src/MediaInput/h264/stream_1. Manufacturer reference.

Use /stream2 for the substream and the VIGI camera’s local credentials. Manufacturer reference.

Uniview and UNV

Common single-camera paths use /media/video2 for substream and /media/video3 for a third stream when supported. Manufacturer reference.

VIVOTEK

Traditional access name; /live2.sdp selects stream 2. Newer firmware can use profile URLs; see below. Manufacturer reference.

EZVIZ local password

For the documented models, the initial local credential can be the verification code on the camera label. If you change the local connectivity/video encryption password, use that updated password. See EZVIZ local authentication.

VIVOTEK profile URLs

Firmware 2.2002.x.x and later can use this form:

Replace profileToken with the actual video profile token from the camera; it is unrelated to a Lens pairing token. Some devices also expose /live1sN.sdp access names. Use the name shown by that camera rather than assuming the stream index. See VIVOTEK’s firmware-specific instructions.

How do I use the RTSP URL in Twin?

Open Settings → Camera Connector in the camera's Twin and enter the full URL in its stream URL field. Configure the substream separately when available, then save and confirm that Twin receives video. Continue with Connecting a Camera to pair Twin with Lens.

If the connection fails, check the address from the Twin host's network, the RTSP port, local account, and exact path capitalization. A working camera web login does not prove that RTSP is enabled. For a camera behind a recorder, use the recorder's address, credentials, and correct channel rather than the direct-camera example.

Keep credential-bearing URLs private. Twin reaches the camera locally; connecting it to Lens does not require exposing the camera's RTSP port to the public internet. See Access and Troubleshooting for the rest of the connection checks.

Last updated