How to Avoid Losing Photos Whose Filenames Differ Only by Capitalization
By ImgHeal · Updated
An archive can contain both scan.jpg and SCAN.jpg as different files on one disk. Another destination may treat those names as the same, creating a collision even though the photographs are different.
Explore this topic: Troubleshoot photo files

Identify the destination's naming rules
Check the disk or service documentation before a large migration. Apple distinguishes case-sensitive APFS from ordinary APFS, and other destinations have their own rules. A computer brand alone does not establish how every attached volume behaves. Look for actual pairs of files in the source that differ only by capitalization, including parent folders whose names differ in the same way.
Compare the colliding files
Open each candidate and record its full path, dimensions, and content. They may be duplicate exports, different scans, or unrelated images that reused a short camera filename. Do not choose a winner from capitalization or modification time alone. Keep both original paths in an inventory so the relationship can be understood even if you need a different naming arrangement on the destination.
Rename staging copies deliberately
Make a separate staging copy and add a meaningful identifier or sequence to the colliding names. Preserve the extension and keep source originals unchanged. If two parent folders collide, rename those staging folders too; fixing only the image basenames may not solve the transfer. Record the old-to-new mapping in a simple text or spreadsheet inventory that travels with the copied archive.
Review every collision prompt
Copy the prepared set without accepting a blanket replace option. Compare expected counts and inspect the known collision examples on the destination. A successful copy dialog is not proof that both members survived if replacement was allowed. Update any working-project links affected by staging names, and retain the source inventory so a later researcher can locate the original file regardless of the destination's naming limitations.
Check before you finish
- Check both file names and parent-folder names.
- Rename only staged copies and retain a mapping.
- Verify both members of each collision after transfer.
Sources and further reading
- Apple: File system formatsDistinguishes case-sensitive volumes from other disk formats.
- Microsoft: File names and sync limitationsDocuments duplicate-name conflicts, unsupported paths, and concurrent offline changes.
Questions about this restoration task
Are names that differ only by upper and lower case always separate files?
That depends on the volume or service. Check its actual naming rules and protect both items before copying to a destination that treats them as equivalent.
Continue with a related guide
Try a restoration on a copy of your photo
Keep the original scan. Upload a separate digital copy, review ImgHeal’s generated result, and decide whether it suits your needs.
Open ImgHeal