Photos Lost During Import: Compare the Card and Destination First

Compare the source card, import settings, and destination files to find missing photos, preserve surviving copies, and identify genuine recovery needs.
XAppSet Team
Published on November 14, 2026

When photographs disappear during import, compare the source card with the destination before running recovery software. Some files may never have been copied, others may be in a different folder, and an interrupted transfer may leave a partial destination file. Stop any deletion or cleanup process and preserve both locations until you know which usable copies remain.

SD and microSD cards beside a USB reader and camera

Freeze the import without erasing its evidence

Do not format the card because the import application reported completion. Do not repeat an operation that deletes originals after transfer. If a sync client is changing the affected destination, pause it while you preserve the available copies and record its status.

Note the import application and version, the destination you selected, whether files were renamed, and the error or interruption. Record any option that removes source files or skips suspected duplicates. These settings help explain the result; the name of the transfer method alone does not establish what happened.

Use a new folder on a healthy device for further copies. Leave the existing destination files in place so you can distinguish the first attempt from a later copy. If the source card is disconnecting or reporting read errors, stop repeating the transfer and assess the medium first.

Reconcile individual files rather than assuming that either the source card or the import counter tells the whole story.

Compare one missing photograph at a time

Choose several important missing frames and inspect the card and destination directly in the file browser. Look beyond the application’s current collection. Check dated subfolders, renamed files, another import location, and the paired JPEG or RAW file.

Source card Destination Next action
Original opens File missing Copy the original into a new destination folder
Original opens Copy is smaller or damaged Preserve both, then make and verify a fresh copy
File absent Destination copy opens completely Protect and back up that copy
File absent or unreadable Destination missing or damaged Investigate backups and an appropriate recovery route

Compare dimensions, file size, and actual content. Matching names and file counts are useful bookkeeping, but they do not prove that all the copied bytes are correct. A folder can contain the expected number of files while one is truncated or belongs to an earlier session.

For unchanged file copies, a checksum comparison can establish whether two readable files have identical bytes. It does not tell you whether the source was already damaged. Renaming changes the filename or path, so you may need another way to match corresponding files; their content hashes can still be compared. Converting RAW to DNG or changing embedded metadata can change the file’s bytes, so those operations require a comparison appropriate to the transformed files.

Check whether the importer deliberately skipped files

An import application can omit a photograph without deleting it. Inspect the source file and the existing catalog entry before turning off duplicate handling or importing the entire card again.

Lightroom Classic, for example, uses the original filename, EXIF capture date and time, and file size to identify suspected duplicates. Adobe documents the Don’t Import Suspected Duplicates option in its import settings. This is more specific than assuming that any reused filename is always skipped.

Also distinguish copying from catalog organization. Adobe’s card-import tutorial explains that Lightroom Classic offers Copy for camera-card imports and does not offer Add or Move for that source. Do not apply the behavior of an operating-system cut-and-paste operation to every import application.

If the original is present, copy it into a separate comparison folder and open it there. That establishes whether there is a content problem before you reorganize the catalog or remove any existing entry.

Retry a copy only from a suitable source

For a stable card with readable originals, copy the missing files into a fresh destination folder. Check available destination space and use a compatible reader and reliable connection. Avoid a second transfer that silently replaces the first attempt’s files.

After copying, open important JPEGs at full resolution and decode RAW files with a compatible application. If a particular source file consistently reports a read error, note it rather than repeatedly retrying the entire card. The issue may require a different acquisition approach.

Wireless transfer needs the same source-and-destination comparison. Do not assume every camera or companion app always keeps the original, transfers full resolution, or uses the same completion rules. Read the settings and documentation for the actual model and application, then verify the copies you have.

When the original is genuinely missing

Check earlier imports, a second recording card, backup drives, and any service holding original uploads. A catalog thumbnail or an online preview may help identify the photograph without providing the original file.

If the card is readable and the original is absent, a recovery scan may locate remaining file data. Preserve the card, use an appropriate image-first workflow when suitable, and save results to another physical device. XRecovery can scan readable disk media for lost files and preview supported types; results still depend on the data the source can return.

Do not automatically scan the card in every case. If an original was removed from a local destination after a successful import, the destination and its backups may be relevant too. Ordinary cross-drive moves are a separate investigation from a camera import. Record the event and preserve the affected storage before selecting a recovery source.

For cloud changes, check the service’s own deleted-items and version-history facilities. Their availability depends on the provider, account, and event. There is no single retention period that applies to every service, and a cloud placeholder is not proof that a local original exists.

Finish with a reconciled set

Make a list of the expected photographs and identify where the best usable copy now lives. Mark lower-resolution substitutes and damaged files separately. Verify the important files, make an independent backup, and keep the source until unresolved gaps have been considered.

Only then should you remove duplicate imports or prepare the card for another shoot. The JPEG verification workflow and RAW verification workflow help establish what each surviving copy actually contains.

If an XRecovery scan does not show the imported photos, check the selected source, result view and filters.

Camera photo and video recovery guide

Privacy Overview
XAppSet

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful. Privacy Policy

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.