Operations

How Much Storage Do CCTV Cameras Need? Worked Examples

How much storage do CCTV cameras need? Use bitrate times time, with worked examples for 1080p and 4K, H.265, motion recording, retention and headroom.

Ceptory TeamUpdated 8 min read
A search bar above four video results with the matching loading dock clip highlighted in coral

TL;DR

One 1080p camera at 4 Mbps uses about 43 GB a day, or 1.3 TB over 30 days. Multiply by camera count, adjust for codec and motion recording, then add 15 to 25 percent headroom. Worked examples below.

How much storage do CCTV cameras need? Storage equals bitrate multiplied by recording time, multiplied by camera count and retention days. One 1080p camera streaming 4 Mbps around the clock writes about 43 GB a day and about 1.3 TB over 30 days. This guide walks through the formula, then works four realistic examples so you can size an NVR or server without guessing.

What is the CCTV storage formula?

The formula is: storage = bitrate × seconds recorded ÷ 8. A camera writes its bitrate to disk for every second it records. One megabit per second is 0.45 GB per hour, which is the rule of thumb used by the CCTV Storage Calculator.

So a 4 Mbps camera recording 24 hours writes 4 × 0.45 × 24 = 43.2 GB a day. Over 30 days that is 1,296 GB, or about 1.3 TB.

Three things change the answer:

  1. Bitrate, set by resolution, frame rate, codec and scene detail.
  2. Recording mode, continuous or motion-triggered.
  3. Retention, the number of days before the oldest footage is overwritten.

What bitrate should I use for each resolution?

Use your camera's actual stream bitrate, found in its stream settings or in the NVR's live view. If you do not have it yet, these planning values at about 15 to 30 fps on H.264 are common:

CameraTypical bitrateGB per day (24 h)TB per 30 days
1080p, 15 fps2 Mbps21.60.65
1080p, 30 fps4 Mbps43.21.30
4K, 30 fps12 Mbps129.63.89

The 1080p figures match the examples in the CCTV Storage Calculator and the CCTV Bandwidth Calculator. The 4K value is an illustrative midpoint inside the 8 to 16 Mbps range the bandwidth tool quotes for 4K cameras; your camera may differ. Real bitrates swing with scene detail, night noise and lens and compression settings.

The video file size calculator works the same sum for individual files, which helps when you export a clip for review.

Example 1: How much storage do 16 cameras need for 30 days?

Sixteen 1080p cameras at 4 Mbps, recording continuously for 30 days, need about 20.7 TB before headroom.

  1. Per camera per day: 43.2 GB.
  2. Per camera for 30 days: 1,296 GB.
  3. Sixteen cameras: 20,736 GB, about 20.7 TB.
  4. Add 20 percent headroom: about 24.9 TB.

That is the number to compare with the usable capacity of your drives after RAID, not the raw capacity printed on the box.

Example 2: What does H.265 save?

H.265 cuts the same site to about 12.4 TB before headroom if it needs 40 percent less bitrate. Use 60 percent of the H.264 figure: 20.7 TB × 0.6 = 12.4 TB, or about 14.9 TB with 20 percent headroom.

Treat 40 percent as a planning figure. Vendor savings claims are marketing figures: IPVM's 2015 report on Axis Zipstream notes Axis claimed its compression could lower bandwidth and storage requirements by an average 50 percent or more, and that H.265's own headline claim is "up to 50" percent savings. IPVM also found bitrates vary hugely between cameras and scenes, so predicting the saving in advance is near impossible. Smart codecs can save more on static or night scenes and less on busy ones, so test one camera over a week.

Example 3: What if cameras record on motion only?

Motion-only recording multiplies storage by the share of time the camera actually records. If each camera records about 6 hours of a 24-hour day, that is 25 percent, so Example 1 drops from 20.7 TB to about 5.2 TB.

The trade-off is risk. Motion recording can miss the quiet seconds before an event, and a camera facing a busy street may trigger almost constantly, giving no saving at all. Many sites record continuously on entrances and cash areas and on motion elsewhere. Pre-event buffers help, so check that your recorder keeps a few seconds before the trigger.

Example 4: How does retention change the total?

Retention scales storage linearly. One 4 Mbps 1080p camera needs about 1.3 TB for 30 days, about 2.6 TB for 60 days and about 3.9 TB for 90 days.

RetentionOne camera16 cameras
30 days1.30 TB20.7 TB
60 days2.59 TB41.5 TB
90 days3.89 TB62.2 TB

Your required retention may be set by policy, contract, insurer or law. Check official sources for your region and industry rather than assuming a number; a retention period set by a regulator can override a storage budget. Longer retention is also worth thinking about for investigations: footage that has been overwritten cannot be searched, as covered in how to search CCTV footage for a person or vehicle. For how to choose the period itself, see how long to keep CCTV footage.

Why do real systems need more than the calculated number?

Real systems need more than the arithmetic because several overheads sit on top of it. Plan for each of these before you buy drives:

  • Decimal versus binary terabytes. Drive makers count 1 TB as 1,000 GB. Operating systems often report binary units, so a drive sold as 8 TB shows as about 7.3 TB. A plan that ignores this runs about 9 percent short.
  • RAID overhead. As the standard RAID levels overview explains, a RAID 5 set gives up one drive of capacity to parity, and RAID 6 gives up two. Four 8 TB drives in RAID 5 give about 24 TB usable before the unit conversion above, not 32 TB.
  • Night and busy-scene bitrate. Constant-bitrate cameras write the same amount all day, but variable-bitrate cameras write more when there is noise, rain or movement. Night image noise can raise a stream well above its daytime average.
  • Audio, metadata and events. If cameras record audio, add it. Event clips, snapshots and exported evidence copies also take space.
  • Growth. Sites add cameras. Sizing for 20 to 25 percent more cameras than today is cheaper than replacing a recorder in a year.

Putting those together for Example 1: 20.7 TB of footage plus 20 percent headroom is 24.9 TB. In RAID 5 with 8 TB drives you need usable capacity of at least 24.9 TB in decimal units, so five drives (4 usable, 32 TB) is the minimum, and six drives gives room to grow. Always check your own recorder's RAID options and its manufacturer's sizing guidance.

How do you check your estimate against reality?

Check the estimate by measuring one week of real recording. Estimates are a starting point; your recorder knows the truth.

  1. After a week, read the recorder's storage page and note the space used by one camera.
  2. Divide by seven to get GB per day, then compare it with your calculation. A gap of more than 20 percent means the bitrate setting differs from what you assumed.
  3. Compare a day with heavy activity against a quiet one. The difference tells you how much headroom the busiest period needs.
  4. Extend to the full retention: multiply the busiest sensible daily figure by the retention days.
  5. Re-check after any change of firmware, codec, frame rate or lighting, because each can move the bitrate.

If measured use is well below plan, you may be able to extend retention rather than shrink the array. If it is above plan, lower the frame rate on low-risk cameras (10 to 15 fps is often enough for a corridor), switch codecs where the camera supports it, or move some cameras to motion recording.

What about network bandwidth?

Every camera streams at its bitrate whether or not anyone watches, so 16 cameras at 4 Mbps put about 64 Mbps on the recording network. That fits gigabit switching, but remote viewing goes through your internet upload. The CCTV Bandwidth Calculator says uploads for cloud review use about 80 percent of the advertised upload speed after overhead. One hour of a 4 Mbps camera is about 1.8 GB and takes roughly 6 minutes at 50 Mbps upload.

For worked LAN totals, remote viewing math, and upgrade triggers, see the dedicated guide how much bandwidth CCTV cameras need.

Storage keeps footage; search makes it findable. Your recorder or NAS holds weeks of video, but nobody can watch it all: reviewing a day from 16 cameras is 384 hours of footage. The video review cost calculator turns that into labour cost, and beyond manual video review explains why automation matters.

Ceptory does not replace the recorder. It indexes recorded video that you upload or add by URL, then searches scenes, speech and on-screen text in natural language through its search feature. Because you choose what to index, you do not need to index everything you store. Pricing is $0.042 per minute indexed plus $0.0015 per minute infrastructure, and search is $4 per 1,000 queries, with the first 10 minutes of indexing free (pricing). At that rate, indexing one full day from one camera (1,440 minutes) is about $62.64, which is why exporting the incident window is usually the better plan than indexing a whole archive. The video intelligence versus storage comparison and video intelligence versus VMS guide cover where each layer fits.

Related: a worked example for Indian societies is in illegal parking in a housing society: prove it with CCTV.

What should you do now?

  1. Read the real bitrate from each camera type, not the spec sheet maximum.
  2. Decide the recording mode for each camera group: continuous or motion.
  3. Confirm the retention period you need from your policy or the official rule for your sector.
  4. Run the numbers in the CCTV Storage Calculator.
  5. Add 15 to 25 percent headroom and subtract RAID overhead from raw capacity.
  6. Test one H.265 or smart-codec camera for a week before relying on its savings.
  7. Plan the export route for incident clips so they can be indexed and searched when needed, and budget analyst time with manual video review cost worked examples.

Storage planning is the unglamorous half of video security: get it right and the footage is there when someone asks. When you need to find a moment in it, try Ceptory on a short clip and see how natural-language search compares with scrubbing the timeline.

Frequently asked questions

How much storage does one CCTV camera need per day?

A 1080p camera streaming 4 Mbps around the clock writes about 43 GB a day. Half the bitrate halves the storage, and a 4K camera at 12 Mbps writes about 130 GB a day. Read your camera's real bitrate for an exact figure.

How do I calculate NVR storage for 16 cameras?

Multiply the per-camera daily storage by 16 and by the retention days, then add headroom. Sixteen 4 Mbps cameras for 30 days need about 20.7 TB before headroom, or about 12.4 TB with H.265 at 40 percent less.

Does H.265 really save storage over H.264?

Usually, yes, but the amount varies. Vendors market H.265 savings of up to about 50 percent, and the CCTV Storage Calculator assumes 40 percent. Real savings depend on the scene and camera model, so test one camera before sizing a whole site.

How much headroom should I add to the calculated storage?

Add 15 to 25 percent. Drives are sold in decimal terabytes, RAID uses part of the raw capacity, and bitrates rise at night and in busy scenes. Buying exactly the calculated figure usually means footage is overwritten early.

Does storing footage longer help with AI video search?

Longer retention keeps more footage available to search, but you only pay to index what you choose to. With Ceptory you export and index just the clips you need, so retention length and indexing cost are separate decisions.

Ceptory

Search your own footage in plain language. The free tier indexes 60 minutes of video.