To specify recording retention, ask for the arithmetic, not just a number of days. Storage used equals bitrate times seconds recorded per day times days times cameras, and every one of those inputs is an assumption you can check. Bitrate depends on the codec, the rate-control mode and how busy the scene is. Recording mode (continuous, motion or scheduled), sub-streams, RAID protection and decimal versus binary drive units all move the result. Retention days themselves come from the owner’s policy, insurer or applicable law, not from the recorder. Then specify how video leaves the system: native export with its player, an open-format copy, accurate time records and any integrity check the platform offers.
Evidence label: Documentation-based guide. ClearTrade Report Editorial Team checked documents from the Scientific Working Group on Digital Evidence (SWGDE), the National Institute of Standards and Technology (NIST), Synology, Ubiquiti, Reolink and Axis Communications on November 16, 2026. No outside professional review was performed and nothing was tested. Companies named are documentation examples, not recommendations. This guide contains no affiliate links.
Every retention claim rests on four inputs
Reolink’s support article on how long its NVRs can record puts it plainly: “The size of the recording is mainly determined by its bit rate.” Bitrate is data per second, usually stated in kilobits per second (kbps) or megabits per second (Mbps). Multiply it by the seconds recorded and you get stored data.
Reolink’s CCTV storage formula article writes the full equation as “Storage Space (GB) = Bitrate (Kbps) * 1000/8 * 3600 * 24 * Cameras * Days/1000 000 000.” The same article lists “recording modes (motion triggered recording or 24/7 recording), amount of motion activities” among the factors that change real use. So a retention spec needs four stated inputs: the bitrate per stream, the hours per day each camera actually writes, the number of cameras and streams, and the number of days required.
Camera count also drives switch power, which is a separate calculation covered in PoE Power Budgets Explained.
Worked example: storage math you can check
Here is the arithmetic with a round bitrate chosen only for illustration. Assume 4 Mbps (4,000 kbps) per camera. That is an assumption for the example, not a figure for any product. Replace it with the average bitrate your recorder reports for your own cameras.
- Bits per camera per day: 4,000,000 bits per second x 86,400 seconds = 345,600,000,000 bits.
- Bytes per camera per day: 345,600,000,000 / 8 = 43,200,000,000 bytes, or 43.2 GB (decimal, 1 GB = 1,000,000,000 bytes).
- Eight cameras recording 24 hours: 43.2 GB x 8 = 345.6 GB per day.
- Thirty days: 345.6 GB x 30 = 10,368 GB, or 10.368 TB (decimal, 1 TB = 1,000,000,000,000 bytes).
- The same total in binary units: 10,368,000,000,000 / 1,099,511,627,776 = about 9.43 TiB.
Now add a sub-stream. Reolink says that when “Calculating storage time, we need to consider both the bitrate of the main stream and the sub-stream.” Its single-lens example uses a main stream of 6144 kbps and a sub-stream of 512 kbps. If each camera in our example also records a 500 kbps sub-stream (again an assumption), the per-camera total is 4,500 kbps and the 30-day total becomes 11.664 TB, about 10.61 TiB.
Recording mode changes the hours. If motion recording wrote the equivalent of 6 hours of full-bitrate video per camera per day (an assumption you would need to verify from your own logs), the 30-day main-stream total drops from 10.368 TB to 10.368 x 6 / 24 = 2.592 TB. That saving is only as good as the 6-hour guess.
Decimal TB, binary TiB and why calculators disagree
Drive makers sell capacity in decimal terabytes. Software often reports binary tebibytes (TiB), where 1 TiB is 1,099,511,627,776 bytes. That is about 10 percent more bytes than a decimal TB, so a “10 TB” figure in one tool can be about 9.1 TiB in another.
Published calculators do not all use the same convention. Reolink’s formula article divides by 1,000,000,000 to get GB, which is decimal. Reolink’s NVR article instead writes “Recording Duration (hours) = (Storage Capacity (TB)×8×1024×1024×1024) ÷ (Bitrate (kbps)×3600),” treating each terabyte as 1024 x 1024 x 1024 kilobits times 8. That works out to about 1.074 trillion bytes per “TB,” which is neither a decimal terabyte nor a true tebibyte, so label it as the calculator’s own convention. Run 4,096 kbps on a 2 TB drive through that NVR formula and you get about 48.5 days. Treat the 2 TB as 2,000,000,000,000 decimal bytes and divide by the same 4,096,000 bits per second, and you get about 45.2 days. Both are reasonable estimates, and Reolink itself says “The estimates below are for reference only.” The lesson for a spec is simple: write down which unit the number uses.
Bitrate moves with the scene, the codec and the rate control
Bitrate is the least stable input. Axis Communications’ white paper on bitrate control for IP video says “A low-complexity scene would produce a stream with a low bitrate” and “A high-complexity scene will produce a stream with a high bitrate.” Under variable bitrate (VBR), “Motion or other events in the scene can cause the stream size and bitrate to increase significantly.”
Other modes cap or average the stream. Axis says “MBR guarantees that the bitrate stays below a set limit regardless of video scene complexity.” With average bitrate (ABR), “A video stream is assigned a certain amount of storage,” and Axis notes “The ABR algorithm needs a time period of 24h with typical scene variations.” Axis also says “CBR is not optimal for storage because it may contain padding data and waste storage space.” For night scenes, the paper suggests you “Adjust night-mode parameters to reduce noise at night.”
Codec and compression features matter too, but savings are scene-dependent. Axis’s Zipstream white paper gives expected reductions as “10-50% (depending on Zipstream strength parameter, scene motion, and scene content)” for one algorithm. It also cautions that “in some cases Zipstream with H.264 could still deliver lower bandwidth” than H.265, that “H.265 ecosystem support is still limited and lacking real progress,” and that “Not all clients or VMS may support smooth playback of video with this algorithm enabled.” Synology’s Surveillance Station specifications list “Supported video formats: MJPEG, H.264, H.264+, H.265, H.265+, MPEG4, and MxPEG.” A spec should therefore name the codec and rate-control mode, and base storage on a measured average over at least a full day, including night.
Recording modes, schedules and tiered retention
Ubiquiti’s help article on UniFi Protect recording modes and schedules describes “Always” as “Continuous recording for complete coverage” and says “Detection Only” “Records only triggered events to reduce storage and incidental footage.” It adds that “Schedules enable recordings only at specified times, conserving storage for higher-priority periods.” Reolink’s NVR article agrees on the direction: “Motion-based recording makes more efficient use of storage, resulting in longer retention time than 24/7 recording.” The trade-off is that nothing between events is kept.
Retention can also be tiered. Ubiquiti’s storage and retention article describes setting “a high-quality retention period (e.g., 30 days),” after which “footage transitions to low quality,” and warns that “Footage downgraded to low quality cannot be restored to high quality.” If a requirement is “90 days,” a spec should say at what quality. Synology’s specifications say “Recording rotation can be triggered by retention time or storage size,” so check which trigger is set. SWGDE’s DVR guidance (below) lists “Whether overwrite is enabled or set to stop if HDD is full” as something to document.
The number of days is a policy decision. Ubiquiti’s UniFi Access recording article offers custom periods from 7 days to 3 years and notes “(Some regions require retention by law.)” This guide did not check any specific legal rule. Retention periods come from the owner’s policy, insurer or applicable law.
RAID and usable capacity
Raw drive capacity is not retention capacity. Ubiquiti’s article on storage protection and data redundancy lists effective capacity for its Basic Protection level as 67% to 75% on UNVR and ENVR recorders. It says the table “helps clarify how retention time and redundancy are intertwined,” and warns that “Using mismatched capacity and speed drives will limit overall retention to the smallest and slowest drive.”
Apply that to the worked example. To hold 10.368 TB of usable recordings at 67% effective capacity, you need about 10.368 / 0.67 = 15.5 TB of raw drives. At 75%, you need 10.368 / 0.75 = 13.8 TB. Leave further margin for bitrate growth, since Axis says VBR can rise significantly with motion. A hot spare, which Ubiquiti calls “a standby drive reserved for emergencies,” adds no recording capacity.
Specify evidentiary export, not just storage
Storage that cannot be exported cleanly does little for an investigation. SWGDE’s Best Practices for Data Acquisition from Digital Video Recorders (17-V-002, version 1.4) says “The evidence from DVRs is perishable and should be acquired as soon as possible.” It says “A native file format or proprietary file format is likely to provide best evidence for legal authenticity purposes” and “Additionally, the proprietary player and/or codec should be acquired directly from the device or through the manufacturer.” It also says “A secondary export of the open file format should also be acquired if time is available.”
SWGDE asks examiners to document “System time/date vs Government-standardized atomic-clock time/date (document device used for actual time and date)” and states “Do not change the time and date on the DVR system.” Its optional items include “Earliest recorded date/time” and “Storage capacity/storage used.” It warns that a network stream “may be downgraded due to bandwidth limitations (e.g., higher compression, lower resolution, lower frame rate),” and that “Adjusting the settings during acquisition is not recommended.”
A NIST presentation on digital video output standards describes why this is hard. It says “video playback, export, and analysis frequently requires vendor-only software” and “Exporting video often involves data conversion resulting in degradation, loss of metadata, and costly delays.” It calls for a “standard codec” in a “flexible + playable container.”
Platforms handle integrity differently. Synology’s specifications say “Recordings can be downloaded as MP4 or AVI files” and “Text and image watermarks can be overlaid when downloading recordings.” Its security features page says “All downloaded recordings will be embedded with digital signature for validation,” checked by a desktop tool. The specifications add a limit worth writing into any procedure: “Recordings with watermarks cannot be authenticated by Synology Evidence Integrity Authenticator.” Ubiquiti’s export and archiving article says exporting lets you download clips “for quick sharing, such as providing evidence,” and its Case Manager article says a case “can be exported as a zipped file containing the selected clips and a descriptive PDF.” Closing a case “Locks the case, preventing further edits.” That article does not describe hashes or checksums on the export.
| Spec item | What to state | Why it matters (source) |
|---|---|---|
| Average bitrate per stream | Measured kbps over 24 hours, main and sub-stream listed separately | Reolink: count both streams; Axis: bitrate rises with scene complexity |
| Codec and rate control | For example H.264 or H.265; VBR, MBR or ABR | Axis: savings vary by scene; H.265 playback support is limited |
| Recording mode and schedule | Continuous, detection only, or scheduled, per camera | Ubiquiti and Reolink: detection recording uses less storage but keeps only events |
| Days at full quality | Days required, and whether footage may be downgraded later | Ubiquiti: downgraded footage cannot be restored |
| Units | Decimal TB or binary TiB | Calculators differ; about 10% gap per terabyte |
| Usable capacity | Raw drives, RAID level, effective percentage, hot spares | Ubiquiti: 67% to 75% effective on Basic Protection (UNVR, ENVR) |
| Overwrite behavior | Overwrite oldest, or stop when full; rotation by age or size | SWGDE and Synology |
| Export package | Native file plus player, open-format copy, time offset record, integrity check | SWGDE, NIST, Synology, Ubiquiti |
Know the limits of this guide
This guide covers retention math and export. It does not help choose cameras, recorders or a security design. The bitrate in the worked example is illustrative and is not a product figure. Real bitrate depends on resolution, frame rate, codec settings, lighting and scene activity, and should be measured on site. Vendor calculators use different unit conventions and are described by their publishers as estimates. Manufacturer features named here, such as Synology’s digital signature or Ubiquiti’s Case Manager, were described from documentation and were not tested, and they may change with firmware. SWGDE documents are best-practice guidance for examiners, not law. This guide did not check any statute, regulation, insurance policy or court rule on how long video must be kept or how it must be produced. Retention periods come from the owner’s policy, insurer or applicable law, and handling evidence for a case may need advice from counsel or the investigating agency.
Primary references checked November 16, 2026: SWGDE, “Best Practices for Data Acquisition from Digital Video Recorders,” 17-V-002, version 1.4; NIST, “Digital Video Output Standards” (Garris, Laamanen, Russell, Nadel); Synology, “Surveillance Station” software specifications; Synology, Surveillance Station security features page; Ubiquiti, “Managing Storage and Retention in UniFi Protect”; Ubiquiti, “UniFi Protect Recording Modes & Schedules”; Ubiquiti, “Storage Protection and Data Redundancy in UniFi (RAID)”; Ubiquiti, “Exporting Clips & Cloud Archiving with UniFi Protect”; Ubiquiti, “Build Incident Reports with UniFi Case Manager”; Ubiquiti, “Configuring Unlock Event Recording in UniFi Access”; Reolink, “How Long Can Reolink NVR Record for”; Reolink, CCTV storage calculation formula article; Axis Communications, “Bitrate control for IP video” white paper; Axis Communications, “Axis Zipstream technology” white paper.
Frequently asked questions
How many days of video should a business keep?
The documents checked here do not set a number. Retention periods come from the owner’s policy, insurer, or applicable law. UniFi’s Access help article notes that some regions require retention by law. Set the period first, then size storage to meet it.
Why does my recorder hold fewer days than the calculator promised?
Calculators assume a bitrate, a recording mode and a unit convention. Axis says motion or other events can cause the bitrate to increase significantly under variable bitrate. Reolink says storage math must include both the main stream and the sub-stream. In the example in this guide, the unit convention alone moves a 2 TB estimate from about 48.5 days to about 45.2 days.
Is motion recording enough to meet a retention requirement?
It can stretch storage, but it changes what is kept. UniFi describes Detection Only as recording only triggered events, and Reolink says motion-based recording gives longer retention than 24/7 recording. Footage between events is not recorded, so decide whether that gap is acceptable for your purpose.
What should I ask for when exporting video for police or an insurer?
SWGDE says a native or proprietary file format is likely to provide best evidence for legal authenticity purposes, and that the proprietary player or codec should be acquired too. A secondary open-format export is useful if time allows. Record the recorder’s time against an accurate clock and do not change the recorder’s time.
Disclaimer: This guide is general information based on manufacturer, standards and government documents, not professional security, legal or IT advice for a specific building or product. Follow your recorder’s documentation, your organization’s retention policy and any instructions from counsel, insurers or investigators. Rules and ratings may change. AI tools assisted with drafting. ClearTrade Report Editorial Team checked the cited sources and edited this guide.
Need a qualified professional?
Trusted Pros uses visible license-verification states and never ranks paid listings above unpaid listings.
