Blue Iris retention planning
Blue Iris Storage Calculator: Retention & Drive Sizing
A Blue Iris storage plan should begin with measured camera bitrate, not megapixel labels or a fixed number of gigabytes per camera. This calculator converts aggregate stream bitrate into daily recording volume, retention capacity, free-space reserve and optional duplicate-copy capacity, then connects the result to surveillance-drive choices.
Quick answer
Calculate from bitrate and recorded time
Enter the average bitrate actually produced by each camera, the recording fraction and retention target. The result shows estimated terabytes per day and the capacity needed before formatting, filesystem behavior and real-world bitrate variation are considered.
Live Amazon infrastructure
Current hardware for this Blue Iris decision
Sprint 7B owns PoE switch, PCIe NIC, UPS, DAS and NAS classes. Surveillance HDD cards are read from Sprint 7A without writing to its catalogue, so Blue Iris recording drives are not duplicated. Accessory-only, USB-NIC, replacement-battery and wrong-product listings are rejected.
Buying decision
Buy capacity after the retention math
A larger hard drive is not automatically a better design. The practical choice depends on required retention, the number of recording volumes, replacement strategy, write concentration and whether critical evidence is copied elsewhere.
Interactive decision tool
Blue Iris Storage & Retention Calculator
Use measured camera bitrate, equipment watts and the retention policy you actually need. The tools use direct unit conversion and planning headroom; they do not invent camera throughput, PoE draw, disk speed or UPS runtime. Verify exact product specifications before purchase.
Compatibility checklist
Four checks before buying surveillance infrastructure
Measure streams instead of guessing
Use actual camera Mbps for storage and network planning. Resolution and codec labels alone do not determine bytes written or link utilization.
Count PoE ports and watts separately
A switch needs enough powered ports and enough total power budget. Night IR, heaters and PTZ movement can change the worst-case load.
Do not convert VA directly into runtime
UPS runtime depends on the exact battery system and connected watts. Use manufacturer runtime data after the protected load is calculated.
Backup must survive a different failure
A second copy is useful when it has an independent retention and recovery path. RAID or another folder on the same recorder is not the same protection goal.
Bitrate is the cleanest storage input
Resolution and frame rate influence bitrate, but the encoder settings ultimately determine how much data reaches the recorder. Two 4K cameras can consume very different bandwidth when one is tuned for a quiet scene and another records constant motion. Use the camera status or stream statistics to obtain a realistic Mbps figure, then update the calculation after several normal days of operation.
Continuous and event recording need different math
A continuously recorded stream writes for the entire day, while an event-driven configuration records only a fraction of the clock. The calculator therefore uses a recorded-time percentage rather than assuming every motion system saves the same amount. If pre-trigger, post-trigger or frequent activity makes the camera record most of the day, enter a high percentage instead of relying on the word event.
Retention is a policy decision before it is a disk decision
Thirty days of footage may sound attractive, but the right number depends on when incidents are normally discovered and how quickly evidence can be exported. A home driveway may have a different requirement from a business entrance or warehouse. Define the period that must remain immediately searchable, then add an archive or export policy for footage that has legal, insurance or operational value.
Free-space reserve protects the operating margin
A capacity estimate that exactly fills a disk leaves no room for bitrate spikes, database growth, temporary exports or changes in camera count. This tool adds a configurable reserve to the calculated retention requirement. Treat that reserve as headroom, not extra advertised retention, and keep monitoring actual free space so a slowly growing workload does not silently consume the buffer.
Drive count matters even when one disk is large enough
A single high-capacity drive may satisfy the raw terabyte number, but it also concentrates recording writes and creates one replacement event for the entire archive. Multiple recording volumes can divide the write path and simplify staged upgrades. The correct layout depends on chassis bays, controller ports, cooling and how Blue Iris folders are assigned, so capacity and topology should be planned together.
Separate system and recording roles when practical
Windows, the Blue Iris application and its database favor low latency and quick small-file access, while video retention is dominated by sustained sequential capacity. Keeping the operating system and database on an SSD while recordings use surveillance HDDs makes the failure domains and upgrade paths easier to understand. This is an architecture recommendation rather than a requirement that every small system use two devices.
Surveillance drives are the natural long-retention class
WD Purple and Seagate SkyHawk families are sold specifically for surveillance workloads, which makes them a sensible starting class for continuous recording. Exact capacities, workload ratings and warranty terms still vary by SKU. The live cards come from Sprint 7A when that catalogue is installed, and Cloudzat keeps model, capacity, condition and seller evidence visible instead of treating a family name as one specification.
Backup is different from retention redundancy
Keeping two copies of important footage is a data-protection decision, not simply a way to increase retention. A mirrored storage layout protects against some device failures but does not automatically protect against deletion, ransomware, configuration mistakes or loss of the recorder. Important clips should have a deliberate independent copy path, preferably to another device or location when the evidence value justifies it.
Write bandwidth should be checked against the recording path
The storage calculator produces aggregate camera Mbps, which can be compared with the capabilities of the controller, drive set and network path. The number is not a benchmark promise because filesystem behavior and concurrent playback add overhead. If the camera stream total becomes large, distribute recording workloads and confirm that every link from switch to NIC to disk can sustain the measured traffic with headroom.
Exports and remote playback create bursty secondary demand
The recorder may be writing continuously while an operator searches the timeline, exports a long clip and several remote users view streams. Those activities do not change the underlying retention formula, but they can change the responsiveness of a nearly saturated disk or network. Systems used for active investigations benefit from more I/O headroom than unattended recorders that are rarely accessed.
Expansion should be designed before the first drive is full
Adding cameras later increases both storage and network load. Leave drive bays, SATA or HBA ports, power connectors and cooling capacity for the expected final deployment rather than only the initial camera count. An enclosure or NAS used for backup also needs a growth plan so the secondary copy does not become smaller than the primary retention set after the first expansion.
Recalculate with real measurements after deployment
The first estimate is a procurement tool. After cameras have operated through daytime, nighttime, motion, weather and normal business activity, record the real bitrate and daily disk growth. Feed those values back into the calculator and adjust retention limits or storage capacity. Measured behavior is more trustworthy than a generic resolution-to-storage chart because it captures the settings and scenes you actually run.
Questions people ask
Blue Iris Storage Calculator FAQs
How much storage does Blue Iris need per camera?
There is no single per-camera figure. Use average camera bitrate, the percentage of time recorded and retention days; the calculator converts those inputs into capacity.
Does H.265 always cut storage in half?
No. Codec efficiency depends on camera implementation, scene complexity and quality settings. Use the measured Mbps produced by the camera rather than assuming a fixed percentage saving.
Should I record Blue Iris footage to an SSD?
SSDs can work, but long surveillance retention is usually a capacity-heavy workload. Many systems use an SSD for Windows/database duties and surveillance HDDs for the video archive.
How much free space should I leave?
Use a deliberate reserve rather than filling the disk to the calculated byte. The tool lets you choose the reserve percentage so growth and bitrate variation have operating room.
Is a mirror the same as a backup?
No. A mirror can keep a storage set available after some device failures, but independent backup protects against a different set of risks such as deletion or loss of the recorder.
Can I use one very large hard drive?
Possibly, if capacity, sustained write load, chassis cooling and failure tolerance fit the deployment. Larger installations often benefit from multiple recording volumes.
Does camera resolution alone determine storage?
No. Resolution affects potential detail, but encoder bitrate is the direct storage input. FPS, scene motion, codec and quality settings also affect the resulting stream.
Should event recording use 25 percent by default?
No. The default is only a starting value. Measure how much of the day your cameras actually record and change the activity percentage to match.
What happens when I add more cameras later?
Aggregate bitrate and retention capacity rise with the new streams. Recalculate storage and confirm that network, controller, bays, power and cooling still have headroom.
Why does the calculator not promise exact usable terabytes?
Formatting, filesystem overhead, product labeling conventions and real bitrate variation all affect usable results. The calculator is for sizing headroom, not a byte-perfect guarantee.
Official references and methodology
Verify the exact Blue Iris and infrastructure behavior
The storage math is direct unit conversion from entered Mbps and recorded time. Product cards reuse accepted Sprint 7A surveillance HDD records read-only when available; Sprint 7B does not duplicate that drive catalogue. Verify actual daily growth on the deployed Blue Iris system.
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, switch power budgets, NIC revisions, UPS battery behavior, enclosure bundles and marketplace conditions can change. Verify the exact model before purchase.