How to Fix Frigate Object Snapshots Not Generating
- Snapshots disabled for the camera/object
- Storage/permissions issue
- Snapshot retention set to zero/short
Problem Description
Frigate events appear in the timeline but no snapshot images are generated — thumbnails show blank or broken, MQTT snapshot messages are empty, and the snapshot API returns no image. Snapshots must be explicitly enabled per camera, detection must be running, and the storage directory must have available space.
Why This Happens in Real Homes
Frigate not generating object snapshots is usually a settings or storage issue — snapshots (the still image saved for a detected object) have to be enabled per camera and object, and they need writable storage with a retention period set. If snapshots are disabled, retention is zero, or the storage path isn't writable, no images get saved even though events are detected.
In the config, enable snapshots for the relevant cameras and object types and set a snapshot retention period, then verify the media storage is mounted, writable (correct permissions), and not full. Check that an object filter isn't excluding the detections you expected snapshots for. With snapshots enabled and healthy writable storage, the still images generate alongside events.
Symptoms
- Object snapshots not generating
- No snapshot images
- Events without snapshots
- Snapshot missing
- Snapshots not saved
- No object images
- Snapshot generation fails
- Empty snapshot
Recognize these? Here's what usually causes it.
Common Causes
- Snapshots disabled for the camera/object
- Storage/permissions issue
- Snapshot retention set to zero/short
- Storage full
- Config not enabling snapshots
- Object filter excluding the snapshot
- Path/mount problem
- Frigate version bug
Most fixes happen in the first 3 steps.
Do not treat detection-only logs as sufficient if snapshots are required operationally.
Tools & Requirements
Step-by-Step Solution
Enable snapshots in the camera config
Snapshots must be explicitly enabled per camera. In frigate.yml: cameras: your_camera: snapshots: enabled: true. You can also configure: bounding_box: true (draws the detection box on the snapshot), crop: true (crops to just the detected object), quality: 70 (JPEG quality 1-100), and timestamp: true (overlays the time on the snapshot). Without enabled: true, Frigate creates events but does not capture snapshot images.
Check that detection is working
Snapshots are generated from detection frames — they are captured when the object detector identifies an object. If detection is not running (detect not enabled, Coral TPU not detected, or the detect stream is offline): no frames are processed and no snapshots are taken. Check the Frigate system dashboard for detection metrics. The detect FPS counter should show a non-zero value. If it shows 0: the detect stream is not running.
Verify storage has space for snapshots
Each snapshot is a JPEG image, typically 50-200KB depending on resolution and quality settings. With 100+ events per day, snapshots accumulate quickly. If the storage mount is full: new snapshots cannot be written. Check disk space on the Frigate media directory. Set retention: snapshots: retain: default: 7 to auto-delete snapshots older than 7 days and prevent storage from filling up.
Check snapshot publishing via MQTT
If you access snapshots through Home Assistant or another MQTT client: snapshots are published as JPEG binary data on the topic frigate/camera_name/person/snapshot. Large snapshots (>256KB) may exceed your MQTT broker's maximum message size limit. Mosquitto's default max payload is 256MB, but some brokers or proxy configurations limit it lower. Check MQTT broker settings if snapshots are received as empty messages.
Test snapshot access via the Frigate API
Frigate provides a REST API for snapshots. Access the latest snapshot directly: http://frigate-ip:5000/api/camera_name/latest.jpg. If this returns an image: snapshots are generating correctly and the issue is in how you are accessing them (MQTT, Home Assistant integration, or web UI). If this returns a 404 or blank: the camera is not generating snapshots. Check the camera's event list in the Frigate web UI — click an event and see if the thumbnail loads.
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.
Snapshot retention should align with incident-review workflow.
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 disabled for the camera/object
- Storage/permissions issue
- Snapshot retention set to zero/short
- Storage full
- Config not enabling snapshots
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 Snapshot Pipeline.
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 Snapshot Pipeline.
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.