There's a cruel pattern to dashcam failures. Every clip on the card plays fine — the drive to work, the parking lot, the empty motorway. The one that won't open is the last one. The one recording when the car was hit, when the battery cut out, or when you yanked the card because you needed the footage right now.
That is not bad luck. It's the direct consequence of how these cameras write files, and once you understand it, the fix is obvious and the mistakes to avoid become obvious too.
Why it's always the last clip
A dashcam records in a loop, writing MP4 or MOV segments continuously. While a segment is being recorded, the video data streams into the file. The small table that tells a player where each frame starts — the index — is written at the end, when the segment closes normally.
Interrupt the camera mid-segment and that segment never gets its index. The footage is there on the card. The table describing it is not, so every player reports a corrupt file.
The three interruptions that cause it, in order of how often they happen:
- Power cut. The engine stops, a hardwire kit trips its low-voltage cutoff, or a capacitor dies mid-write. The camera loses power between writing the footage and writing the index.
- Impact. The event you most want on video is also the event most likely to jolt the power connector, trigger a shutdown, or crack the card seating.
- The card pulled while recording. Understandable in the moment, and the fastest way to produce exactly this failure. If the camera is still on, it is still writing.
Notice what these have in common: the footage was already recorded. The file is usually large and full. It's the closing table that's missing.
Do these three things first, in this order
1. Stop recording with that card. Now. A dashcam loops — it overwrites the oldest footage to make room. Leave the card in a running camera and it will eventually write over the very segment you're trying to save. This is the one mistake that turns a fixable problem into a permanent loss. Take the card out, or put a different card in the camera.
2. Copy the file off the card before touching it. Get the broken clip onto a phone or computer and work on the copy. If the card itself is failing, every read is a risk you don't need to repeat.
3. Check the obvious things. Does the file have a sensible size? A file of a few kilobytes means the recording died almost immediately and there may be nothing inside to recover. Did the copy finish? An interrupted transfer produces the same symptoms as a corrupt file, and re-copying is free.
What actually fixes it
The repair is not recovery — nothing needs undeleting. The index has to be rebuilt around the footage that's already in the file.
On your phone. Video Repair is our Android app for exactly this failure. Move the clip from the card to the phone, and it scans the raw data, finds every frame boundary, and writes a fresh index around your original footage. Checking, repairing and watching the full result are free — you see the recovered clip play before deciding anything — and the repair runs entirely on the device, which matters when the footage is evidence you'd rather not upload to a stranger's server. Nothing is re-encoded, so the picture is exactly what the camera recorded.
On a desktop. The open-source untrunc rebuilds truncated MP4/MOV from the command line using a healthy reference clip. Commercial desktop tools cover more formats and batch work — we compare the main ones in our Repairit comparison.
Whichever route you take: dashcams are the ideal case for index rebuilding, because a dashcam fills its card with segments recorded at identical settings. If a tool needs a healthy reference file from the same camera — and for recovering the audio track, ours does — the card is already full of them.
What can't be fixed, honestly
- Footage the loop already overwrote. If the camera kept running and recorded over that segment, the data is gone. This is why step one is "stop recording."
- A card that has failed physically. If the card won't mount or throws read errors, that's a hardware problem before it's a video problem.
- A file that's nearly empty. A few kilobytes means the recording never really started. There's no footage inside to rebuild an index around.
A good repair tool tells you which of these you're in rather than producing a file that opens and plays noise. That's the point of previewing the result before paying for anything.
The same failure on drones and action cameras
Everything above applies unchanged to drone footage and action cameras, for the same reason: they run on batteries that die mid-recording, they get shut off abruptly, and they crash. A drone that loses power in the air stops writing at exactly the moment you most wanted recorded. The mechanism is identical, and so is the fix.
Frequently asked questions
Why does only the last dashcam file refuse to play? Because it was the segment still being written when the camera stopped. Every earlier clip closed normally and got its index; that one didn't.
Can I recover dashcam footage after an accident? If the card wasn't overwritten afterwards, usually yes — the interrupted segment normally still contains the video data and needs its index rebuilt. Stop recording with that card first.
Should I keep the dashcam running after a crash? Not with the same card, if the footage matters. Loop recording will overwrite it. Swap cards or remove the card and store it.
Do I need a reference clip from the same dashcam? Often not for the picture. For the audio track, yes — and a dashcam card is full of healthy clips from the same camera, so this is easier here than almost anywhere else.
Does repairing reduce the video quality — will it still be usable as evidence? A proper index rebuild copies the original recorded data through without re-encoding, so the frames are unchanged. Keep the untouched original file as well; a repair tool worth using never modifies it.
The bottom line
The clip that won't play is the clip that was still being written — which is exactly why it's the one you needed. The footage is usually intact under a missing index. Get the card out of the camera before the loop reaches it, copy the file somewhere safe, and rebuild the index: on your phone with Video Repair, which shows you the recovered clip in full before charging anything, or on a desktop if that's where the card ended up. The full mechanism is in how to fix a corrupt MP4.
