NVR vs. DVR: Which Recorder Your Camera System Needs
Affiliate Disclosure: This article contains affiliate links. If you buy through these links, we may earn a commission at no extra cost to you. Our editorial opinions are our own and are not influenced by affiliate relationships. Read our full disclosure policy →
Contents
Quick Answer
An NVR records IP cameras that encode the video inside the camera and send it over an Ethernet cable. A DVR records analog or HD-over-coax cameras that send a raw signal down coax and let the recorder do the encoding. Every argument people have about these two recorders is downstream of that single fact: one cable versus two, Power over Ethernet versus a separate power run, a 328-foot Ethernet limit versus coax runs several times longer, frame-rate ceilings at 4K, and whether audio arrives at all. If you are wiring from scratch, buy an NVR. If coax is already home-run to every camera position, a DVR – or its hybrid successor, the XVR – is a legitimate answer rather than a consolation prize.
The One Difference Everything Else Comes From
Almost every comparison of these two recorders opens with a feature list, which is exactly backwards. There is one architectural difference, and the feature list is what falls out of it.
Video has to be compressed before it can be stored. Raw video is enormous; a modern camera system writes H.264 or H.265 files, not raw frames. The only real question is which box does the compressing. On an IP system, the camera does it: the camera contains a processor, encodes the video internally, and sends the recorder a finished digital stream. On an analog system, the camera does not do it: the camera sends a raw video signal down the cable, and the DVR converts that signal into digital video before writing it to the drive.
That is the whole distinction. An NVR is a network video recorder that stores and manages streams which arrived already digitized. A DVR is a digital video recorder that has to digitize first. Once you hold that in your head, the rest of the comparison stops being a list of trivia and starts being a chain of consequences.
The first consequence is where the intelligence lives. A camera with a processor good enough to encode video can also analyze that video before it leaves the camera – which is why person and vehicle detection is normal on IP cameras and rare on coax ones, while a DVR receives raw footage and does any analysis afterward. The rest of the consequences are cabling, power and distance, and we take them in that order.
The encoder location is the root difference. Cabling, power delivery, distance limits and audio support are all consequences of it.How to Tell Which One You Are Looking At
If you have inherited a system – a house bought with cameras already on it, or a small business with a dusty box in a closet – you can identify it in under a minute without powering anything on. Do not go by the label on the front. Manufacturers have used “DVR” as a generic word for “recorder” for years, and plenty of NVR boxes carry it in the marketing copy.
Look at the back panel instead. A DVR has a row of round screw-on BNC connectors, one per camera channel, for coaxial cable. An NVR has a row of rectangular RJ45 Ethernet ports, which on most models are also the PoE ports that power the cameras. That is a physical difference you can see from across the room.
Identifying an Existing System in Four Looks
1
Check the back panel
Round BNC screw connectors, one per channel, means DVR. Rectangular RJ45 ports means NVR.
2
Check the camera end
A thick cable ending in a screw-on BNC plug plus a separate barrel power plug is analog. A single thin cable with an RJ45 clip is IP.
3
Count the ports
An NVR with PoE has one RJ45 port per camera plus a separate LAN port for the router. An NVR without PoE has only the LAN port and expects a switch.
4
Read the model page
If the spec sheet says XVR, hybrid or pentabrid, it accepts coax and IP cameras on the same recorder.
None of this needs the system powered on, and none of it depends on what the front bezel says.
One more tell: if the camera cable is a fat cable with a thin power pair bonded alongside it in the same jacket, that is siamese cable, and siamese cable means coax. Nobody runs it to an IP camera, because the point of Power over Ethernet is that the second pair is unnecessary.
What the Cable Decides
This is the section that decides most real installations, and it matters far more than any spec-sheet resolution number.
On the IP side, a single Ethernet cable with an RJ45 connector carries video, audio, data, PTZ control and the camera’s power all at once. Power over Ethernet is what makes that possible, and it is a real IEEE standard rather than a vendor feature: 802.3af delivers up to 15.4 watts at the switch and 12.95 watts at the device, 802.3at (PoE+) raises that to 30 and 25.5 watts, and 802.3bt goes to 60 or 90 watts. For cameras that matters more than it sounds. A fixed indoor camera with no infrared illuminator draws roughly 5 to 8 watts and runs happily on plain PoE, while a camera with infrared, a motorized lens or onboard analytics generally needs PoE+. Undersizing the switch is a common way to end up with cameras that boot, then drop out at night when the infrared array fires.
On the coax side, the video cable carries video and nothing else. Every analog camera needs a separate power connection, which is why installers run siamese cable – a coaxial video line with a power pair bonded alongside it – back to a centralized power supply near the recorder, with each camera home-run all the way to the DVR. Two connections per camera instead of one is not a catastrophe, but across eight cameras it is eight extra terminations.
The Cable Numbers That Actually Constrain a Build
328 ft
Maximum length of a single Ethernet run to a camera, or 100 meters
15.4W
Power at the switch under plain PoE; PoE+ raises it to 30W
1,000 ft
Distances some coax systems reach, depending on camera and power delivery
2 vs 1
Cables per camera – coax plus power, against a single PoE Ethernet run
Sources: CCTV Camera World DVR vs NVR guide; TP-Link Power over Ethernet standards.
Distance is where the two technologies genuinely trade places, and it is the one advantage coax still holds outright. A single Ethernet run tops out at about 328 feet, or 100 meters, before you need a PoE extender, an intermediate switch or a fiber uplink. Coax has no equivalent hard ceiling: runs of several hundred feet are routine and some systems reach beyond 1,000 feet, depending on the camera and how power is delivered. There is a real honest caveat here, though – published coax distance figures vary enormously by vendor. Reolink, an IP-first brand, puts the practical maximum at roughly 300 feet, while a distributor selling both formats describes runs into four figures. Both can be true, because the answer depends on cable grade, resolution and voltage drop on the power pair. Treat any single number as a starting point for your own testing, not a guarantee.
Ethernet does have partial answers to distance. Some managed switches include an extended mode that stretches PoE to about 250 meters, or 820 feet, at the cost of dropping port speed to 10 Mbps – fine for one or two cameras, not for a 4K bank of them. Planning your runs before you buy anything is the single highest-value hour in this project; our room-by-room camera placement walkthrough is the right place to work out where the cameras go before you measure how far the cable has to travel. If you have already settled on the network path, our guide to PoE security cameras covers which cameras fit which PoE budget.
| DVR system | NVR system |
|---|
| Camera type | Analog or HD-over-coax | IP network cameras |
| Where video is encoded | Inside the recorder | Inside the camera |
| Cable to the camera | RG59 coax, usually siamese | Cat5e or Cat6 Ethernet |
| Connector | BNC | RJ45 |
| Power delivery | Separate power run per camera | Power over Ethernet on the same cable |
| Single-run distance limit | Hundreds of feet, sometimes 1,000+ | 328 ft / 100 m |
| On-camera analytics | Analysis happens at the recorder | Common – the camera already has a processor |
| Best fit | Buildings with coax already installed | New installations |
Resolution, Frame Rate and the 4K Ceiling
The old version of this comparison was simple: analog meant standard definition and IP meant megapixels. That has not been true for years, and repeating it would be lazy. HD-over-coax cameras reach high resolutions now, and 4K coax systems exist and sell.
The ceiling moved rather than disappeared. Two things are still genuinely different. First, the range: IP cameras span roughly 2MP to 12MP and beyond, a spread analog simply does not cover. Second – and this is the number most buyers never see – motion. A distributor that sells both formats reports that 4K coax cameras top out at around 7 frames per second, while 4K PoE cameras reach 30. Both produce a 4K image. Only one produces 4K video that looks like video rather than a slideshow, and a person walking briskly across a driveway is exactly the subject that falls apart at 7 frames per second.
There is a cost consequence too. 4K DVR systems do exist, but pushing that resolution through a recorder that also has to encode every stream requires more expensive video processing silicon – which erodes the cost advantage that was the reason to pick a DVR in the first place. If 4K is a firm requirement, it pulls hard toward the network side. Our guide to 4K security cameras goes into what that resolution actually buys you at realistic distances, which is a separate question from whether your recorder can accept it.
Audio: Where Our Two Sources Disagree
Most comparisons state flatly that DVR systems cannot record audio. We read two sources that contradict each other on this, and rather than pick the one that makes for a tidier article, here is the disagreement.
Reolink’s position is the traditional one: the analog video signal does not carry voice, so recording sound means adding an RCA audio connection to the DVR, which is extra hardware and extra installation. A distributor that sells both formats says that is outdated – many modern HD-over-coax cameras and recorders do send audio over the same BNC video connection, but with an important string attached: audio support tends to be tied to the signal platform, so a camera defaulting to CVI works best with a CVI-compatible recorder and a TVI camera with a TVI recorder, meaning audio is not reliably universal across mixed-format systems even when the video works fine. The same source notes that dedicated RCA audio inputs have become harder to find on modern DVRs as a result.
Both accounts are defensible, and the practical takeaway sits between them. On an IP system, audio rides inside the same stream the camera already produces – no extra cable, no extra input, no format matching. On a coax system, audio is achievable but conditional: it depends on the camera and recorder speaking the same analog signal format, and it is the first thing to verify rather than assume when you are mixing brands or generations. If audio matters to you at all, note that recording it carries legal weight that video alone does not – our guide to what security cameras can legally record covers the consent rules that apply before you switch a microphone on.
If Your Walls Already Have Coax in Them
This is the situation the internet consensus handles badly. The stock advice is “just get an NVR, IP is better,” which is easy to say when you are not the one pulling cable through a finished ceiling. If your building already has coax home-run to each camera position, staying on coax is a real, defensible choice, and it is the main reason DVRs still sell.
Existing coax can usually be reused directly to upgrade to HD-over-coax cameras without rewiring anything. The labor – the genuinely expensive part of any camera install – drops close to zero, and you replace only the cameras and the recorder. In a commercial building with a drop ceiling and a decades-old analog system, that difference can be the entire project budget, which is why business camera systems and older commercial sites skew toward coax far more than new homes do.
Coax Already in the Walls: Two Honest Routes
🔌 Stay on coax (DVR or XVR)
- Reuse the existing cable outright and upgrade only the cameras and recorder
- No rewiring, no ceiling work, no fishing cable through finished walls
- Keeps very long existing runs that would exceed a 328 ft Ethernet limit
- Accepts that per-camera 4K frame rate is capped well below the IP equivalent
🔁 Convert the coax to Ethernet
- Ethernet-over-coax converters send IP data and PoE power down existing RG59, RG6 or RG11
- Compatible with 802.3af and 802.3at, so standard PoE cameras work
- Roughly 100 Mbps out to about 1,000 ft, extending to about 3,000 ft as bandwidth drops to 10 Mbps
- Costs a converter pair per camera and adds two more devices per run that can fail
That second column deserves more attention than it gets, because most guides never mention it. Ethernet-over-coax converters – sometimes sold as EoC or PoE-over-coax – let you run genuine IP cameras on the coax already in the building. One manufacturer’s documentation describes carrying both PoE power and Ethernet data over existing coaxial cable, compatible with RG59, RG6 and RG11, supporting the 802.3af and 802.3at standards, at up to 100 Mbps over roughly 1,000 feet of coax and out to about 3,000 feet with bandwidth falling to 10 Mbps. Power budget falls off with distance too: that documentation quotes around 21 watts of PoE load at 330 feet, dropping to about 11 watts at 1,000 feet.
The honest limitations matter as much as the capability. These converters work point to point, so each camera needs its own pair of units, and the manufacturer itself recommends a dedicated EoC switch kit rather than loose converters when several coax runs share one system, to avoid signal interference – a caveat published by the company selling the product, not a reviewer’s guess. For one awkward run – a detached garage, an elevator shaft, a long driveway – a converter pair is elegant. For sixteen cameras it is sixteen extra failure points, and pulling new Ethernet starts looking better.
What Both Recorders Do Identically
Several things people treat as differentiators are not differences at all, and knowing which ones saves you from being sold a feature both boxes already have.
Neither one needs the internet to record. Both are standalone local recording systems: cameras wire directly to the recorder, footage is written to a drive in the box, and no cloud account is involved. Both connect to a monitor over HDMI or VGA, are driven with a mouse, and export clips straight to a flash drive. Internet is only needed to watch the cameras from outside the building, which either recorder does by plugging its LAN port into your router. That is a genuine privacy and reliability argument for a wired recorder over cloud cameras, and the same reasoning behind our guide to cameras that work without wifi. It also means no monthly fee, unlike cloud-recording subscriptions on consumer camera brands.
Both need a hard drive built for the job. This is the most commonly skipped step, and the most expensive to skip. Western Digital states its Purple line is designed for 24×7 video surveillance recording and engineered to withstand the elevated heat fluctuations and equipment vibration inside recorder enclosures, whereas an average desktop drive is built to run only for short periods. A spare desktop drive in a recorder works right up until it does not, usually at the exact moment you need the footage.
Both make you choose a retention window. Drive capacity, camera count, resolution and frame rate together decide how many days of footage you keep before the recorder overwrites the oldest. Our guide to how long security cameras keep footage covers the arithmetic; if you are still deciding between a recorder, a card in the camera and a cloud plan in the first place, where your footage should live is the decision to make before you shop for either box. For a one-camera setup, a memory card in the camera may make the whole recorder question moot.
XVR: The Hybrid That Makes the Naming Worse
The clean two-way split above is muddied by a third category most shopping pages fail to explain. Many recorders sold today as DVRs are actually XVRs, and an XVR records coax and IP cameras on the same box – the IP cameras joining through a network switch rather than the coax inputs.
The format support goes further than that. Some of these recorders are described as pentabrid, meaning they accept several different analog signal types – CVI, TVI, AHD and the older CVBS – on the same BNC inputs. That matters when you inherit a mixed system, or replace two failed cameras out of eight and cannot find the original brand. A traditional analog DVR cannot record IP cameras at all, so the distinction between an old DVR and a current XVR is worth checking on the spec sheet rather than assuming.
Practically, the XVR is the gradual-upgrade path. You keep the coax cameras that still work, add IP cameras where you actually need the resolution – the driveway, the front door – and retire the analog ones as they fail. Our wired camera system guide covers complete kits on both sides of that line, and the driveway camera guide covers the position where people usually want the extra pixels first.
Where Each One Genuinely Wins
Stripped of brand marketing, the decision comes down to a handful of situations, each with a clear answer.
| Your situation | The recorder that fits | Why |
|---|
| New build, nothing in the walls yet | NVR | Ethernet is thinner, more flexible and often more cost-effective than siamese cable, and one run does both power and data |
| Existing coax to every camera position | DVR or XVR | The cable is the expensive part, and it can be reused as is |
| One camera run beyond 328 ft | DVR, XVR, or an Ethernet-over-coax pair | That distance is past a single Ethernet run’s limit without extra hardware |
| 4K matters, and so does smooth motion | NVR | 4K coax runs near 7 fps against 30 fps on 4K PoE |
| Person and vehicle detection matter | NVR | The analysis happens on an IP camera’s own processor |
| Replacing two failed cameras on an old system | XVR | Pentabrid inputs accept CVI, TVI, AHD and CVBS on the same recorder |
| You will not run any cable at all | Neither – or a wifi NVR | Wifi NVRs exist and pair with wireless cameras, but the cameras still need mains power |
That last row deserves a caution. A wifi NVR removes the cable between camera and recorder but not the camera’s power cable, and it inherits every weakness of a wireless link: interference, bandwidth limits and signal loss, which is why professional installs stay wired. If you are seriously considering that route, test the wifi at the actual mounting spot before you buy anything, because a camera that shows three bars from a phone in your hand may not hold a 4K stream from a soffit.
Final Recommendation
Before you compare a single spec sheet, go look at what is physically in your building. Pull the cover off one camera position, or check the closet where an old recorder used to sit. Whether there is coax already run to the places you want cameras is the fact that decides this, and it takes ten minutes to establish.
If there is nothing there, buy an NVR. That is the default and it is not close: one Ethernet cable per camera carrying video, audio, data and power, on-camera analytics, full 4K at full frame rate, and a system that expands by adding a switch rather than re-pulling cable. Size the PoE switch or recorder for PoE+ rather than plain PoE if any of your cameras have infrared, a motorized lens or onboard detection, and put a surveillance-rated drive in it from day one.
If there is coax already home-run to your camera positions, buy an XVR rather than a plain DVR. You reuse the cable, you keep any run longer than a single Ethernet segment allows, and the hybrid inputs leave you a path to add IP cameras later without replacing the recorder again. Three things would change that answer: needing 4K at full frame rate, needing on-camera person and vehicle detection, or finding that the existing coax is damaged or does not reach where you now want cameras. In that last case, price an Ethernet-over-coax converter pair for the one awkward run before you write off the whole cable plant, because it is often just one run causing the problem.
SafeBode does not yet run an in-house product testing program. This guide is built from manufacturer specifications, official support documentation, current retail listings and verified buyer feedback rather than hands-on testing, and we say so plainly rather than implying testing we have not done.
Frequently Asked Questions
Is an NVR always better than a DVR?
No. An NVR is the better choice for a new installation, and by a wide margin. A DVR or XVR is the better choice when coaxial cable is already installed, because reusing existing cable avoids the most expensive part of the job. Neither is a downgrade in the abstract – they suit different buildings.
Can I connect analog cameras to an NVR?
Not directly. An NVR expects a digital stream over a network connection, and an analog camera does not produce one. You would need an encoder that converts the analog signal to a network stream first, which is a real product category but rarely worth it for a small system. A hybrid XVR is the simpler route if you need both types on one recorder.
Can I connect IP cameras to a DVR?
A traditional analog DVR cannot record IP cameras. Modern XVR recorders can, with the IP cameras joining through a network switch rather than the coax inputs. Check the spec sheet before assuming a recorder labeled DVR is actually an XVR.
Do I need internet for an NVR or DVR to record?
No. Both record locally to a hard drive inside the recorder, with the cameras wired directly to the box. Internet is only needed to view the cameras remotely, which you enable by connecting the recorder’s LAN port to your router.
What hard drive should go in a recorder?
A surveillance-rated drive, not a spare desktop drive. Surveillance drives are specified for continuous writing and for the heat and vibration inside a recorder enclosure, whereas typical desktop drives are built for intermittent use. Recorders are usually sold either with a drive fitted or with an empty bay and a stated maximum capacity.
Can I reuse the coax cable already in my house for IP cameras?
Often yes, using Ethernet-over-coax converter pairs, which send network data and PoE power down existing coaxial cable. They work point to point, so each camera needs its own pair, and manufacturers recommend a dedicated switch kit rather than loose converters when several runs share a system. It is an excellent fix for one or two awkward runs and gets clumsy across a large install.
What is the difference between an NVR and a PoE switch?
A PoE switch only distributes power and network connectivity – it stores nothing. An NVR records and manages the video. Many NVRs have a PoE switch built into their camera ports, which is why one box can be the recorder and the power source at once. Non-PoE NVRs exist and expect you to supply a separate switch.
How many cameras can one recorder handle?
Recorders are sold by channel count – commonly 4, 8, 16 or 32 – and that count is a hard ceiling for the box. Pick one above your current camera number if you expect to expand, since moving to a larger recorder later means rebuilding the system rather than adding a camera.
Does a longer coax run reduce image quality?
It can. Degradation over distance depends on cable grade, the resolution being carried and how power is delivered, which is why published maximum distances vary so widely between vendors. Higher resolutions tolerate a long or poor-quality run far less well than standard-definition analog did, so cable that was fine for an older system is not automatically fine for an HD-over-coax upgrade.
Sources
Show sources (5)
