How to Choose Cameras for Cloud Video Surveillance: RTSP, Resolution, Bitrate

Cloud video surveillance doesn’t require “special” cameras — almost any IP camera already sold in Tashkent will do. But three settings determine how much you’ll pay for the archive every month.

The key requirement: RTSP

A cloud service receives video from a camera over the RTSP protocol. It’s supported by virtually all IP cameras from Hikvision, Dahua, Uniview, HiWatch, Ezviz (except some “home” models locked to the manufacturer’s cloud), TP-Link Tapo/Vigi, Reolink and most no-name cameras from AliExpress. If the specs list “RTSP” or “ONVIF,” the camera will connect.

Not suitable: analog cameras without a recorder (AHD/TVI/CVI), Wi-Fi baby monitors that work only with the manufacturer’s app, and cloud-locked cameras without local access. Analog cameras can be connected through a hybrid recorder with RTSP output — a common approach when cameras are already installed.

Resolution: 2 MP is almost always enough

Full HD (2 MP, 1920×1080) reads a license plate at 10–15 meters, a face at 5–7, and banknotes at the checkout at 2–3 meters. That’s enough for a sales floor, checkout, corridor or warehouse. 4 MP is needed where a single frame covers a large area and background details matter: a large warehouse, a parking lot, a yard.

The key point: archive size grows with resolution. With the same settings, 4 MP produces roughly twice as much data as 2 MP — and costs twice as much to store.

Bitrate is what you actually pay for

Bitrate is how many megabits per second the camera sends to the cloud. It’s bitrate, not megapixels, that determines archive size:

• 1 Mbps ≈ 10.5 GB per day per camera;
• 2 Mbps ≈ 21 GB per day (typical for 2 MP with H.264);
• 4 Mbps ≈ 42 GB per day (2 MP at high quality, or 4 MP);
• 6 Mbps ≈ 63 GB per day (4–5 MP).

At 10 UZS per GB per day and a 30-day archive, a camera at 2 Mbps costs about 189 000 UZS per month with 24/7 recording. The same camera at 4 Mbps costs twice as much. So the first thing to do after connecting is to open the camera settings and set a sensible bitrate: for 2 MP, 1.5–2.5 Mbps is usually enough.

Codec: H.265 saves a third

If the camera supports H.265 (HEVC), turn it on: at the same picture quality, the stream is 30–50% smaller than with H.264. All cameras from recent years support it; make sure the service accepts H.265 — MCVMS does.

Recording mode

24/7 recording isn’t needed everywhere. Options that reduce the volume:

• Scheduled — only during business hours. For a store or office, that’s an instant 50% saving.
• Motion-triggered — the camera records when something happens in the frame. For a warehouse at night, an entrance or a corridor, this saves 60–70%.
• Combined — the checkout records continuously during business hours, everything else on motion.

How much bandwidth you need

As much as the total bitrate of your cameras, plus a 20–30% margin. Four cameras at 2 Mbps need 8 Mbps of upload — a regular plan will do. Ten cameras at 4 Mbps need 40 Mbps, and it’s worth checking that your ISP doesn’t throttle upload speed (on many residential plans it’s several times lower than download). Put guest Wi-Fi on a separate network so it doesn’t interfere with the cameras.

Pre-purchase checklist

• RTSP or ONVIF is listed in the specs.
• 2 MP resolution for indoor rooms, 4 MP for large areas.
• H.265 support.
• For outdoor and damp areas — IP66/IP67 protection and IR illumination with the range you need.
• PoE power — one cable instead of two, fewer power adapters and points of failure.

You can estimate the cost for your number of cameras and archive depth in the MCVMS calculator. If your cameras are already installed, send us the models and we’ll tell you whether they’ll connect.