A blank monitor doesn't always mean a broken camera. "Offline" and "no video" are two separate faults with different causes, and mixing them up is the fastest way to waste an afternoon swapping cables that were never the problem.
An offline status points to a lost connection between camera and recorder. A no-video image means the connection is fine but the image itself isn't showing.
Work out which fault you've got first, then trace it back through power, network and signal, in that order. Checking in this sequence is usually the quickest route to a fix.
Why is my CCTV camera showing no video or offline?
Offline means the recorder has lost contact with the camera; no video means it can see the camera but the picture won't decode. These are two different faults, and treating them as the same thing wastes time.
Offline points to a power or network-layer problem — the device simply isn't answering. No video points to a signal, cabling or configuration-layer problem further downstream. Work out which one you have first, because the fix paths barely overlap.
An offline camera on an NVR typically shows a broken-link icon or a "camera offline" status rather than a picture at all. That tells you the recorder can't reach the device, which points you at PoE power, the switch port, or the cable run.
A "no video" fault usually shows as a black or grey screen with the camera still listed as connected. That points instead at the video stream, a resolution mismatch, or — on analogue systems — a degraded coax connection.
One camera down vs. the whole screen going black
A single dead camera and a fully black multiview point to entirely different fault layers, so diagnosing them the same way wastes time.
- One camera offline, others fine — almost always local to that camera: its PoE port, its cable run, its power injector, or the camera itself.
- Whole screen black or all channels offline — points to the recorder, the main switch, or a shared power supply, since it's affecting every channel at once.
Always check whether it's one camera or all of them before touching any cabling. That single check rules out half the possible causes immediately and stops you swapping cable when the fault is actually the NVR's PSU or a shared PoE switch.
Step 1: Is it a power fault? (PSU, PoE budget, injectors)
No LED and no infrared glow at the camera itself means the fault is in the power layer, not the network — don't waste time on IP addresses yet. Every PoE and analogue camera shows some sign of life when powered: a status LED, or IR LEDs glowing faintly in low light. If there's genuinely nothing, trace back to the injector, switch port, or DC PSU before touching any network settings.
PoE budget, not just a dead port
A camera that drops offline intermittently, rather than staying dead, often points to the switch's total PoE power budget being exceeded rather than a fault on that one camera. This gets missed because it's easy to add a ninth or tenth camera to a switch without re-checking its rated PoE wattage total. The symptom can look exactly like a random, unexplained dropout on whichever camera draws power last in the polling order.
Analogue and HD-TVI on a separate DC PSU
For analogue, HD-TVI or AHD cameras — including 5MP TVI cameras — running off a separate DC PSU, check the output voltage under load, not just at idle. Our 12V 5A 60W PSU's product specification notes that camera instability, video signal interference and unexpected shutdown are typical symptoms of voltage fluctuation under load, not necessarily total PSU failure. A multimeter reading at idle can look fine while the same PSU sags once several cameras are drawing current simultaneously on a shared run.
A camera that reboots or drops every few days, not permanently, is often a power-under-load symptom rather than a dead unit. Check the PoE budget and PSU voltage under real load before assuming the camera itself has failed.
Step 2: Is it the cable or connector? (signal loss vs no signal)
Whether this is a cabling fault depends on which type of camera you're running: analogue systems fail differently to IP ones, and testing them the same way wastes time. On an analogue HD-TVI/AHD/CVI run, "no signal" on the DVR is almost always a physical-layer fault — the cable, a connector or a balun. On an IP camera, "offline" in the NVR or app points to a network-layer problem instead — routing, PoE negotiation or DHCP — so don't cable-test an IP camera as if it were coax.
Analogue: chase the balun and the crimp first
Where HD-TVI, AHD or CVI cameras run over Cat5e/Cat6 rather than coax, a passive video balun does the BNC-to-RJ45 conversion — and it's a common failure point. A passive unit such as the 4CH Passive Video Balun BNC to RJ45 (SKU: BALUN-4CH-1080P-RJ45) has no active electronics, so a poor crimp, a reversed pair or a loose screw terminal can show up as "no signal" even with a perfectly healthy camera.
Reseat the connections and re-crimp the RJ45 ends at both the camera and DVR side before assuming the camera itself has failed. This takes a few minutes and rules out the cheapest, most common cause first.
Water ingress: the fault that only shows up in rain
A camera that drops signal only in wet weather usually points to moisture at an external gel connector or junction box, not a settings problem. Check every outdoor joint for condensation or corrosion inside the connector shell — this is a cabling fault, not something a menu reset will fix.
It's also worth checking DC barrel connections feeding the camera.
Step 3: Is it a network fault? (IP conflict, switch port, PoE negotiation)
A network fault is confirmed if the camera won't reply to a ping, or replies but still shows no image on the NVR or web browser — these are two different failure layers, not one. Isolating which layer has failed determines whether the fix is a five-minute cable swap or a network reconfiguration.
Start with a ping test from a laptop on the same subnet as the camera. If it replies but the web interface or NVR feed still won't load, the network path is up but the video service inside the camera has stalled.
As one installer's troubleshooting thread on IPVM points out, ping and video streaming are handled by separate processes on the camera. A clean ping response doesn't clear the network layer of suspicion, and it certainly doesn't confirm the video pipeline is working.
Next, rule out an IP address conflict, where two devices on the same network have been given the same address. Recorders such as the Dahua EZ-IP XVR1B16-I (SKU: XVR1B16H) log this as a named event — MAC conflict — in their alarm system, alongside video loss, video tampering and camera-offline triggers, per the unit's own datasheet (XVR1B16H-I_datasheet_20241113.pdf).
A conflict typically causes intermittent drops rather than a permanent offline state, because whichever device answers first on the network "wins" that moment. This is one reason we'd suggest fixed IP allocation or DHCP reservations on any system running more than a handful of cameras.
If ping and addressing check out, move the camera to a different switch port. If you're running a PoE injector rather than a PoE switch, swap that too.
A failing port or a PoE negotiation fault — the switch and camera failing to agree on power class — can present identically to a dead camera even though the hardware is fine.
Step 4: Is it an NVR/DVR configuration fault? (channel setup, licence, resolution)
A "no video" channel is often a configuration mismatch inside the recorder, not a broken camera or cable. This shows up most on multi-format ("penta-brid" or hybrid) DVRs that support several signal types on the same board, such as the Dahua EZ-IP XVR1B16-I 16-channel 4MP hybrid DVR (SKU: XVR1B16H), which handles TVI, AHD, CVI, CVBS and IP inputs across its channels.
Check the channel's assigned input type before touching anything else.
Channel type and resolution mismatches
If a channel is still set for CVBS or a lower resolution while you've connected a 5MP TVI camera, the recorder can display black screen or "no video" even though the cable and camera are both fine. On hybrid boards this is a menu setting per channel, not something the DVR always detects automatically — worth checking first on any 5mp tvi cctv camera install where an older analogue camera has just been swapped out.
Display resolution catching you out after a swap
Just replaced a camera and now the whole output looks wrong? The Annke 5MP 4-Channel Hybrid DVR product specification (SKU: AN-DV4-5MP-DW41JD) notes that VGA output defaults to 1024×768 and needs manual adjustment for higher resolutions — an easy miss that reads as "no video" on the monitor but is purely a display setting, not a fault with the DVR or camera.
Hybrid IP channel and licence reassignment
On hybrid recorders mixing BNC and IP inputs, each IP channel typically draws from a limited pool of IP licences or slots. If that slot has been reassigned to a different camera during a previous change, the channel you're looking at will show no video even though the camera itself is powered and streaming.
Recommended kit
For the setup above, this is the kit we'd fit from our own range:
This article was researched and written by itmaster.uk.
