How to Fix Frigate High CPU Usage After Config Changes
- Too many high-res streams
- Wrong decode settings
- Excessive snapshots
Problem Description
When your Frigate Frigate Performance Regression isn't working as expected, it usually traces back to one of a small number of causes — this guide covers them in order, starting with the most likely.
Symptoms
- CPU pegged
- UI lag
- Dropped frames
Recognize these? Here's what usually causes it.
Common Causes
- Too many high-res streams
- Wrong decode settings
- Excessive snapshots
Most fixes happen in the first 3 steps.
Avoid changing many performance knobs at once.
Tools & Requirements
Step-by-Step Solution
Diff recent config
Identify exact changes made before CPU increase.
Scale back heavy roles
Lower stream count/quality for detect roles first.
Enable proper acceleration
Confirm hardware decode config matches host capabilities.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Keep versioned config snapshots before major tuning.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- Too many high-res streams
- Wrong decode settings
- Excessive snapshots
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.