How to Fix Frigate Snapshot Images Not Saving to Storage
- Snapshot feature disabled
- permission issue on storage mount
- path mapping mismatch
Problem Description
Frigate is not saving snapshot images to storage — the snapshot directory is empty, event thumbnails are blank, and the latest snapshot API returns no image. Snapshots must be explicitly enabled per camera in frigate.yml, the storage directory must be writable and have available space, and retention settings control how long snapshots are kept before auto-deletion.
Why This Happens in Real Homes
Why this happens in real homes usually comes down to environment and timing, not instant hardware failure. Detections occur but snapshot images are missing from expected storage path. The pattern people actually report is No snapshot files, event metadata exists, and snapshot path empty
The most common real-world triggers are Snapshot feature disabled, permission issue on storage mount, and path mapping mismatch. The fix is most reliable when the sequence is followed exactly: Confirm snapshot config enabled, then Validate storage write permissions, then Retest event output. After the repair, run multiple command and automation checks so the issue does not reappear later in the day.
Symptoms
- No snapshot files
- event metadata exists
- snapshot path empty
Recognize these? Here's what usually causes it.
Common Causes
- Snapshot feature disabled
- permission issue on storage mount
- path mapping mismatch
Most fixes happen in the first 3 steps.
Do not assume event records guarantee media artifact creation.
Tools & Requirements
Step-by-Step Solution
Enable snapshots in camera configuration
Snapshots are disabled by default. In frigate.yml: cameras: your_camera: snapshots: enabled: true, retain: default: 10. This saves a JPEG snapshot for each detection event, retained for 10 days. Without enabling this setting, detection events are recorded in the database but no snapshot files are written to storage. After changing the config, restart Frigate for the setting to take effect.
Check the storage mount and available space
Snapshot images are saved to the Frigate media directory, typically /media/frigate/clips/. In Docker, this path must be volume-mapped to a host directory. Check your docker-compose.yml for the volume mapping. Then verify the host directory has available space: df -h /path/to/frigate/storage. If full, snapshots fail silently. Set retention limits to automatically clean old snapshots: snapshots: retain: default: 7.
Verify snapshot files exist on disk
After enabling snapshots and triggering a detection event: check if files were created. List the snapshot directory: ls -la /media/frigate/clips/ (or the equivalent host path). Snapshot files are named with the event ID and camera name. If no files appear after a confirmed detection event: check Frigate logs for write permission errors or I/O failures. The Frigate process (container user) must have write access to the storage directory.
Access snapshots via the API instead of filesystem
Frigate provides REST API endpoints for snapshots: http://frigate-ip:5000/api/events/EVENT_ID/snapshot.jpg for event snapshots, http://frigate-ip:5000/api/CAMERA_NAME/latest.jpg for the most recent snapshot from a camera. If these endpoints return images: snapshots are working and the issue is how you are trying to access them (filesystem browsing vs. API). Home Assistant's Frigate integration uses the API automatically.
Configure snapshot quality and crop settings
Snapshot size and quality affect storage usage and clarity. In frigate.yml: snapshots: quality: 80 (JPEG quality, 1-100, default 70), height: 480 (resize to this height, maintaining aspect ratio). Higher quality = larger files. crop: true saves a cropped image of just the detected object — useful for person identification. bounding_box: true draws the detection rectangle on the snapshot. timestamp: true adds the detection time as a text overlay.
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 be validated after storage path changes.
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.
- Snapshot feature disabled
- permission issue on storage mount
- path mapping mismatch
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 Save Failures.
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.