Call us — 0191 406 1051
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →

Data Recovery Case File · Cameras, Drones & Cards · The Best Route Is the One You Regret

Three Safety Nets, Removed in Order

Her enquiry is unusually clear-eyed and lists its own failures. Transferring photographs and video from a camera to a laptop and uploading to cloud storage: "I made 3 mistakes. 1) I accidentally moved the files from the laptop folder to the cloud instead of copying the originals. 2) I deleted the files off the SD card before confirming successful upload. 3) Upon checking the cloud, 6 files, all video, are not readable — either the file types are unsupported, the file extension is incorrect, or the file is corrupt." Three steps, each removing a copy, in the order that leaves nothing. But the second mistake is also the best remaining route, because a card that was cleared is not a card that was erased.

MediaCamera SD card cleared after transfer, laptop folder emptied by a move operation, and cloud copies partially unreadable — six video files affected
Reported situationFiles moved rather than copied from the laptop to cloud storage, removing the local originals · card cleared before upload was confirmed · six video files subsequently found unreadable in the cloud · card retained
Fault classIncomplete upload with local and card copies removed — card content deleted but not overwritten; recovery by carving from the card
Equipment usedCard removed from use immediately · imaged write-blocked (DeepSpar USB Stabilizer 10Gb) · cloud and local deleted-items areas eliminated first · format-aware carving for video containers · footage validated by playback

The decode: why each step cost, and why the card saves it

What a move to a synced folder actually does: the first mistake, and it is a genuinely easy one. Copying leaves the original; moving removes it once the transfer is reported complete. The problem is that a sync client reports completion when it has taken the file into its own management — not necessarily when the file has fully uploaded and been verified at the far end. So a move can delete a local original while the upload is still in progress, or has stalled, or has failed. That is the mechanism behind her third mistake as well.

What the six unreadable files are: almost certainly incomplete uploads. A video file that stopped partway through transfer exists in the listing with a name and a size and cannot be decoded, which produces exactly the error she describes — unsupported type, wrong extension, or corrupt, which is a service saying this is not a valid file without knowing why. Video files are large, so they are the ones that fail to complete.

Why the card is the answer, and this is the hopeful part: deleting files from a card does not erase them. It writes an updated index marking the space as available; the video itself remains physically present until something records over it. She stopped using the card, which means the material is very likely still there in full. Camera video carves exceptionally well — the files are large, written in continuous passes, and carry distinctive container headers, so clips are identified by their own structure and rebuilt whole without needing any index at all.

The two free checks first: the cloud service's own deleted items area, which retains removed files for a period measured in weeks, and the laptop's trash, since a move that failed partway may have left originals behind. Both take minutes and either may return complete files.

The instruction that matters: the card must not go back in the camera. It is now the only complete copy of that material, and a camera with a card in it will write to it.

The habit worth changing, said gently: copy rather than move, and clear the card only after opening files at the destination. Not after a progress bar completes, not after a sync client reports success — after actually playing a video from where it ended up. She has already worked this out herself; it is worth stating because the sequence she describes is one of the most common ways people lose material they had successfully transferred.

On the bench

The card was removed from use immediately, since it had become the only complete copy of the material and a camera with a card in it writes to it. The cloud and local deleted-items areas were eliminated first, as either may hold complete files and both are free. The card was then imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb, and format-aware carving run for video containers — rebuilding clips from their own headers rather than from the index the deletion replaced. Footage was validated by playback.

The outcome

The free routes checked first, the card imaged write-blocked and the video carved and validated by playback. Recovery of deleted or overwritten data from memory cards and USB sticks is charged at a flat figure, payable upfront. The decode, for anyone whose transfer went wrong at every stage: the card you cleared is the best route back, because deleting from a card writes an updated index and marks the space available rather than erasing anything — so the footage is physically present until something records over it, and camera video carves exceptionally well. Check the cloud's deleted-items area and your trash first, both free. And keep the card out of the camera, since it is now the only complete copy.

Cleared the card before checking the upload worked

Keep that card out of the camera — it's now your best route back, not your worst mistake. Deleting files from a card doesn't erase them; it writes an updated index marking the space as free, so your footage is still physically there until something records over it. Camera video carves particularly well too, because the files are large, written continuously and distinctively headed, so clips can be rebuilt from their own structure without any index. First, though, check two free places: the cloud service's deleted-items area, which keeps removed files for weeks, and your computer's trash. As for what went wrong — sync clients report a transfer complete when they've taken the file into their own management, not when it's fully uploaded and verified. That's why moving rather than copying is risky, and why large video files are the ones that fail.

Deleted the card before the upload finished?
Keep it out of the camera — call Newcastle Data Recovery on 0191 406 1051; free routes checked first, card imaged write-blocked, video carved by container signature and played through.
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.