
Apple Photos lets you choose an export naming method, including the titles assigned in Photos, the filenames or a sequential scheme. If the recipient expects camera filenames but the export uses titles, the images can be correct while their handoff identifiers differ. Apple's export guide describes those naming choices separately from optional subfolder organization.
Key Takeaways
- Agree which identifier the recipient will use.
- Inspect the export naming option before a large handoff.
- Keep a mapping when a new naming scheme is intentional.
Identify the approval sheet's reference
For a proposed portrait selection, a client may approve images using camera filenames printed below contact-sheet thumbnails. A gallery title such as ‘Office portrait’ is a description, not necessarily that identifier. Determine what the recipient means when referring to a selected image.
Keep the approved list and source selection together. Do not infer an image match from a similar thumbnail when multiple frames look alike. A file can depict the same pose while being a different approved take.
Choose the output names deliberately
Inspect the available naming choices for the intended Photos export route. If the recipient's workflow depends on existing filenames, choose the corresponding naming method and verify a candidate export. If a sequential scheme is preferred, define its prefix and maintain the connection to the source selection.
Do not assume that putting images in a different subfolder resolves an identifier mismatch. Folder organization and individual file naming are separate parts of the export contract. Likewise, a name on the outgoing file is not evidence that the source asset has been renamed within the retained library.
Match the delivered files to the selected images
A proposed acceptance pass checks a small candidate against the approval sheet before the complete export. Inspect both the image content and the chosen output name. For an intentional rename, create a reliable correspondence list rather than asking the client to reconstruct it from order alone.
Repeat the match check on the actual delivery folder, especially if files were renamed or reorganized after export. This article does not establish how every version handles duplicate names or collisions. Keep those cases subject to actual verification. Accept the handoff when the recipient can unambiguously connect each delivered image with the approved selection and the naming method is documented.
Rehearse a three-file identifier map
Use a deliberately small hypothetical set before releasing a renamed portrait collection:
| Retained source identifier | Assigned Photos title | Intended sequential delivery name |
|---|---|---|
| IMG_4101.JPG | Portrait left | Client-A-001.jpg |
| IMG_4102.JPG | Portrait center | Client-A-002.jpg |
| IMG_4103.JPG | Portrait right | Client-A-003.jpg |
These are planning names, not observed Photos outputs. Record the actual exported names in a fourth column after the trial; extension case, numbering details and collisions remain subject to the selected route and version. Match each output to its visible portrait and approved source, not just the row number. If the current interface cannot generate the intended sequential scheme, document the supported scheme or use a separately reviewed renaming step.
Check original-versus-rendered export choice before deciding what the filename identifies. Record the rendering settings separately using the previous-export versus preset distinction; a matched name does not prove matched processing. Retain the source images following the catalog-backup coverage check, so an unsuccessful naming trial does not become the only copy of the selection.
Related tasks
- How Do I Choose the RAW Original in a Photos RAW and JPEG Pair?
- Why Did Export With Previous Use My Last Test Settings?
- Does a Lightroom Classic Catalog Backup Include My Original Photos?
Sources and scope
- Export photos, videos, slideshows and memories on Mac, Apple Support: Photos export naming can use assigned titles, filenames or a sequential scheme, with separate subfolder choices.
Based on Apple's official export-option extract checked October 31, 2026. The source later returned a rate limit; no batch export or collision behavior was tested.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.