How long can a Reolink NVR record? Bitrate and storage estimate

Count the streams that consume storage

Reolink's recording-duration guidance says to include main and sub-stream bitrates and, for cameras with separately recorded wide and tracking views, the streams from both views. Its reference table is not a guarantee for every setup. Motion-only schedules and actual recording activity also affect the retained duration; a camera count without stream settings is insufficient input.

Worked example with explicit units

Hypothetical calculation, not a Reolink model specification: assume 4,000,000,000,000 usable bytes and four cameras each contributing a combined 8,000,000 bits/s of recorded data. Total bitrate is 32,000,000 bits/s, giving 4,000,000,000,000 × 8 ÷ 32,000,000 ÷ 86,400 ≈ 11.57 days. This uses decimal units. Reolink's published examples use a 1024-based storage conversion, so compare units and inputs before comparing results.

Check your setup

1. Record the usable storage shown by your system and its units. For every recorded channel or view, note the relevant main/substream bitrate. Sum only streams actually stored by that recorder; do not count an unrecorded preview as an additional recording.
2. Use a consistent conversion: 1 decimal TB = 1,000,000,000,000 bytes and 1 Mbps = 1,000,000 bits/s. Allow for storage overhead and bitrate variation rather than promising retention to an exact hour.
3. Check the overwrite policy. Reolink documents both replacing the oldest files when full and, on supported devices, a chosen retention interval. A configured interval may remove older footage before the disk fills. Disabling overwrite stops new recording when storage is full.
4. After enough normal use, compare the prediction with the earliest playable clip and the schedule actually used. If retention is short, investigate the inputs and policy before buying storage. Test whether proposed lower encoding settings still retain the detail you need.

What this does not establish

This arithmetic does not establish an NVR's drive limit, camera support, guaranteed recording quality or motion duty cycle. It assumes a constant total bitrate for the example; changing codecs or enabling motion recording does not justify an invented percentage saving.