How to Fix Frigate Event Thumbnail Not Loading
- Snapshots/thumbnails not generated (storage/permissions)
- Storage full or unwritable
- Browser cache issue
Problem Description
Frigate events appear in the timeline but thumbnails show as broken images, blank placeholders, or never load. Thumbnails are generated from detection snapshots — if snapshots are not enabled, storage is full, the MQTT connection is broken, or the detect stream quality is too low, thumbnails fail to generate or display.
Why This Happens in Real Homes
Frigate event thumbnails not loading usually ties back to snapshot generation and storage — thumbnails are derived from the snapshot images, so if snapshots aren't being saved (disabled, or storage isn't writable or is full), there's no thumbnail to display. A browser cache issue can also make thumbnails appear broken when they actually exist.
Confirm snapshots are enabled and generating with healthy, writable, non-full storage (the same requirements as object snapshots), then clear your browser cache or hard-refresh in case it's a display issue. Verify the media path is correctly mounted, update Frigate to rule out a version bug, and address slow storage that might delay thumbnail creation. Working snapshot storage plus a fresh browser view restores the thumbnails.
Symptoms
- Event thumbnail not loading
- Missing thumbnails
- Broken thumbnail images
- Thumbnails blank
- Timeline thumbnails missing
- No preview images
- Thumbnail fails to load
- Empty event preview
Recognize these? Here's what usually causes it.
Common Causes
- Snapshots/thumbnails not generated (storage/permissions)
- Storage full or unwritable
- Browser cache issue
- Thumbnail generation disabled
- Path/mount problem
- Frigate version bug
- Slow storage delaying thumbnails
- Config not enabling snapshots
Most fixes happen in the first 3 steps.
Do not assume event records imply media preview artifacts exist.
Tools & Requirements
Step-by-Step Solution
Check snapshot storage configuration
Frigate generates thumbnails from snapshots taken during detection events. Snapshots must be enabled: cameras: your_camera: snapshots: enabled: true. Without this setting, Frigate creates event entries but does not capture the snapshot image used for thumbnails. After enabling, restart Frigate — new events will have thumbnails. Existing events without snapshots cannot be retroactively given thumbnails.
Verify the snapshot storage path has space
Thumbnails are stored alongside clips in the media directory. If the storage drive is full: new thumbnails fail to write and events show a generic placeholder or broken image. Check disk space on the Frigate media mount. Thumbnails are small (10-50KB each) but accumulate over time — 100 events/day × 30 days = 3,000 thumbnails. Set snapshot retention: snapshots: retain: default: 14 to auto-clean old thumbnails.
Check MQTT thumbnail publishing
If you are viewing thumbnails through Home Assistant or another MQTT-connected service: thumbnails are published via MQTT on the topic frigate/events. If your MQTT broker is down or the connection between Frigate and MQTT is broken: thumbnails do not reach Home Assistant. Check Frigate logs for MQTT connection errors. Verify the MQTT broker is running and Frigate can connect to it (mqtt: host, port, user, password in frigate.yml).
Check the detect stream quality
Thumbnails are cropped from detection frames. If the detect stream resolution is very low (320x240) or heavily compressed: thumbnails appear blurry or pixelated to the point of being useless. Set the detect stream to at least 640x480 or 720p in your camera settings. Higher detect resolution produces better thumbnails but uses more CPU. The thumbnail is a crop of the detected object, so a 720p detect stream produces a reasonably clear person thumbnail at 100-200px resolution.
Clear the Frigate cache and restart
If thumbnails worked before but stopped loading: the Frigate internal cache or the browser cache may be stale. Clear your browser cache for the Frigate web UI URL. Then restart Frigate to regenerate its internal state. In some cases, upgrading Frigate changes the thumbnail storage format and old thumbnails become incompatible — a restart after upgrade rebuilds the thumbnail index from the clip files.
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.
Thumbnail integrity helps fast triage in high-event environments.
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.
- Snapshots/thumbnails not generated (storage/permissions)
- Storage full or unwritable
- Browser cache issue
- Thumbnail generation disabled
- Path/mount problem
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 Event Thumbnails.
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.
Accessories owners commonly pair with Frigate Event Thumbnails.
SANDISK 64GB Extreme microSDXC UHS-I Memory Card with Ada...
SANDISK 128GB Ultra microSDXC UHS-I Memory Card with Adap...
SANDISK 64GB Ultra microSDXC UHS-I Memory Card with Adapt...
As an Amazon Associate we earn from qualifying purchases.