Tesla has three storage buckets, not one
The mental model most new Tesla owners have — "my dashcam records everything and keeps it" — isn't how it actually works. Tesla uses three separate folders inside TeslaCam/, each with different retention behaviour:
RecentClips/— a rolling buffer of the last ~60 minutes of driving (varies by drive size). Tesla auto-deletes the oldest clips as new ones come in. This is always churning.SentryClips/— footage captured around Sentry Mode detection events. Preserved longer than RecentClips, but Tesla will auto-clean older SentryClips folders when the drive starts running low on space to make room for recording to continue.SavedClips/— footage you explicitly pressed the dashcam-save button for while driving. Preserved until you manually delete. This is the only bucket Tesla doesn't auto-clean.
If the clip you're looking for was a Sentry event that happened weeks ago on a drive that's been actively recording since, there's a real chance Tesla itself deleted the SentryClips folder to free space — not formatting, not corruption, just the car's normal housekeeping.
The event.json sidecar
Each SentryClips event folder also contains a tiny event.json file that records metadata about why the event fired:
- reason — what triggered it (alarm, glass break, object detection, lean-on, honk)
- camera — which camera first detected the event
- timestamp — exact time of the trigger
- est_lat / est_lon — approximate GPS when the event fired
This file is less than 1 KB and often survives even when the clip MP4s themselves have been partially overwritten. Recovering the event.json alongside the clips gives you the "why" behind each event — useful if you're compiling incident evidence for insurance or police and need to explain what the car was detecting.
What's actually recoverable
When SentryClips data has been auto-deleted by Tesla (not secure-erased — just marked as free space by the file system), the MP4 cluster data is still physically on the drive until something else gets written over it. Because Tesla writes new RecentClips sequentially, the rate of overwriting is predictable: roughly 4 GB per hour across all cameras.
On a 128 GB drive that was running near full, a Sentry event from three days ago may have been partially overwritten by subsequent RecentClips recording. Some of its six camera MP4s may still be intact; others may be partially overwritten (lower confidence scores, possibly playback glitches in specific segments); one or two may be entirely gone.
A good recovery scan finds whatever's recoverable, scores each clip 0–100 based on structural completeness, and lets you save only the ones worth saving.
Why this happens more on smaller drives
Older Tesla documentation suggested USB drives as small as 32 GB. With Tesla's ~4 GB/hour recording rate, a 32 GB drive fills completely in about eight hours of driving and starts auto-deleting immediately. That's one long day of commuting. Sentry events on a 32 GB drive are almost always at risk.
On a 256 GB drive, you've got roughly 64 hours of driving headroom before the oldest content starts getting cycled. That's enough margin that most Sentry events survive until you next plug the drive in — unless the car has been heavily driven since the event.
Prevention — before the next incident
- Press the Save button. When Tesla notifies you of a Sentry event, open the dashcam UI and tap "Save." This moves the clip from SentryClips to SavedClips, which Tesla never auto-deletes.
- Use a drive with headroom. 128 GB minimum; 256 GB preferred if you drive daily. More headroom means more time to review events before they're at risk.
- Two-drive rotation. Keep two USB drives. Rotate one out of the car weekly. Copy anything interesting off before putting it back in. At any moment, one drive is a snapshot.
- Check periodically. Plugging the drive into a computer once a week and eyeballing SentryClips catches anything notable before it ages out.
When the Sentry event was critical
If you're trying to recover a Sentry clip for an insurance claim, police report, or legal proceeding, the sequence is:
- Remove the USB drive from the Tesla now. Every minute of further driving reduces recoverability.
- Run a scan to see what's still there. Free scans surface every recoverable clip — including partially-overwritten ones — with confidence scores.
- Recover anything scoring above 40. Even lower-confidence clips may contain enough visible detail to identify a license plate or confirm what happened.
Recovered MP4 files are byte-for-byte copies of what Tesla originally wrote — not reconstructions. Insurance companies and police generally accept them as evidence when supplied with the confidence score as documentation of file integrity.