A missing preview does not automatically mean that a file is unrecoverable. The file may use a preview format or encoding that is not supported, or its contents may be incomplete. Check what the result represents, then export an appropriate candidate to another device and open it in a compatible application where possible.
Identify the result before judging it
Confirm the file type, reported size, source location, and result view. An empty directory, a zero-byte item, a generated signature result, and a named file with a plausible size are different starting points.
Compare alternative candidates for the same work. The familiar filename may come from a surviving record while a type-based result contains a more useful copy. Conversely, a result grouped by file type may be an embedded preview or a false positive: data that resembles a file of that type but is not actually one.
Keep a note of which candidate you are testing so that you do not repeat the same uncertain export under several names.
Check whether the expected presentation is supported
XRecovery supports previews for common pictures, documents, videos, and audio. It also supports contents-list previews for specified archive formats. Those are defined capabilities, not a promise that every format variant, codec, encrypted document, or archive member can be previewed correctly.
A RAW photograph can have a camera-specific variant. A video extension can contain different encoded streams. A document can depend on application features or credentials. Check the actual file and its intended application rather than reasoning only from the last letters of the filename.
An archive list is not the same as extracting every member successfully. If a list appears but a document inside cannot be opened, assess that member separately.
Compare with a known-good file where available
Use a healthy file of the same relevant type and encoding in its ordinary application. If the intended player cannot open the healthy example either, resolve that application compatibility question before declaring the recovered candidate damaged.
Do not modify the affected source merely to construct a comparison. Use a safe existing copy or an independent working location. Comparing two different camera variants or encodings may not answer the compatibility question you intended to test.
Export a candidate and validate the contents
Where appropriate, recover the selected candidate to a separate physical device. Open the exported copy with the software that normally handles that format. Preserve the unmodified recovered version before attempting conversions or repairs.
Check the full content relevant to your task. A document may open but lose later pages; a photograph may show a thumbnail while its full image is damaged; a recording may begin correctly and then stop. Conversely, an application-level open can reveal usable content that the recovery preview did not present.
If export fails, record that as an export problem rather than a preview result. Check the destination identity, available space, and any exact error message before changing the source.
If the contents are damaged
XRecovery supports file repair for listed formats, including specified pictures, documents, video, and audio. Repair is a separate operation and depends on the content that remains. Work on a copy and compare the actual repaired result; an output file is not by itself proof that all original material was restored.
If the missing content was overwritten, cleared, or never present in the candidate, changing its extension cannot supply it. Retain alternative scan results and known copies for comparison rather than repeatedly renaming the same bytes.
Describe the right question to support
Record the application version, file type/encoding if known, size, source/result view, preview message, and whether the exported file opens elsewhere. A small authorized non-sensitive sample may help when support requests one, but do not share private documents by default.
The useful distinction is whether the issue concerns preview compatibility, incomplete contents, export, or the application used to validate the output. Each has a different next step; “no preview” alone does not decide all four.
For the next step, see XRecovery 4.0 Support: Find the Right Workflow for Your Next Step.