Data Recovery Case File · Cameras, Drones & Cards · The Restore, Then the Overwrite
Camera Restore Wiped a 45-Minute 4K Clip
This enquiry came from a production crew and documents a sequence that costs professionals footage every week. Recording 4K on a full-frame camera to a 128GB card, they shot a long clip and then: "camera battery was low, so we cut the clip with 17 minutes remaining. When we cut, the camera said the clip hadn't been captured and media needed restoring to rescue. I executed the restore, but after, the card was showing it was empty as recording time had jumped back up to about 1 hour 6 minutes — which is what it shows when empty. We continued to record the interview. At the end of the day the original clip wasn't there." Two separate events happened there, and only the second one really hurt. The restore made the clip invisible. Continuing to shoot on the same card is what made parts of it gone — and the distinction is the whole case.
| Media | 128GB professional video card — approximately 45 minutes of 4K 10-bit footage recorded, interrupted before finalisation; camera restore function executed; further recording performed on the same card afterwards |
| Reported situation | Recording cut short by low battery · camera reported the clip uncaptured and offered media restore · restore accepted; card subsequently reported as empty · shooting continued on the same card for the remainder of the day |
| Fault class | Unfinalised clip with management structures rebuilt by the camera, followed by partial overwrite from subsequent recording |
| Equipment used | Card imaged write-blocked (DeepSpar USB Stabilizer 10Gb) · management structures analysed on the image · frame-level carving of the codec stream with overwritten regions mapped · surviving footage rebuilt into a playable container and validated by playback |
The decode: what the restore did, and what shooting on cost
Why the clip was not captured: a camera writes video as a continuous stream of frames and only completes the file when recording stops properly — writing the index that says where each frame begins, the duration, and how audio aligns. Cutting a clip while the battery is failing can interrupt that finalisation, leaving the frames on the card with no valid entry describing them. That is why the camera reported the clip as uncaptured: from its management database's point of view, no completed file existed. The footage, at that moment, was entirely present.
What the restore function actually does: and this is the part worth every professional knowing. A camera's media restore rebuilds the card's management database — the index files that catalogue clips, durations and thumbnails — by scanning for entries it recognises as complete. It is designed to fix a card whose catalogue has become inconsistent. What it does not do is rescue an unfinalised clip: finding no valid completed entry for those 45 minutes, it rebuilt the catalogue without them and updated the free-space accounting accordingly. Hence the recording time jumping back to an empty card's figure. Nothing was erased at that point — the space was simply marked available again.
What continuing to shoot cost: the painful part, said plainly. With the space marked free, every subsequent take was written into it. A 45-minute 4K 10-bit clip is a very large object — tens of gigabytes — so an afternoon of interview footage will have landed on some of it and not all. What is overwritten is permanently gone; what was not touched is still there, frame by frame. The recovery therefore becomes a mapping exercise: identify which regions of the original stream survive, and rebuild a playable file from them.
What can honestly be expected: partial recovery, with the surviving portions genuinely usable. Video codecs of this type are structured so that a stream can be reassembled from intact segments, and a rebuilt clip typically plays cleanly through the surviving passages with gaps where later footage landed. For a 45-minute interview that may mean substantial usable material rather than the whole take, and it is reported honestly as a map of what survives rather than as a percentage.
The production lesson: when a camera reports any problem with a card — a failed capture, an offer to restore, a warning of any kind — that card comes out and a fresh one goes in. The restore is not a rescue tool and shooting on afterwards is what converts an invisible clip into a lost one.
On the bench
The card was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb, freezing the day's damage exactly as it stood. On the image, the rebuilt management structures were analysed to establish what the restore had discarded, and the card's raw contents were then carved at frame level for the codec in use — every surviving group of frames from the original clip located and its position in the stream established, with the regions occupied by the later interview footage mapped as losses rather than guessed at. The surviving passages were rebuilt into a playable container with a reconstructed index and validated by playing them through end to end, and the result was delivered alongside a plain map of what had survived and what the afternoon's shooting had taken.
The outcome
The surviving footage carved at frame level, rebuilt into a playable file and validated, with the overwritten passages identified explicitly. Free assessment, one fixed written figure including VAT, no recovery, no fee. The sequence, documented for every production: a clip interrupted before finalisation is present but uncatalogued, because cameras write the index only when recording stops properly; the camera's restore function rebuilds the catalogue from complete entries and will therefore discard an unfinalised clip and mark its space free — it is not a rescue tool; and continuing to shoot on that card writes into exactly that space, which is the step that turns a recoverable clip into a partially destroyed one. When a card reports a problem, swap it out and keep it.
Camera reporting a failed capture or offering to restore media
Take the card out of the camera and put a fresh one in — before doing anything else, including accepting the restore. An interrupted clip is usually still entirely present on the card; it simply has no index describing it, because cameras write that index only when recording stops cleanly. The restore function rebuilds the card's catalogue from clips it recognises as complete, so it will quietly leave out your unfinalised one and mark its space as free. That alone doesn't destroy anything. What destroys it is the next thing you record, which is written straight into that freed space. So if the restore has already run and the card looks empty, stop shooting on it immediately — everything not yet overwritten is recoverable, and a long 4K take is large enough that a partial overwrite usually leaves substantial usable footage.
Stop shooting on that card — call Leeds Data Recovery on 0113 322 3083; imaged write-blocked, the stream carved frame by frame, surviving passages rebuilt into a playable file and checked by playback.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.