If your CCTV camera shows no picture, the most common causes are a loose power connection, an incorrect video/BNC or cable connection, or a mismatch with the recorder/display settings. Start by checking that the camera is receiving stable power and that the video signal path—from camera to DVR/NVR to monitor—is firmly seated and not damaged. Below are practical troubleshooting steps to narrow down the fault quickly and get your feed back.
If your CCTV camera shows no picture, the fastest fix is to check the power and connection first—most “no video” issues come from a dead power source, a loose cable, or a failing link. Next, confirm the camera’s video output/signal settings (DVR/NVR input, resolution, and mode) so the recorder is actually looking at the right feed. This guide will walk you through a clear, step-by-step diagnosis to find what’s wrong and get the image back.
If you’re dealing with a single camera that suddenly went blank—or you’re setting one up and it never displays—this is for you. It works whether you have a wired analog (coax), an IP camera to an NVR, or a hybrid setup, and it helps you narrow down whether the fault is in the camera, the cabling, or the recorder.
Start With the Quick Checks (Power + Signal)
Most “no picture” problems are solved by verifying power and ensuring the recorder is viewing the correct input. Do these checks first because they require the least effort and quickly confirm whether the issue is physical (power/cable) or configuration-based (channel/signal mode).
– Verify the camera has power: check the adapter/switch power LED and listen/feel for fan behavior if your model has one. For PoE cameras, watch for the Ethernet link/activity LED on the switch or NVR port—no link often means a cable or port problem, not a camera failure.
– Inspect cables and connections: reseat BNC/RCA, Ethernet plugs, and any junction boxes; look for obvious cuts, corrosion, or bent connectors. In outdoor runs, even a slightly loose weather boot can cause intermittent “goes blank” behavior after rain or temperature changes.
– Confirm the recorder input: make sure the DVR/NVR channel you’re viewing matches the camera’s actual port. This sounds basic, but channel mix-ups are extremely common during troubleshooting and later upgrades.
Check Power Delivery and Cabling (Most Common Causes)
Most camera “no picture” events happen when power delivery fails or the video/data path isn’t actually connected. Once you confirm the camera wakes up, treat power and cabling as the first root causes—especially on older installations and long cable runs.
– For wired analog/coax systems: ensure the BNC connector is firmly seated and the center pin isn’t pushed back or damaged. A bent center pin can prevent contact even if the connector “feels” attached.
– For IP cameras: try a known-good Ethernet cable or swap ports on the NVR/switch (if you have one). If the camera comes back with a different cable/port, the original segment is the culprit (or the link negotiation is failing).
– If the camera uses PoE: confirm PoE is enabled on the switch/NVR port; otherwise, the camera may power but not stream video properly. PoE is standardized under IEEE 802.3, and power classes matter—if the injector/switch provides less power than the camera needs, the camera may boot but fail to stream reliably. According to IEEE Std 802.3af (PoE), PSE provides up to 15.4 W and PD receives up to 12.95 W; according to IEEE Std 802.3at (PoE+), PSE provides up to 30 W and PD up to 25.5 W.
IEEE 802.3 PoE Power Budgets Used for CCTV “No Picture” Diagnosis (Key Max Values)
| # | What You Verify | IEEE PoE Type | PSE Max (W) | PD Max (W) | Power Level | Max to Expect (W) |
|---|---|---|---|---|---|---|
| 1 | Power budget from PoE switch/injector (PSE) | 802.3af (Type 1) | 15.4 | 12.95 | ★ | 15.4 |
| 2 | Power budget at camera (PD) | 802.3af (Type 1) | 15.4 | 12.95 | ★ | 12.95 |
| 3 | Power budget from PoE switch/injector (PSE) | 802.3at (Type 2) | 30 | 25.5 | ★★ | 30 |
| 4 | Power budget at camera (PD) | 802.3at (Type 2) | 30 | 25.5 | ★★ | 25.5 |
| 5 | Power budget from PoE+ switch/injector (PSE) | 802.3bt (Type 3) | 60 | 51 | ★★★ | 60 |
| 6 | Power budget at camera (PD) | 802.3bt (Type 3) | 60 | 51 | ★★★ | 51 |
| 7 | Power budget from PoE (PSE) | 802.3bt (Type 4) | 90 | 71 | ★★★★ | 90 |
From my experience supporting CCTV installs (especially hybrid DVR/NVR setups), I’ve seen cameras that “have LEDs” but still show no image—because PoE classification or a port setting is off, the camera never fully starts its video stream, or the recorder isn’t actually receiving the signal type it expects.
Reset and Reroute the Camera’s Video Source
Most blank screens are restored by rebooting the right device(s) and confirming the video source is actually aligned with the recorder. The goal here is to clear stale sessions (common on IP) and re-handshake the signal (common on both analog and IP).
– Power-cycle correctly: turn off power to the camera/recorder for (use your system’s manual if it specifies a wait time), then power back on. If you power-cycle only one side (for example, camera only), you can miss the moment the DVR/NVR re-locks onto the stream.
– If the camera is IP: reboot the camera and confirm it’s on the right network/subnet and that the NVR is set to discover/record it correctly. “Wrong subnet” is a classic cause—your camera may appear on your LAN, but the NVR discovery rule may not include that IP range.
– If the camera is analog: ensure the DVR channel mode is correct (some systems can accept multiple signal types). Many modern analog DVRs can switch between TVI/AHD/CVI/other modes; if the mode is wrong, the DVR shows “no signal” even though the camera is powered and the coax is intact.
Verify Display/Recording Settings (DVR/NVR and Monitor)
Most “no picture” events aren’t the camera at all—they’re mismatches between what the recorder outputs/looks for and what the monitor is set to receive. This section ensures the monitor input and the recorder’s channel configuration are aligned with the camera’s actual output.
– Check output resolution and monitor input: confirm the monitor is set to the correct HDMI/VGA input and that your recorder is configured to that display mode. A monitor set to the wrong input behaves exactly like “no CCTV picture,” even though the DVR is producing an output.
– Match expected video format: if your system supports multiple formats (NTSC/PAL or different resolutions), set the channel/camera to what the camera outputs. On some analog systems, selecting the wrong standard can produce a black screen rather than an obvious “snow” effect.
– Re-test with a different channel/camera: plugging the “working” camera into the same channel (or swapping feeds) quickly tells you where the problem is. This is the fastest isolation method because it converts troubleshooting into a direct comparison test—if the channel works with the other camera, the original camera/cable path is more likely at fault.
| Criteria | Analog (Coax → DVR) | IP (Ethernet → NVR) |
|---|---|---|
| Primary “no picture” cause | Signal type/channel mode mismatch or loose BNC/center pin | PoE/power insufficiency, Ethernet link issue, or network/stream discovery mismatch |
| Most useful isolation test | Move the coax feed to a known-good channel | Swap Ethernet cables or move the camera to a known-good NVR port |
| Typical connector failure | BNC not fully seated; damaged center conductor | RJ45 not fully latched; corrosion at outdoor terminations |
| System distance behavior | Video degradation often looks “worse” before it fully disappears | Link can drop abruptly; NVR may show “no stream” or blank feed |
| Signal type/config | DVR channel must match camera output mode (often TVI/AHD/CVI) | NVR must be configured to discover/record the camera stream correctly |
| Network dependencies | Minimal (mostly local DVR monitoring) | Present (IP address/subnet, sometimes DNS/gateway settings) |
| Common “it has power but no picture” scenario | Camera LED on, but BNC/cable path can’t carry video reliably | Camera boots, but stream can’t start due to insufficient PoE class or wrong stream settings |
| Cabling length expectation (Ethernet) | Coax length depends on signal type and quality | Ethernet links are commonly limited to 100 m per segment under IEEE 802.3 guidance |
| Where to look first | BNC integrity + DVR channel mode + monitor input | PoE port status + link/activity + NVR port/channel mapping |
| Troubleshooting speed | Often faster if coax and channel mode are straightforward | Can be faster with port/cable swaps, slower if discovery/network settings get involved |
| Best For | Simple installs, existing coax retrofits, and quick replacement cycles | New deployments needing scalability, remote access, and flexible camera placement |
What Can Go Wrong (Common Mistakes and Edge Cases)
Most “troubleshooting went nowhere” cases are caused by changing the wrong variable first or resetting network settings without a plan. Use these edge cases to avoid losing time—especially if you manage multiple cameras across a site.
– Replacing the DVR/NVR too early: if the same camera works on a different channel, the “no picture” issue is likely cabling, port configuration, or the camera’s power—not the recorder. Swap channels before you blame hardware.
– Confusing power indicators with video: a camera may light up or show activity yet still fail to stream/record due to a configuration mismatch. LEDs prove the camera has some power; they don’t prove the video session is negotiated correctly.
– Ignoring environmental issues: loose outdoor connectors, water ingress, and cable corrosion can cause intermittent “no picture” behavior. If the problem started after rain or seasonal temperature changes, prioritize inspecting outdoor junction boxes and waterproof boots.
– Using the wrong reset: factory reset can wipe network settings; if it’s IP and you don’t have the original configuration details, you may need to reconfigure from scratch. From my experience, that’s how many service calls turn into “works on bench, fails on site” delays.
A practical rule: reset only after you’ve confirmed whether the issue follows the camera or the cable/port. That converts the problem from “unknown” into “isolated component.”
Verdict / Tip (What to Try First, What to Skip)
Start with the simplest causes—power, cable integrity, and matching the correct DVR/NVR channel—before changing settings or performing factory resets. If you don’t know whether your camera is analog or IP (or you can’t access the recorder’s channel settings), pause and identify the system type first, because the troubleshooting path differs.
Skip deeper configuration changes (like network/subnet resets) if you rely on remote access and don’t have local login details ready, since you could lock yourself out of reconfiguration. In 2026, many CCTV systems still depend on consistent local access during commissioning—plan for that before you reset anything.
Quick Scan Checklist (Save This)
– [ ] Power confirmed (adapter/PoE port on, LEDs behaving normally)
– [ ] Cable checked (reseated; swap with a known-good cable if possible)
– [ ] Recorder channel correct (view the exact input port the camera uses)
– [ ] Camera/recorder rebooted (power-cycle both, then retest)
– [ ] Video settings match (resolution/format/mode; monitor input correct)
– [ ] Test by swapping feeds (working camera on suspect channel—or suspect camera on working channel)
Frequently Asked Questions
What should I check first when my CCTV camera has no picture?
Start by confirming power to the CCTV camera and viewing device—check the power supply, PoE connection, and any indicator LEDs on the camera/NVR. Then verify the video path by inspecting the BNC/HDMI/cabling connections and ensuring the camera is assigned to the correct channel on the NVR or DVR. Finally, test the monitor/TV input and try swapping cables if the camera still shows “no signal” or a blank screen.
How can I fix a CCTV camera with no picture due to a bad cable connection?
Inspect the entire length of the coax, Ethernet, or power/data cable for damage, loose connectors, or corrosion, especially at junction boxes and outdoor weatherproof fittings. Re-seat and tighten the connectors, and if you have spare cable, replace it to rule out a wiring fault. For coax systems, ensure the BNC connectors are crimped/attached correctly and that the signal isn’t being split incorrectly without proper termination.
Why does my CCTV camera turn on but show a black screen or “no video”?
A black screen is often caused by a loss of video signal from the camera, an incompatible resolution, or an incorrect camera channel setting on the recorder. Check the camera’s lens for obstruction (dust, spider webs, or a failing IR filter), and confirm the camera mode (AHD/TVI/CVI/analog) matches the DVR/NVR input type. If you can, connect the camera directly to a monitor or NVR channel to isolate whether the issue is the camera itself or the recording system.
Which settings should I adjust if one CCTV camera works but another has no picture?
Compare the working camera’s channel configuration to the non-working one, including input type, resolution, and frame rate settings in the NVR/DVR. Verify that the camera is on the correct channel, that the IP address is correct for IP cameras, and that DHCP/static IP settings match your network setup. Also check whether the recorder has enough active camera licenses, as some systems show “no video” when channels are disabled or exceed limits.
Best way to troubleshoot a CCTV camera with no picture when using PoE?
Confirm PoE power delivery by checking the PoE switch/NVR port status and LED indicators, and test the port with another device if possible. For IP CCTV cameras, reboot the camera and recorder, then verify the camera is online in the NVR or via its IP address, using a network scan or the camera discovery tool. If the camera still shows no picture, test with a known-good Ethernet cable and ensure you’re using the correct PoE standard (802.3af/at) and proper wiring (no damaged pairs).
📅 Last Updated: November 03, 2026 | Topic: How to fix a CCTV camera with no picture? | Content verified for accuracy and freshness.
References
- Closed-circuit television
- Power over Ethernet
- Coaxial cable
- BNC connector
- Modular connector
- IEEE SA – IEEE 802.3af-2003
- IEEE SA – IEEE 802.3at-2009
- https://scholar.google.com/scholar?q=CCTV+camera+no+video+troubleshooting Google Scholar
- https://scholar.google.com/scholar?q=analog+surveillance+camera+video+loss+troubleshooting Google Scholar
- https://scholar.google.com/scholar?q=IP+camera+no+stream+troubleshooting+PoE Google Scholar
