Back to Frigate Guides
Frigate

How to Fix Frigate Live View Slow or Not Loading

Frigate GuideSecurity Cameras
hard difficulty 20-30 minutes 468 views 0 found helpful Where this fix applies: Global Updated
This guide applies to: Frigate Frigate Live View Performance (Frigate live view via go2rtc WebRTC/MSE paths)
At a glance — most common causes
  • Using jsmpeg (CPU-heavy) instead of WebRTC/MSE
  • go2rtc restream not set up for low-latency
  • High-res stream over a weak link
20-30 minutes13 solutions coveredhard level

Expert Review & Technical Scope

DeviceFrigate Frigate Live View Performance
Model CoverageFrigate live view via go2rtc WebRTC/MSE paths
Fix Time20-30 minutes
DifficultyHard
Required Toolsfrigate config, browser test access, camera stream settings
Network / ProtocolWi-Fi / app-based troubleshooting context

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.

Why This Happens in Real Homes

Frigate live view being slow or not loading usually comes down to how the live stream is delivered. The default jsmpeg player is CPU-heavy and higher-latency, while WebRTC or MSE (via go2rtc) give a much smoother, lower-latency live view — so setting up go2rtc restreaming for live view is the single biggest improvement. Codec and server load are the other factors.

Configure go2rtc to provide the live stream and enable WebRTC/MSE in Frigate for the smoothest experience, using an H.264 (and AAC audio) stream the browser can play without transcoding. Use the camera's sub-stream for live view where full resolution isn't needed, ensure the server isn't overloaded (enable hardware acceleration for decoding), and limit how many high-res streams play at once. A go2rtc-backed WebRTC live view resolves most slowness.

Symptoms

  • Live view slow to load
  • Live view stutters
  • Live view won't load
  • Laggy live view
  • Buffering live view
  • High latency in live view
  • Live view fails
  • Slow camera feeds

Recognize these? Here's what usually causes it.

Common Causes

  • Using jsmpeg (CPU-heavy) instead of WebRTC/MSE
  • go2rtc restream not set up for low-latency
  • High-res stream over a weak link
  • Server CPU overloaded (transcoding)
  • Codec needing transcode for the browser
  • Network bandwidth limited
  • Too many simultaneous viewers
  • Config not optimized for live

Most fixes happen in the first 3 steps.

Warning

Do not increase resolution and frame rate blindly for live view; this often worsens reliability without meaningful monitoring benefit.

Tools & Requirements

frigate configbrowser test accesscamera stream settings

Step-by-Step Solution

1

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.

2

Adjust keyframe and stream design

Set practical keyframe interval and make sure 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.

3

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.

4

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.

5

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

Set up WebRTC or MSE via go2rtc for live view
Configure go2rtc restream for the live view
Use the sub-stream for live view where possible
Reduce server load / enable hardware acceleration
Provide a browser-friendly codec (H.264/AAC)
Ensure adequate bandwidth
Limit simultaneous live viewers
Optimize the live-view config

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.

Pro Tip

Use separate streams for detect/record/live roles to balance quality and latency instead of forcing one stream to do everything.

Real-World Insight

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.

What Usually Goes Wrong
  • Using jsmpeg (CPU-heavy) instead of WebRTC/MSE
  • go2rtc restream not set up for low-latency
  • High-res stream over a weak link
  • Server CPU overloaded (transcoding)
  • Codec needing transcode for the browser

Official Manufacturer Manual

Frigate provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Frigate Live View Performance.

View Frigate Live View Performance Online Manual

Source: docs.frigate.video

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.