The short definition

An NVR is a purpose-built appliance with a CPU, an Ethernet switch (often PoE+), internal hard drives, and embedded recording software. Cameras connect to the NVR's PoE ports or a separate switch on the same network. The NVR pulls each camera's H.264 or H.265 stream over RTSP or ONVIF and writes it to disk. A monitor and mouse plug into the HDMI output for local review; a web interface or mobile app handles remote access.

Compared to a DVR, the NVR's defining feature is that the cameras are IP-addressable and the wiring is Cat5e, Cat6, or Cat6a Ethernet, not coax. That single change unlocks 4K resolution, audio, two-way talk, smart motion, and PoE-powered cameras with one cable per drop.

NVR vs DVR vs VMS

Three terms get conflated. The differences matter at procurement.

  • NVR. Hardware appliance. IP cameras. Ethernet network. Fixed channel count (4 to 64). Local storage. One site. See the DVR entry for the analog counterpart.
  • DVR. Hardware appliance. Analog cameras. Coax cabling. Fixed channel count. Local storage. Legacy installs.
  • VMS. Software. Runs on servers (on-prem or cloud). Scales to thousands of cameras across many sites. Role-based access, federation, integrations. See the VMS entry.

Channel counts and storage math

NVR sizing is two numbers: how many cameras and how many days of retention. Channel counts are fixed at purchase, so over-buying by a few channels is normal. Storage is upgradeable on most enterprise NVRs (drive bays, sometimes external eSATA).

Bitrate per camera at common settings, using H.265:

  • 1080p, 15fps. About 2 Mbps. 22GB per camera per day, 660GB per month.
  • 4MP, 15fps. About 4 Mbps. 43GB per day, 1.3TB per month.
  • 4K (8MP), 30fps. About 12 Mbps. 130GB per day, 3.9TB per month.

Multiply by camera count and retention days. Add 15 to 20 percent overhead for filesystem and indexing. H.264 roughly doubles those numbers. Motion-only recording typically halves them but is unreliable for forensic review without good motion-detection tuning.

PoE-built-in vs separate switch

Two install patterns, each with tradeoffs.

  • NVR with built-in PoE. 8, 16, or 32 PoE+ ports on the recorder itself. Cameras land directly on the NVR. Simpler install, smaller bill of materials, isolated camera network by default. Constraint: per-port power and total PoE budget. PTZ and multi-sensor cameras often exceed what the NVR's switch can deliver.
  • NVR plus external PoE switch. Camera traffic and power come from a dedicated 24- or 48-port PoE++ switch in the IDF. NVR has only data ports. More wiring, more flexibility, easier to scale. Required for cameras above 30W or for installs where the switch budget needs to flex.

For the underlying power math, see the PoE entry.

When an NVR is the right call

Three patterns where we spec an NVR over a VMS:

  • Single-site small-to-mid commercial. One building, 8 to 32 cameras, no remote access requirements beyond a manager's phone app. NVR-plus-monitor is cheaper, faster to deploy, and easier for a non-IT operator.
  • Edge recording at branch sites under a cloud VMS. A multi-site fleet on Eagle Eye Networks or Verkada uses an NVR-class device at each branch as the recording target, while the cloud VMS handles user management and federation. Same hardware role, different software architecture.
  • Standalone retention island. A site that wants 30-day retention without depending on cloud upload. NVR records local. The VMS pulls clips on demand if a search hits.

When to ask Tec-Tel about NVR vs VMS

The line between "NVR is enough" and "VMS is required" is fuzzy on a 30-to-100-camera install. We've helped buyers avoid both directions of overspend. We'll cover the camera count, retention math, and whether your team needs federation or just a recorder.