Target working capacity
16.77 TBincludes overhead + free-space reserveConnected worksheet
NVR System Planner
A recorder plan can fail even when the drive estimate looks right. This worksheet keeps camera channels, recording throughput, working storage, and PoE power in one calculation so a constraint is less likely to disappear between vendor tabs.
Runs in your browserNo sign-upFormula shown below
01
Camera inventory
Group cameras that share the same average bitrate and maximum power draw.
| Group | Count | Average bitrate | Max power each | Remove |
|---|---|---|---|---|
| cams | Mb/s | W | ||
| cams | Mb/s | W |
02
Planning constraints
Make reserve and headroom deliberate rather than burying them inside the result.
03
Constraint check
A purchase shortlist should satisfy all four checks, not only storage.
Recording network
40.0 Mb/scamera main streams to recorderPlanned PoE load
110.0 W40.0 W switch marginRecorder channels
12 / 164 channels spareRaw video data12.96 TB
After recording overhead14.26 TB
Camera nameplate power88.0 W
Next, choose a supported drive layout that provides at least the target working capacity. Verify recorder inbound-bandwidth limits, switch PoE class/per-port limits, and the camera maker’s real bitrate range.
How it works
The formula, without the black box.
One camera inventory → storage + network + power + channel checks
Each group contributes count × average bitrate to recording traffic and count × maximum watts to PoE load. Retention converts traffic into video volume. Overhead, free-space reserve, and PoE headroom remain separate and visible.
Inputs that deserve a second look
- Average bitrate
- Use a measured average or a value from the exact camera/encoder profile—not resolution alone.
- Maximum power
- Use maximum draw with IR, heater, illuminator, or accessories active.
- Activity and schedule
- These reduce recorded seconds only when the system actually records by event or schedule.
- Reserve
- Space intentionally kept free; distinct from filesystem/container overhead.
Common planning mistakes
- Treating a codec or resolution label as an exact bitrate.
- Using switch wattage without checking the separate per-port limit.
- Buying exactly the calculated video volume and leaving no working reserve.
- Counting recorder channels but ignoring the recorder’s incoming bitrate limit.
Questions installers ask
Does the planner recommend a recorder model?
No. It gives constraints you can compare with a recorder datasheet: channels, incoming bandwidth, storage layout, and PoE needs.
Does anything get uploaded?
No project input is sent to Camera Ledger. The plan is calculated and saved locally in this browser.
Is the result a guarantee?
No. It is a planning estimate. Final retention and image usability depend on real encoder behavior, scene conditions, firmware, storage implementation, and device limits.
Sources and boundaries
These links support the method or terminology. They do not turn a planning estimate into a site guarantee.
ONVIF Profile T overview ↗
Explains why H.265 support affects bandwidth and storage planning.
Seagate video storage calculator ↗
A useful vendor reference for surveillance-storage variables and multi-group planning.