Will my cameras work with other software?

Almost every camera sold in the last decade can hand its video to other software. Here's how to check yours in about ten minutes, without buying anything.

What RTSP is, in one paragraph

RTSP (Real Time Streaming Protocol) is the common language cameras use to hand live video to other software. If your camera or recorder speaks it, then any system that also speaks it — recording software, analytics, a monitoring service — can read your video without replacing hardware. It is the reason "you don't need new cameras" is usually true rather than a sales line.

The ten-minute check

1. Find out what you have

Look at the label on the recorder or a camera, and note the brand and model. Hikvision, Dahua, Uniview, Provision, Reolink, Amcrest, TP-Link VIGI, Ubiquiti, Axis and the many rebadges of the first two cover the bulk of South African installations, and all of them support RTSP.

2. Decide: cameras or recorder?

• Straight from each camera — best quality and lowest latency, and it keeps working if the recorder is off. Needs each camera reachable on the network.
• From the DVR/NVR — one device to point at, useful when cameras are analogue (HD-TVI/AHD/CVI) and the recorder is the only thing on the network. This is the only option for analogue systems.

3. Get the stream URL

The pattern is nearly always the same shape:

rtsp://username:password@ip-address:554/path

Only the path differs by brand — for example Hikvision commonly uses /Streaming/Channels/102 for a sub-stream, and Dahua something like /cam/realmonitor?channel=1&subtype=1. You rarely need to know these by heart: any decent onboarding process discovers cameras on the network and tries the known paths for you.

4. Test it

Install VLC on a laptop on the same network, choose Open Network Stream, paste the URL and press play. If you see live video, your cameras will work with third-party software. If you get an error, work through the next section.

Main and sub-streams — use the small one

Nearly every camera publishes at least two streams: a main stream (full resolution, for recording) and a sub-stream (typically 640×360 or 704×576, for phone apps). For detection and analytics the sub-stream is usually the better choice — it costs a fraction of the processing power and AI models downscale the image anyway. Reach for the main stream only where fine detail matters, such as reading faces or number plates.

When it doesn't work

Symptom	Usual cause	Fix
Authentication failed	Wrong credentials, or special characters in the password	Test in the camera's own web interface first; avoid @ and : in passwords
Connection refused	RTSP disabled in settings	Enable RTSP / "third-party access" in the camera or NVR network menu
Works once, then fails	Anti-brute-force lockout after repeated attempts	Wait for the lock to clear (often 30 min), then connect once — see below
Nothing on the network	Analogue cameras	Pull the stream from the DVR instead
Cloud-only camera	Brand deliberately blocks RTSP	Usually cannot be worked around — see below

The lockout trap, and why it matters

Several brands — Hikvision especially — lock out an IP address after a handful of failed logins. Software that opens a new connection per stream can trip this and get itself banned, which looks exactly like a broken camera. The right approach is a single pooled connection per camera that is then shared internally. It's worth asking any provider how they handle this; we learned it the hard way on our own cameras.

The genuinely closed ones

A few consumer brands — parts of the Ring, Nest, Arlo and Eufy ranges, and some Tapo models — deliberately provide no RTSP, so your video is only accessible through their own app and subscription. If that is what you have, no third-party system can read it, and the honest answer is that you'd need to add or replace a camera. Worth knowing before anyone quotes you.