How to Fix Frigate Event Clips Not Playing in Browser
- codec/container incompatibility
- incomplete clip indexing
- reverse proxy header/range handling issue
Problem Description
You click on a Frigate event to view the recorded clip, but the video does not play — the browser shows a black box, a loading spinner that never resolves, or a codec error. The most common cause is the camera recording in H.265 (HEVC), which most browsers cannot play natively. Other causes include corrupt clip files, missing file permissions, or an outdated Frigate version.
Why This Happens in Real Homes
Why this happens in real homes usually comes down to environment and timing, not instant hardware failure. Event clips exist but fail to play in web UI/browser clients. The pattern people actually report is Playback error, blank player, and clips download but do not stream
The most common real-world triggers are codec/container incompatibility, incomplete clip indexing, and reverse proxy header/range handling issue. The fix is most reliable when the sequence is followed exactly: Check clip codec/container, then Validate clip metadata/index, then Test direct vs proxied playback. After the repair, run multiple command and automation checks so the issue does not reappear later in the day.
Symptoms
- Playback error
- blank player
- clips download but do not stream
Recognize these? Here's what usually causes it.
Common Causes
- codec/container incompatibility
- incomplete clip indexing
- reverse proxy header/range handling issue
Most fixes happen in the first 3 steps.
Do not assume local file playback equals web client compatibility.
Tools & Requirements
Step-by-Step Solution
Check the video codec in recordings
Frigate records clips in the codec your camera outputs — typically H.264 or H.265. Most browsers play H.264 natively but cannot play H.265 (HEVC). If your camera's record stream is set to H.265: clips will not play in the Frigate web UI or Home Assistant media player. Fix: change the camera's main/record stream to H.264 in the camera's web interface. H.264 is universally supported across all browsers and media players.
Check the clip file path and permissions
If clicking an event shows a loading spinner that never resolves or a 'not found' error: the clip file may not exist at the expected path or Frigate cannot read it. Check the Frigate logs for file-not-found errors. Verify the media path is correctly mounted in Docker and the files exist: ls -la /media/frigate/clips/. If files exist but cannot be played: check file permissions — the web server process needs read access to the clip files.
Test playback outside of Frigate
Download a clip file directly and try playing it in VLC on your computer. If VLC plays it fine but the browser does not: the issue is browser codec support (likely H.265). If VLC also cannot play it: the file is corrupt — possibly from a storage write error, disk full condition, or the recording being interrupted. Corrupt clips cannot be recovered. Check that storage has adequate free space and the filesystem is healthy.
Check the Frigate web UI version
Older Frigate versions (pre-0.12) had known issues with clip playback in certain browsers. Update Frigate to the latest version. In the Home Assistant add-on: go to Settings > Add-ons > Frigate > check for updates. In Docker: pull the latest image (docker pull ghcr.io/blakeblackshear/frigate:stable). Newer Frigate versions include an improved media player that handles more codecs and provides better error messages when playback fails.
Check browser compatibility
Safari on macOS supports H.265 playback but Chrome and Firefox do not (as of 2026). If clips play in Safari but not Chrome: your camera is encoding in H.265. Firefox also has issues with some H.264 profiles (High 4:2:2 profile is not supported). For the most compatible setup: set your camera to H.264 Baseline or Main profile at the record stream level. This ensures clips play in any browser without transcoding.
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.
Browser playback reliability depends on encoding and transport headers.
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.
- codec/container incompatibility
- incomplete clip indexing
- reverse proxy header/range handling issue
Before you go — try one of these (they fix most cases).
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 Browser Playback Issues.
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.