Data Recovery Case File · Cameras, Drones & Cards · Two Images in Every File
A Preview Embedded in a Photograph Can Survive When the Photograph Does Not
Her enquiry contains a distinction most people would not think to report. A card where, "when I view the photos quickly on my camera they are all visible and completely fine, but when I go to view them normally it says unidentified image" — and nothing shows on a phone or computer. The two views read different parts of the same file, and the difference tells us exactly what survived.
| Media | Camera memory card reporting corruption — embedded preview images displaying in review mode, full images not opening in normal review or on any host |
| Reported situation | Memory card reported as corrupted · photographs visible in the camera's rapid review mode · photographs reported as unidentified when opened normally in the camera · card not displaying content on a phone · card not displaying content on a computer · images required |
| Fault class | Image files partially readable — embedded preview data intact with full image data unreadable or unreferenced; structure damage indicated by host-level inaccessibility |
| Equipment used | Preview visibility distinguished from full-image readability to locate the surviving data · card removed from use before assessment · imaged write-blocked before any scanning · embedded previews extracted as a guaranteed floor · full image data carved and reassembled where regions returned |
The decode: what a camera's two views actually read
What is inside a single photograph file: more than one image. Cameras embed a small preview alongside the full-resolution data, so that a photograph can be displayed instantly without decoding the whole thing.
Why the rapid review mode is fast: it reads only that preview. Scrolling through images in review displays the embedded previews rather than the photographs themselves, which is why it responds immediately.
What normal review does instead: decodes the full image. It reads the whole file and reconstructs the photograph at full resolution, which is a far larger operation touching far more of the card.
Why her observation locates the damage precisely: previews display and full images do not. The beginning of each file, where the preview sits, is readable — and the bulk of each file, where the photograph sits, is not.
Why unidentified image is the expected message for that: the camera read the file, could not decode the full image data, and declined it. It is a failure to interpret rather than a missing file.
What that suggests about the card: regional read failure rather than total loss. Some parts of the card return data and others do not, and the parts that do happen to include the file openings.
Why nothing appears on a phone or computer: those need the card's structures to list files at all, and the camera has its own more tolerant handling of its own layout. Host inaccessibility is a separate and additional finding pointing at damage to the directory as well.
Why the previews are worth extracting regardless of anything else: they are recoverable now and they are real images. They are small and heavily compressed, so they are not a substitute for the photographs — but they establish what was there and provide something if nothing better is achievable.
Why they also make the recovery verifiable: each preview corresponds to a full image. Extracting them produces a manifest of what should come back, against which any fuller recovery can be checked.
What must not happen: no further review in the camera, and no formatting when any device offers. Scrolling through previews is still reading a failing card, and the temptation to look is strongest when something is visible.
On the bench
Preview visibility was distinguished from full-image readability to locate the surviving data — cameras embedding a small preview alongside full-resolution data so review mode can display instantly, whereas normal review decodes the whole file. Previews displaying while full images fail places readable regions at the file openings and unreadable regions across the bulk. Embedded previews were extracted as a guaranteed floor, and full image data carved and reassembled where regions returned.
The outcome
Preview visibility distinguished from full-image readability, previews extracted as a floor, and full image data carved where regions returned. Free assessment, one fixed written figure including VAT; on cards where content has been deleted or overwritten, the figure is payable upfront. The decode: your two views read different parts of the same file. Review mode displays a small preview embedded at the start; normal viewing decodes the whole photograph — so the openings read and the bulk does not.
Photographs that appear in review and refuse to open
Stop scrolling through them in the camera — that's still reading a failing card, and the temptation to look is strongest when something is visible. What you've noticed is genuinely diagnostic: every photograph file contains a small embedded preview alongside the full-resolution data, and rapid review displays only the preview, while opening one properly decodes the whole file. So previews working and full images failing means the start of each file reads and the bulk doesn't. Those previews are worth extracting whatever else happens, both as a floor and as a manifest.
Stop reviewing them — call Manchester Data Recovery on 0161 871 0788; preview visibility distinguished from full-image readability, previews extracted as a floor, full image data carved where regions return.
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.