CCTV recording days depend on usable storage capacity, the combined recorded bitrate, camera count and recording hours per day—not memory-card size or “4K” alone. A 128GB card recording occasional events can last very differently from the same card recording continuously. Cloud retention is a separate plan condition, not a conversion from gigabytes into days.
For continuous recording, a useful planning formula is: days ≈ usable capacity in GB ÷ (10.8 × combined bitrate in Mbps). This uses decimal units and 24 recording hours per day. The examples below are calculations, not measurements of a particular camera, card or hard drive.
Manufacturer information checked on 7 October 2026. Elechid sells products linked in this guide; these are purchasing references, not independent performance tests. The AI-generated cover compares storage options and is not a wiring diagram.
What information do you need before calculating?
Write down the recording destination first: an individual camera's microSD card, a compatible NVR, a hub or a cloud plan. Then record the streams saved at that destination. Live-view quality, recording quality and remote-preview quality can be different settings, so the bitrate displayed for a low-resolution phone preview may not describe the stored files.
- Usable capacity: the space actually available for recording after formatting and any reserved space.
- Recorded bitrate: the data rate of every stream being saved, including additional lenses, secondary streams or audio where relevant.
- Number of cameras: add their individual recorded bitrates rather than assuming every camera uses the same value.
- Recording schedule: continuous all-day recording, selected hours or triggered clips.
- Retention behaviour: automatic overwrite, stopping when full, or a cloud plan's expiry rules.
Resolution describes the picture dimensions, while bitrate describes the amount of data recorded per second. Two cameras producing the same resolution can create different file sizes because their compression, frame rate and quality settings differ. Variable-bitrate recording can also change with scene detail and movement.
A transparent storage formula
One megabit per second recorded for one hour is approximately 0.45GB in decimal units: 1,000,000 bits × 3,600 seconds ÷ 8 ÷ 1,000,000,000. Therefore, a constant 4Mbps stream uses approximately 1.8GB per hour, or 43.2GB over 24 hours. The unit conversion is arithmetic, not a manufacturer performance claim.
For a schedule shorter than a full day, use daily GB ≈ 0.45 × combined Mbps × recorded hours per day, then divide usable capacity by that daily amount. Include all streams actually stored and leave room for uncertainty. A camera's configured maximum bitrate is not necessarily its measured average, and file-system or recorder overhead is not represented automatically by this simplified equation.
Reolink's storage calculation guidance highlights the need to include saved main/sub-streams and additional lenses. Its storage calculator is another planning reference. Use model-specific recording compatibility documentation: a generic statement about battery cameras should not override a current supported-mode list.
128GB, 256GB and 2TB: worked examples
The following table assumes 90% of labelled decimal capacity is available, constant aggregate bitrate as shown, and continuous 24-hour recording. The 90% allowance is simply an illustrative planning assumption—not the measured usable capacity of any product. Audio, extra streams and system overhead must already be allowed for in your actual inputs.
| Illustrative setup | Assumed usable capacity | Daily data | Calculated retention |
|---|---|---|---|
| 128GB, one camera at 4Mbps | 115.2GB | 43.2GB | About 2.7 days |
| 256GB, one camera at 4Mbps | 230.4GB | 43.2GB | About 5.3 days |
| 2TB, one camera at 4Mbps | 1,800GB | 43.2GB | About 41.7 days |
| 2TB, four cameras at 4Mbps each | 1,800GB | 172.8GB | About 10.4 days |
| 256GB, one camera at 8Mbps | 230.4GB | 86.4GB | About 2.7 days |
The lesson is not that every 256GB card lasts five days. Doubling the recorded bitrate approximately halves calculated retention when everything else remains unchanged. Adding cameras to one recorder increases the combined data rate, so a large hard drive can fill much sooner than expected.
If your system needs 14 days with four constant 4Mbps streams, the same simplified calculation gives 14 × 172.8 = 2,419.2GB of usable recording space. With the illustrative 90% allowance, labelled capacity would need to exceed about 2,688GB before other margins. This is a planning example, not advice to install a particular drive: verify the NVR's supported drive capacity and exact hardware first.
Why event recording cannot promise a fixed number of days
Event recording depends on the total duration actually saved each day, including supported pre-event and post-event periods. “Twenty alerts” does not mean twenty equally sized clips. Overlapping triggers may merge, clips may have different lengths, and a busy entrance can create a substantially different daily total from a quiet room.
To estimate an event-recording setup, measure several representative days of saved file volume or total recorded duration at the chosen settings. Use the busiest relevant day as a planning check rather than relying only on a quiet weekday. Do not reduce detection coverage purely to make storage last longer if that removes the event you need to capture.
A missing beginning is also different from an overwritten old clip. If the camera did not capture the lead-in, a larger memory card cannot recover it. Our battery CCTV recording-mode troubleshooting guide explains that distinction and the importance of checking supported pre-recording modes.
microSD, NVR and cloud: three different decisions
| Storage option | Main planning question | Important limitation |
|---|---|---|
| Camera microSD | Does the exact camera support this card's capacity, format and recording workload? | Storage is attached to that camera; faults, removal or overwrite can affect access. |
| Compatible NVR | What combined streams, camera count and hard-drive capacity are supported? | One central recording destination is not automatically an off-site backup. |
| Cloud plan | Which camera, region, recording mode and retention window does the plan cover? | Subscription duration and footage retention are different; upload and service conditions matter. |
The Reolink NVS8 with 2TB hard drive is a product reference for recorder planning. Check camera compatibility, supported storage expansion and firmware rather than treating “eight ports” as a promise that all cameras or functions work. A PoE port count does not by itself establish the complete system's network or power requirements.
For card-based storage, compare the Kodak Endurance microSD options against the camera manual. Endurance, capacity and speed markings describe different things. Do not assume V30 or U3 is a universal minimum for all CCTV cameras, or that buying a faster card changes a camera's supported maximum capacity.
A SpotCam one-year cloud recording plan describes a subscription purchase period, not automatically one year of stored video. Before subscribing, confirm the exact plan's rolling footage window, eligible camera, event versus continuous recording, export limits and renewal conditions. Do not infer those terms from another brand's cloud service.
How to verify retention on your own installation
- Record the full camera/NVR model, firmware, storage device and recording settings.
- Confirm where recordings are actually saved and whether overwrite is enabled.
- Check storage health and available capacity without formatting or deleting recordings.
- Observe daily storage use across representative quiet and busy periods.
- Compare the oldest playable timestamp with the expected retention window.
- Export a non-sensitive test clip, play it on another device and confirm its timestamp and audio where relevant.
- Recheck after adding cameras, changing bitrate, enabling extra streams or altering the recording schedule.
This procedure produces installation-specific evidence without exposing private footage. Keep a simple record of dates, settings and file volumes; you can share those numbers with support before sharing images. An advertised drive size and a screenshot of live view do not demonstrate that last week's footage is recoverable.
If an input is unknown, label it as unknown rather than inserting an apparently precise figure. You can calculate a range using clearly stated lower and higher bitrate assumptions, then replace them with observed file volumes. Keep the assumptions alongside the result so anyone reviewing the plan can see why it changes. This is especially useful when a system has not yet been installed or the recording schedule is still undecided.
Frequently asked questions
Will an NVR automatically remove monthly fees?
Local recording can be selected without a cloud recording subscription where the product supports it, but do not generalise every service or feature. Internet service, optional cloud features, hardware replacement and installation are separate costs. Compare the complete setup and required functions, not only a “no monthly fee” slogan.
Is lowering quality the best way to keep more days?
It can reduce storage use, but first check whether the resulting footage still answers your purpose. A longer archive is not useful if the important action becomes unreadable. Test an exported clip at the intended viewing size before accepting the compromise.
Can I format the card when earlier clips disappear?
Export important recordings first. Formatting can erase remaining footage and does not reverse automatic overwrite. Check schedules, filters, card status and the actual recording destination before treating a storage problem as a card fault.
What should I provide when asking Elechid to help plan storage?
Provide the camera count, full models, desired recording hours, retention days and current bitrate settings. Say whether continuous recording is essential and whether cloud storage is acceptable. We can then check suitable CCTV recorders and accessories against those requirements rather than promising a fixed duration from capacity alone.
