The big picture:

A home camera does not grab plain numbers like a smart plug; it sends a steady stream of data that a local box must unpack to decide what to keep.

The camera in this example ships at 3840×2160 pixels and takes 25 frames a second in a dense format known as High Efficiency Video Coding (H.265) [1]. Its code rate ships at 6,144 kilobits a second inside a stated range of 4,096 to 8,192 [1]. That single number sets the size of the whole purchase.

A cloud plan hides this data weight, since the brand keeps the physical disks on their end. Keep the video yourself and you inherit the bill in bytes, which means one lens at the shipped rate fills about 66 GB a day [1]. Frigate, the free, open-source recorder, splits the job into three clear streams for finding motion, saving footage, and live viewing [2].

Detection does not need the full data rate to spot a person in the yard. The base rule is five frames a second, which the project calls correct for almost all cameras [2]. That job runs on a lighter copy of the stream that ships at 256 kilobits a second [1]. Saving the video is the heavy job, and Frigate suggests setting that recording feed to 15 frames a second inside the device’s own settings [2]. The guide gives this tip to keep playback smooth and reduce network strain [2]. That detail matters, because the trick often travels online as a storage fix rather than a speed fix.

The recorder carries its own printed frame limit, and the maker does not state it as a simple camera count. The two-bay box in this example lists a hard cap of 17 channels and 170 total frames a second at 4K in the older Advanced Video Coding (H.264) format [4]. That limit rises to 20 channels with 200 frames a second in the newer H.265 format [4]. It also ships with two free camera licences, and the product page says adding more cameras means buying extra licences [4]. My read is that this frame limit and the software rules are the real walls a buyer hits at the third camera.

By the numbers

  • 66.4 GB — Daily camera volume: At the shipped 6,144 kilobits a second, a single 4K camera writes about 66 GB a day [1], so four lenses kept for a month reach 7.96 terabytes (TB).
  • 44 to 88 GB — Code-rate range: The exact same hardware can be set anywhere from 4,096 to 8,192 kilobits a second [1], which shifts the daily file size by a factor of two.
  • 194.2 hours — Seller card capacity: A 512 GB memory card holds 194.2 hours, or roughly eight days for one camera [1], which works out near 63 GB a day and lets a buyer test any claim.
  • 170 frames — Recorder speed cap: The two-bay box publishes a 4K limit of 17 channels and 170 frames a second [4], so four cameras running at 25 frames a second eat 100 of those 170.

What I’d watch:

What I keep coming back to is that the settings matter far more than the shopping list, and every one of them is visible before the carton is open. A buyer can sketch the whole storage footprint from the public sheets.

  • The recording rule: A stated Frigate setup keeps every frame for three days, motion video for seven, and alert video for 30 [3], which buys a month of the events that matter rather than an empty driveway.
  • The detection stream: Detection runs on the light copy at the base rate [2], so the heavy stream is paid for once, at the moment it is recorded.
  • The licence count: The recorder ships with a couple of free licences and the rest are bought one at a time [4], a cost that turns up at the third camera rather than in the first quote.
  • The math check: Any seller’s space table can be divided by the code rate it prints next to it [1], and a table that disagrees with its own math is worth a second look.

The real cost lands on the third and fourth cameras rather than the first one you hang up. One lens recording to a memory card is a simple weekend project. Four cameras kept for a full month force a disk choice made with real money, and the math above is the only honest way to make it.

The catch

My read starts with two numbers the seller prints about its own product, because they do not quite agree. The code rate implies 66.4 GB a day, while the memory card table implies 63.3 GB [1]. That gap near 5% comes from rounding plus hidden guesses the page never states. Treat that pair of figures as a budget band, and expect a real camera to land inside it rather than exactly on one hard number.

The frame cap belongs to that box’s own recorder app, tested with specific drives fitted under nonstop recording [4]. It says nothing certain about a different recorder app running on the exact same hardware. It also says nothing at all about a laptop doing the same job. Where the software path changes, the speed number changes right along with it.

A separate network and a blocked cloud account are worth doing, but neither changes the heavy volume of bytes a camera writes on a Tuesday afternoon. The same trap shows up in the breaker box, where a printed threshold gets read as your own constant load, which is the argument behind the 80% test for your electrical panel.

At a glance

  • The Big Shift: Managing your own security footage turns a monthly cloud plan into a physical disk purchase. The size of that disk is set by the camera’s code rate and the recorder’s frame ceiling, not by the brand on the box.
  • Why It Matters: A local camera project usually gets planned from a hardware list and an app, then meets the storage bill when the fourth camera arrives and the drives are already installed.
  • What I’d Watch:
  • The code-rate setting: It decides the daily data volume, so it belongs in your purchase notes rather than hidden in a settings menu nobody opens twice.
  • The recording rule: Keeping every frame for a few days and motion events for a month costs far less than keeping everything for a full month.
  • The recorder ceiling: Frame throughput and licences are printed separately, and both run out long before the box looks full.
  • The Catch: The vendor’s own two storage estimates differ by a few percent, the frame ceiling applies to one specific recorder app, and none of this math makes a camera fully private.

Related reading

Sources

[1] Reolink, RLC-810A security camera specifications (code rate, frame rate, resolution, microSD capacity table) — https://reolink.com/product/rlc-810a/ [2] Frigate 0.18 documentation, “Camera setup” (detection frame rate, recording and viewing streams) — https://docs.frigate.video/frigate/camera_setup/ [3] Frigate 0.18 documentation, “Recording” (retention policy: continuous, motion, alerts and detections) — https://docs.frigate.video/configuration/record/ [4] Synology, DiskStation DS224+ specifications (Surveillance Station licences and maximum IP cameras with total frames per second) — https://www.synology.com/en-us/products/DS224+