Verkada

Verkada Poor Video Quality? Enterprise Fix Guide

Resolve Verkada video quality issues with advanced diagnostics and Verkada Command tools. Identify root causes from network misconfigurations to hybrid storage conflicts.

Is this your issue?

Camera shows 4K resolution in VMS but streams at 1080p
Verkada Command motion search fails to detect movement in specific zones
RTSP stream drops intermittently despite stable network link
Firmware update stuck in pending state in the management platform
Verkada Command's Bandwidth Monitor shows unexpected spikes
Hybrid storage reports 'insufficient space' despite local disk having 50% free
Camera lens appears blurred in Verkada Command's Live View

Sound familiar? The guide below will help you fix it.

Verify Your Verkada Camera's Network Configuration

Degraded video quality often stems from network misconfigurations or hybrid storage conflicts. Confirm your camera is on a dedicated VLAN with QoS prioritisation, and that hybrid storage settings align with your retention needs. Use Verkada Command's Device Health dashboard to identify potential root causes quickly.

Verkada Quick Diagnostics

Before diving into advanced diagnostics, perform these 30-second checks:

Check VMS Dashboard: In Verkada Command, navigate to Cameras → [device] → Diagnostics and verify Connection Health shows Stable.
Verify PoE Link Light: Ensure the switch port shows a green PoE link light (Class 3 or 4). A Class 0 status indicates negotiation failure.
Power Cycle via Switch: Disable the switch port for 10 seconds, then re-enable to restart the camera.
Ping Camera IP: Use ping [camera_ip] from the management server to confirm network reachability.
Check Status LED: A blinking amber light on the camera indicates a firmware update in progress.

Verify Verkada Command Network Diagnostics

Access Cameras → [device] → Network Diagnostics to identify potential issues:

Check VLAN Assignment

Confirm the camera is assigned to a dedicated VLAN (e.g. VLAN 100 for cameras).
Ensure 802.1p tagging is enabled if using QoS.
If VLAN mismatch is detected, adjust settings in Network Settings.

Validate PoE Budget

Check the Power Usage tab for real-time consumption (e.g. CB62 Bullet uses ~12W).
Compare against your switch's advertised PoE budget (e.g. 30W per port for 802.3at).
If budget is exceeded, consider upgrading to a higher PoE standard (e.g. 802.3bt).

Check Hybrid Storage Configuration

Verkada's hybrid model stores recent footage locally and archives events in the cloud. Poor video quality may result from:

Confirm Local Storage Settings

In Cameras → [device] → Storage, verify Retention Period is set to 30-365 days (depending on model).
Ensure Cloud Backup is enabled for AI-processed events.

Resolve Cloud Connectivity Issues

Check Cloud Connectivity Status in the same section. A disconnected status may indicate a firewall blocking Verkada's cloud ports (check Verkada Help Centre for required ports).
If using 4G/5G backup, ensure the SIM card has sufficient signal strength (check Signal Strength in the dashboard).

Diagnose Verkada Command Video Quality Analytics

Poor analytics performance (e.g. motion search failures) may indicate:

Verify Camera Placement

Use Verkada Command's Motion Search to draw regions in the timeline. If detection fails, ensure the camera has minimum 40 pixels per foot coverage (check Analytics Module Status).

Check Lens Cleanliness

Use Lens Inspection Tool in Verkada Command to identify smudges or condensation (see related article on condensation inside lens for solutions).

Adjust Bitrate and Compression

In Cameras → [device] → Video Settings, confirm Bitrate is set to Auto and Compression to H.265.
For 4K models like CB62 Bullet, avoid H.264 as it increases bandwidth usage.

Advanced Troubleshooting: Enterprise-Specific Tools

If basic fixes fail, proceed with these steps:

Perform Packet Capture

Use Packet Capture in Verkada Command to identify network congestion or packet loss.
Analyse the capture for RTSP stream drops or multicast issues.

Repair VMS Database

For VMS integration issues, navigate to System → Database in your VMS platform and run a Consistency Check.
If corruption is detected, restore from a recent backup.

Escalate to Enterprise Support

If the issue persists, use Verkada's Enterprise Support Portal to submit a Support Ticket with the Packet Capture and Device Health data.
Include details on firmware channel and VLAN configuration for faster resolution.

Root Causes of Verkada Video Degradation

Common enterprise-level issues include:

PoE Budget Exhaustion: Multiple cameras on a single switch port may exceed the 802.3at (30W) limit.
VLAN Misconfiguration: Missing 802.1p tagging or incorrect VLAN IDs may throttle bandwidth.
Hybrid Storage Conflicts: Local storage retention settings conflicting with cloud backup policies.
Firmware Incompatibility: Using Beta firmware without VMS compatibility checks.
UK-Specific Challenges: Double glazing reducing Wi-Fi signal strength by 20-30dB (see related article on Verkada live view buffering for solutions).

How to Prevent Future Verkada Poor Problems

Implement these strategies to avoid recurring issues:

Schedule Firmware Updates

Use Verkada Command's Firmware Channel to ensure all cameras are on the Stable channel.
Schedule updates during off-peak hours to avoid disrupting video streams.

Plan PoE Budget Headroom

Reserve 20% extra capacity on switches to accommodate future camera additions.
Use PoE Budget Calculator in Verkada Command to estimate requirements.

Implement Network Best Practices

Create a dedicated camera VLAN (e.g. VLAN 100) with QoS prioritisation.
Enable SNMP monitoring to track switch port utilisation.

Full disclosure: we built scOS to address exactly this—the complexity of managing enterprise camera fleets across VLANs. scOS uses permanently powered cameras connected via ethernet.

When to Replace Your Verkada Poor Equipment and Lifecycle Management

When troubleshooting exceeds 30 minutes, consider hardware replacement:

Wired Camera Lifespan: 5-8 years for models like CD62 Dome (check warranty_uk for Consumer Rights Act 2015 coverage).
Battery Camera Lifespan: 3-5 years for battery-powered models (degrades after 300-500 cycles).
Surveillance HDD Lifespan: 3-5 years for WD Purple/Seagate SkyHawk drives (replace if VMS shows disk errors).
SD Card Lifespan: 1-2 years for microSD in CB62 Bullet (use Samsung PRO Endurance for high-endurance needs).

What if every frame was crystal clear?

scOS works with any wired camera — including professional-grade models. It detects suspicious activity and only alerts you when it matters. All features included.

Detects Suspicious Activity

Not motion — actual suspicious behaviour. Like a person would notice.

Designed to Be Left Alone

No settings to tweak. No app to check. It just works.

All Features Included

No subscriptions. No tiers. Everything works from day one.

See why this keeps happening

Works with any wired camera brand. See all features

Frequently Asked Questions

Verify VLAN assignments in Verkada Command by navigating to Cameras → [device] → Network Settings. Ensure the camera is on a dedicated VLAN with QoS prioritisation for video streams. If VLANs are misconfigured, switch port settings may throttle bandwidth. Use Network Diagnostics in Verkada Command to identify VLAN mismatches or missing 802.1p tagging. For PoE budget issues, check the Power Usage tab in the same section and compare against your switch's advertised PoE budget. If the camera is drawing more than 15.4W (Class 4), consider upgrading to a higher PoE standard or reducing concurrent camera loads.

In Verkada Command, access Cameras → [device] → Video Settings and confirm the stream profile matches your VMS requirements. For 4K cameras like the CB62 Bullet, ensure Bitrate is set to Auto and Compression to H.265. If the VMS is receiving 1080p streams despite 4K capability, check the RTSP URL in the VMS configuration. A mismatch in stream profiles (e.g. using Main Profile instead of Baseline) may reduce resolution. Use the Bandwidth Monitor in Verkada Command to identify unexpected bitrate spikes or drops that correlate with video degradation.

Access Cameras → [device] → Firmware in Verkada Command to ensure the camera is on the Stable firmware channel. If the camera is on Beta, switch channels and restart the device. For staged rollouts, verify Firmware Rollout Status shows 100% Success. If a rollback is needed, use the Rollback button in the same section but note this may revert analytics features like Person/Vehicle Detection. Ensure your VMS is compatible with the firmware version—check Verkada Compatibility Matrix for VMS integration details.

Use Network Diagnostics in Verkada Command to capture packet loss and jitter metrics. If the Connection Health tab shows more than 5% packet loss or more than 100ms latency, check switch port configurations for Flow Control or Pause Frames. For cloud-managed cameras, verify Cloud Connectivity Status in the same section. If the camera is using 4G/5G backup, ensure the SIM card has sufficient data allowance and signal strength. For on-premises cameras, use Wi-Fi Analyzer in Verkada Command to identify channel congestion on 2.4GHz networks.

For UK-specific issues like double glazing or stone walls, use Wi-Fi Analyzer in Verkada Command to identify signal degradation. If the camera is using Wi-Fi and shows poor quality, consider a hardwired PoE connection. For victorian terrace layouts, ensure the camera is within 30m of the router. If using foil insulation, verify the camera's RF shielding is intact. For cavity walls, use Wi-Fi Extenders with MU-MIMO support to maintain signal integrity.

All Troubleshooting Guides