How to Fix Frigate Live View Slow or Not Loading
- Keyframe interval too high
- Browser codec mismatch
- go2rtc stream not optimized for live
Problem Description
Frigate live view loads slowly, stutters, or fails completely while recordings may still work. This is commonly caused by keyframe settings, codec/browser incompatibility, constrained hardware decode paths, or overloaded stream role design.
Symptoms
- Live view takes long to start
- Video stutters or buffers
- Black screen in browser live view
- Some cameras load while others fail
- Recordings look fine but live is broken
- Issue worse on mobile
Recognize these? Here's what usually causes it.
Common Causes
- Keyframe interval too high
- Browser codec mismatch
- go2rtc stream not optimized for live
- NVR hardware decode overloaded
- Wrong live method selected
- Network jitter between client and NVR
Most fixes happen in the first 3 steps.
Do not increase resolution and frame rate blindly for live view; this often worsens reliability without meaningful monitoring benefit.
Tools & Requirements
Step-by-Step Solution
Measure baseline live behavior
Test one camera on local network first and record start time, smoothness, and failure pattern. Isolating a single stream helps determine if issue is global platform load or camera-specific configuration mismatch.
Adjust keyframe and stream design
Set practical keyframe interval and ensure live stream profile is optimized for low-latency preview rather than heavy record-quality output. Using the same high-bitrate stream for all purposes commonly causes slow starts and dropped live sessions.
Match codec to client support
Check browser/client compatibility with selected video/audio codecs. If live path uses unsupported codec, playback can fail while recordings remain valid. Use compatible transcoding or camera stream settings where needed.
Select proper live transport mode
Test both MSE and WebRTC paths and keep the one that performs best in your network conditions. Some environments are more stable with one method, especially when NAT, mobile clients, or constrained hardware are involved.
Load test and finalize
Open multiple live feeds gradually and watch CPU, memory, and network impact. Set practical live-view concurrency limits if needed. A stable tuned profile is better than max quality that fails during real-world usage.
Quick Solutions
Still having issues? This is usually the deeper cause below.
Camera issues that start suddenly almost always trace back to an upload bandwidth drop — run a speed test before assuming hardware failure.
Use separate streams for detect/record/live roles to balance quality and latency instead of forcing one stream to do everything.
Live view problems that start suddenly usually trace back to an upload speed drop — the camera itself is fine, the bandwidth path to the cloud isn't.
- Keyframe interval too high
- Browser codec mismatch
- go2rtc stream not optimized for live
- NVR hardware decode overloaded
- Wrong live method selected
Before you go — try one of these (they fix most cases).
Need More Help? Frigate Support
Note: The contact information below connects you directly to Frigate's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.