
Export each new Apple Photos selection into a separate temporary export folder, compare it with the previous delivery, and add only the files you have identified. Do not use a blanket Skip decision merely because Finder reports the same name. A camera filename identifies a name in that folder; it does not prove that two files contain the same photograph.
Before the next export
- Keep a record of which Photos selection produced each delivered batch.
- Choose originals or rendered edits deliberately.
- Resolve filename conflicts before merging folders.
Define what the editing application needs
A Lightroom input, a viewing JPEG, and a finished video are different deliverables. Use the export route that matches the recipient's task. Apple's Photos export guide describes selected-format exports and Export Unmodified Original separately. It also documents optional IPTC sidecars and explains that an original Live Photo export produces a still file and a video file.
Choose the route in Photos before exporting:
- Select the items for this batch. To send the visible edited version, choose File > Export > Export [number] Photos. Set the file type and any format-specific options in that dialog.
- To send camera originals instead, choose File > Export > Export Unmodified Original. Review the optional IPTC XMP choice if the recipient needs that metadata.
- Choose the file naming option and export into the new empty folder. Check what was written before copying it into an existing archive.
These are two separate export routes. They do not create a record of everything you have already delivered.
Write the intended route in your batch note. For example: original captures for further editing, rendered copies for a client selection, or both in separate folders. This is your delivery convention, not a Photos setting. Keeping those roles apart prevents a later rendered export from being mistaken for a second original.
If the source is not fully available on the Mac, establish that first. The iCloud original preparation guide covers that separate problem. A repeatable export system cannot compensate for an incomplete input.
Give each export its own temporary folder
Create a new empty folder for the selection you are exporting now. Record its date, purpose, source selection, export route, and intended recipient. Use an album or another selection you can identify again; do not rely on remembering which thumbnails you highlighted last week.
Choose the naming option deliberately. A sequential export can make a handoff readable, but numbering a second batch from the beginning can create fresh collisions. Retain a mapping to the source name whenever you rename files. After export, leave the temporary folder intact until the receiving application has accepted it.
This approach uses extra temporary space. If the drive cannot hold the current batch, reduce the batch size or arrange another destination. Do not solve a storage shortage by deleting the only source before checking the handoff.
Compare files rather than counting thumbnails
Compare the exported files with the selected media types. A photo with a companion video or sidecar can produce more than one file, so a simple file count need not equal the number of selected library items. Keep related assets together through copying and import.
For a same-name conflict, inspect file type, dimensions, visible content, and relevant capture metadata. A complete byte-for-byte comparison can confirm that two files contain the same bytes. A different result does not prove that they show different captures: changing an export option or embedded metadata can change a file. A matching name, size, or thumbnail alone is not enough to confirm a duplicate. Preserve both unresolved files under distinct names while you investigate.
| Conflict | Safe next decision |
|---|---|
| Same name, different photographs | Keep both and record the new naming map |
| Same photograph, different edit | Label the rendition's role |
| Identical bytes | Record the duplicate before omitting a copy |
| Missing companion asset | Treat that item as incomplete |
Work through a second export
This is a hypothetical handoff, not a test report. In batch trip-01, you send an unmodified IMG_0101.HEIC to an editor. The editor confirms it opens and accepts that batch. Record the source selection and the delivered filename before starting another export.
A week later, the next selection contains that same capture, a new IMG_0102.HEIC, and a revised JPEG of the first photograph. Export them into a new folder named trip-02-review. Do not merge that folder straight into trip-01.
| Item in the new folder | Check against the accepted batch | Delivery decision |
|---|---|---|
| First original appears again | Confirm the complete file matches the accepted original | Mark as already delivered; keep the source |
| New capture | Confirm it was not in the recorded first selection | Add to the next handoff |
| Revised first photograph | Check the new appearance and recipient's requested role | Deliver as a new edited version with a distinct name |
| Same name but uncertain identity | Inspect it without replacing either file | Keep in an unresolved folder until identified |
Use this plain-text record for each accepted item. These are fields you maintain outside Photos, not built-in automatic export tracking:
- Batch:
trip-02; source selection: the named album or explicitly recorded items. - Route: unmodified original or edited export; source filename:
IMG_0102.HEIC. - Delivered filename: the actual name in the handoff folder.
- Companion: matching movie/XMP filename, or none expected for this item.
- Status: new, revised, already delivered, or unresolved.
- Acceptance: who checked the receiving app, when they checked it, and the accepted folder.
For the following batch, start with this record and explicitly select known new or revised items. If you cannot tell whether an item was delivered, export it separately and compare it. Do not assume a recently edited view, a filename, or Finder's Skip command is a complete export history.
Check the recipient and retain the record
Import a small reconciled batch into the actual editing application. Check that the intended files, dates, and companion assets are usable there. Then record the accepted batch and its destination. Your next export starts with this record, not with a guess based on Finder's conflict dialog.
This procedure does not back up the Photos library or retain every application-specific edit. See the separate explanation of sync versus a family backup, and preserve the required RAW editing data when that is part of the job.
The workflow above is a proposed reconciliation method based on the documented export routes. It is not a report that Apple Photos automatically detects everything you previously exported.
Related tasks
- Why Is My iCloud Photo Small or Unavailable When I Upload It to an AI Editor?
- Does Deleting a Phone Photo Also Delete the iCloud Original?
- Why Does My RAW Photo Lose Its Edits on Another Computer?
Sources and scope
- Export photos, videos, slideshows and memories on Mac: Apple documents exported formats, file naming, original export, optional IPTC XMP, and the still/video pair produced by an unmodified Live Photo export. It does not document an automatic incremental-export ledger.
- Workflow for saving iPhone photos and videos to Mac for editing in Lightroom Classic or Final Cut Pro: One public user asks about repeated exports, duplicate external files, new folders and Finder Skip. Used as a single demand example, not as software authority or search-frequency evidence. The captured page provides only relative posting time; no absolute publication date is asserted.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance, not a claim of hands-on testing or independent review. Report a correction.
Cover: Pignatta / Pixabay, Content License. The city photograph is an illustrative source asset; it does not show this application or a test result.