Fixing a CCTV camera that’s not working is usually a straightforward process: you check power, verify the connection, and confirm the recorder/display is communicating. This step-by-step guide tells you exactly what to test in order so you can pinpoint the fault fast—before you waste time swapping parts. If you follow the sequence, you’ll know whether the issue is the camera, the wiring, the network, or the system it’s plugged into.
A CCTV camera that “does nothing” is usually failing because of power delivery, a cabling/port mismatch, or (for IP systems) a network/stream settings mismatch—so start there before you reset anything. If your CCTV camera shows signs of life but you still get no video, verify the correct DVR/NVR channel/port, then confirm the IP address/codec/IR (night mode) behavior that can make a live camera appear “dead.”
This guide is for homeowners, small businesses, and anyone troubleshooting a non-responsive CCTV camera—whether it’s a wired analog camera, an IP camera, or a camera connected to an NVR.
Quick checks first (before you open anything)
Start with the basics: confirming power and checking that every cable is fully seated resolves a large majority of “CCTV camera not working” cases. These checks take minutes and help you avoid unnecessary resets that can wipe IP settings on your camera.
A CCTV camera that shows no LEDs, no link lights, or no NVR channel activity often has a power delivery or physical connection problem rather than a failed sensor.
For wired CCTV camera setups, a partially connected BNC/DC lead commonly results in “no video” even when the camera shell feels powered or warm.
For IP CCTV cameras, confirming Wi‑Fi signal strength and client isolation settings is often the difference between “camera online” and “camera unreachable.”
– Confirm the camera has the correct power supply and that any power adapter/PoE switch is delivering power.
– Check the physical connections: cable fully seated, no loose BNC/DC plugs, and no visible damage to wiring.
– If it’s a wireless camera, verify Wi‑Fi signal strength near the camera and that the network hasn’t changed.
Fix the power: the most common cause
Fixing the power issue is the fastest path back to video for a CCTV camera that’s not working. In 2026, power problems still top the list because DC adapters fail quietly, PoE ports go inactive, and damaged Ethernet/coax runs can block power and/or signaling.
IEEE 802.3 Ethernet over twisted-pair is specified for up to 100 m (about 328 ft) between a switch and powered device, so long runs and poor terminations can trigger “no camera” symptoms even when PoE is available.
With PoE (Power over Ethernet), checking the active PoE port on the NVR/switch is often more reliable than swapping cables alone, because the port may be disabled or under-supplying the CCTV camera.
Power method 1: Wired (analog) CCTV cameras with DC adapters
For wired systems, inspect the DC adapter output (if applicable) and test at the source if you can. If you don’t have a multimeter, look for adapter activity (LED or power indicator), and try a known-good adapter with the same voltage rating.
Power method 2: PoE/IP CCTV cameras
For PoE/IP cameras, confirm the PoE port on the switch/NVR is active (swap ports if possible). PoE cameras frequently fail due to:
– the wrong PoE port (some devices separate PoE and non-PoE outlets),
– a port configured for different mode,
– or a cable issue that prevents PoE negotiation.
Use the startup LEDs as a diagnostic signal
If the camera has LEDs, note what they do during startup (no light at all vs. blinking vs. steady). For CCTV camera troubleshooting, LED behavior is often more informative than “it’s on,” because different boot states point to either a power starvation issue or a configuration/network issue.
📋 MANDATORY DATA TABLE (Power standards you can check quickly)
PoE Power Classes & Typical Limits (What to Verify on Your CCTV Camera)
| # | PoE method | PSE max power | PD max power | PD available power margin* |
|---|---|---|---|---|
| 1 | IEEE 802.3af (PoE) | 15.4 W | 12.95 W | +83% |
| 2 | IEEE 802.3at (PoE+) | 30.0 W | 25.5 W | +85% |
| 3 | IEEE 802.3bt Type 3 | 60.0 W | 51.0 W | +85% |
| 4 | IEEE 802.3bt Type 4 | 90.0–100.0 W | 71.0 W | +79%–+85% |
| 5 | Passive PoE (typical) | 24 V (common) | ~(depends) | Not standardized |
| 6 | 12 V DC (common CCTV) | 12 V DC | ~(model-dependent) | Verify adapter rating |
| 7 | 24 V AC (common CCTV) | 24 V AC | ~(model-dependent) | Confirm transformer output |
Margin here is PD max power relative to PSE max power where the value is standardized; passive/non-standard supplies vary by device model. For absolute values, match the spec for your exact CCTV camera model.
Check the connection and video path (analog vs. IP)
Fixing the “no video” symptom depends on whether your CCTV camera is analog or IP. If you route the video correctly but the camera still won’t show up, the problem is usually the stream settings (IP) or the channel/port mapping (NVR/DVR).
Analog CCTV uses a BNC/coax video path where a disconnected coax run or incorrect DVR channel often looks identical to a failed camera.
IP CCTV cameras rely on an IP stream (commonly RTSP) and a compatible codec/resolution, so a reachable camera can still display “no video” if the recorder can’t decode the stream.
Analog (BNC/coax) cameras: confirm the signal path and channel
Analog (BNC/coax) cameras: verify the coax run isn’t disconnected and confirm the NVR/DVR channel input matches where that camera is connected. A classic mistake is moving a camera’s BNC cable to another port but forgetting to switch the channel view in the app.
IP cameras: align IP addressing and confirm the stream opens
IP cameras: make sure the camera’s IP address, subnet, and gateway align with your router/NVR network; then confirm the stream opens in the recorder/app. If the camera works on one device/channel but not another, the issue is often a DVR/NVR port or app integration setting.
Analog vs. IP CCTV cameras: what to check first
| Area | Analog CCTV camera | IP CCTV camera |
|---|---|---|
| Primary failure symptom | “No signal” on a DVR channel | App/NVR can’t open stream or camera “offline” |
| First check | BNC seating + correct DVR channel input | IP reachability + stream URL/codec compatibility |
| Cable relevance | Coax continuity and connector condition | Ethernet/Wi‑Fi link + routing to NVR/router |
From my experience resolving “CCTV camera not working” calls, the fastest wins usually come from confirming the correct channel/port mapping first (for analog) and confirming stream compatibility (for IP).
Reboot, re-pair, and verify camera settings
Rebooting is effective when a CCTV camera is “online but not streaming” due to a stuck session, codec mismatch, or NVR/app integration error. The key is doing the reboot sequence in a sensible order so you don’t lock in stale network settings.
Power-cycling a CCTV camera and then restarting the NVR/router clears many session-state issues where the recorder no longer requests the stream correctly.
Resolution/codec compatibility issues can produce “no video” even when an IP CCTV camera is reachable on the network.
Do a practical reboot sequence
Power-cycle the camera and reboot the NVR/router (in a practical order: camera → NVR/app, or follow your system’s recommended sequence). If your CCTV camera is IP, do not change multiple settings at once—make one change, then observe the camera’s status.
Re-check the settings that create “no image” scenarios
Re-check key settings that affect “no image” scenarios: resolution/codec compatibility, recording mode, and channel assignment. If the CCTV camera is set to a streaming format the NVR can’t decode, you’ll see a “dead camera” effect.
Investigate night/day mode and IR behavior
If night/day mode causes the camera to appear broken, verify IR settings and whether the camera is physically blocked or dirty on the lens/IR window. In 2026, many modern CCTV cameras support IR-cut switching; if the IR window is fogged, scratched, or obstructed, the image can fail specifically at night.
A CCTV camera that works during the day but fails at night often has an IR window blockage, incorrect IR/ICR (IR-cut) mode, or dirty optics that prevent adequate IR illumination.
What can go wrong (common mistakes and edge cases)
Most troubleshooting failures come from assuming “no video” always means a dead CCTV camera. In reality, power, networking, and recorder configuration can each mimic “camera failure,” and some issues don’t clear with a reset.
A damaged coax/Ethernet run, a faulty PoE port, or an incorrect DVR channel mapping can make a CCTV camera look completely non-responsive.
Client isolation on Wi‑Fi (or a changed subnet/IP range after a router swap) can make an IP CCTV camera reachable to you locally but unreachable to your NVR or app.
– Power symptoms that look like “camera failure” can actually be a dead adapter, damaged coax, or a bad PoE port.
– For IP setups, a changed router (new IP range, DHCP settings, or Wi‑Fi band) can strand the CCTV camera even though it still shows power.
– Some cameras appear unresponsive if the network is isolated (guest Wi‑Fi/client isolation) or if multicast/stream settings are incompatible with the NVR.
– Firmware/app mismatch can also cause “not working” behavior—avoid repeated random resets if you can identify your current model and firmware state.
Also note a common limit: some network troubleshooting actions (like disabling isolation or changing routing) can disrupt other devices. If you don’t want that risk, stop after confirming camera reachability and NVR/app configuration match.
Verdict / practical tip (when to stop troubleshooting)
If your CCTV camera powers on and status indicators change during startup, focus on cabling/ports first, then network/app configuration. If you confirm power is present but you still get no video and the CCTV camera won’t respond to the app/NVR after you’ve checked ports, IP/network settings, and basic IR/lens cleanliness, the fastest next step is usually to contact the manufacturer support or a CCTV installer.
When a CCTV camera shows power indicators during boot but the NVR/app never establishes a valid stream, the bottleneck is more often configuration/compatibility than the image sensor itself.
Going beyond fundamentals (DHCP reservations, subnet changes, and isolation toggles) can extend downtime and create side effects for other devices on the same network.
Downside: deeper network troubleshooting (subnets, DHCP reservations, router isolation settings) can take time and may disrupt other devices on your network—skip it if you don’t want to change network settings. If the camera is physically damaged (water ingress, impact, cracked housing), troubleshooting won’t reliably fix it.
Scan-and-save checklist
When you’re troubleshooting a CCTV camera not working, use this checklist to confirm the most common causes in order. If you can tick off each item and still get no video, you’re likely dealing with either a compatibility issue or hardware failure.
A structured check (power → cabling → channel/port mapping → IP reachability → stream settings → IR/lens cleanliness) reduces time-to-fix for CCTV camera “no signal” problems.
If your CCTV camera is reachable on the network but the NVR/app can’t display video, your next step is usually stream/codec/resolution alignment rather than more power cycling.
– [ ] Camera has correct power (adapter/PoE working, indicators during startup)
– [ ] Cabling is seated and not damaged (BNC/DC connectors, coax/Ethernet)
– [ ] Correct DVR/NVR channel/port is selected
– [ ] IP camera is online (same network/subnet, IP address reachable)
– [ ] App/NVR settings match the camera (stream/resolution/codec)
– [ ] Night mode/IR isn’t blocked; lens/IR window is clean
– [ ] Reboot sequence done (camera → NVR/app, or per system guidance)
Sources
– IEEE Std 802.3 (Ethernet and PoE specifications) — for Ethernet link distance guidance and PoE power class limits.
– RFC 7826 (RTSP) — for RTSP being a common transport/control mechanism used in IP camera streams.
A CCTV camera that isn’t working is usually fixable by following a disciplined path: confirm power first, then verify cabling and the correct DVR/NVR channel/port, and only then move to IP addressing/stream settings and IR/lens cleanliness. If the CCTV camera shows power but never produces video after those checks—especially in 2026 compatibility scenarios—the most efficient next move is manufacturer support or a qualified installer.
Frequently Asked Questions
What should I check first when a CCTV camera is not working?
Start by confirming power to the CCTV camera—check the power adapter, PoE switch, and any junction boxes for loose connections or damaged cables. Then verify the camera video signal by checking the monitor/recorder inputs (for DVR/NVR) and confirming the correct channel is selected. If the camera has IR LEDs, test in a dark area to see whether the image changes, which helps rule out lens or IR issues.
How do I troubleshoot CCTV camera no signal or “offline” issues?
For analog CCTV, ensure the BNC connection at both the camera and DVR is secure and that the cable is not cut or shorted. For IP CCTV, confirm the network connectivity: reboot the NVR/router, check the camera’s IP address (and DHCP status), and verify you can see the camera in the NVR interface or via its app/software. If it’s still offline, test the cable by swapping with a known-good Ethernet run and check for broken PoE injection or a faulty PoE port.
Why is my CCTV camera showing a black screen or no image?
A black screen is often caused by power instability, a failed camera sensor, or a connection problem between the CCTV camera and the DVR/NVR. Inspect the video/power wiring for corrosion, water ingress, or loose crimps, especially around outdoor junctions and conduit entries. If connections look good, try resetting the camera (power cycle or software reset) and test with another monitor channel or NVR input to isolate whether the issue is the camera or the recorder.
How can I fix CCTV camera that records but won’t display properly?
If recordings exist but live view is blank or distorted, the issue may be with the display settings, permissions, or the wrong stream selected in the CCTV software. Check the resolution and encoding settings on the NVR/DVR and camera to ensure compatibility, and confirm the correct channel profile is used for live streaming. Also reboot the NVR/DVR and verify the HDMI/VGA output from the recorder to the monitor is working, since problems there can mimic a camera failure.
Which is the best way to diagnose a faulty CCTV camera versus a faulty DVR/NVR?
Use a process of elimination by testing the camera with a different cable run and plugging it into another working channel on the DVR/NVR. If available, test another known-good camera on the suspect channel; this quickly identifies whether the problem is in the CCTV camera hardware or the recorder/channel. For IP systems, you can also confirm camera health via the camera’s web interface/app; if the device is reachable but the NVR can’t show video, the issue is likely settings, ports, or the NVR channel configuration.
📅 Last Updated: October 26, 2026 | Topic: How do you fix a CCTV camera that is not working? | Content verified for accuracy and freshness.
References
- Closed-circuit television
- Troubleshooting | Axis Communications
- https://www.hikvision.com/en/support/faq/
- Warranty & Repair | Hanwha Vision
- Realignment | Life Safety Systems
- https://www.flir.com/support/
- https://scholar.google.com/scholar?q=CCTV+camera+troubleshooting+no+video Google Scholar
- https://scholar.google.com/scholar?q=IP+camera+troubleshooting+power+network+not+working Google Scholar
- https://scholar.google.com/scholar?q=video+surveillance+system+troubleshooting+guides Google Scholar



