Why Did My Apple Photos Export Create an XMP File Beside the Original Product Photograph?

Distinguish the original image from the metadata sidecar

Apple's Photos export documentation includes an Export IPTC as XMP option for unmodified originals. This separates exported IPTC information from the image data.

The image file remains the photographic source. The XMP companion is a metadata representation, not another picture or a higher-resolution version.

Start by identifying the export command and whether the option was selected. Inspect the source photograph, its descriptive fields in Photos and the files produced by export.

Do not assume that every XMP file contains the same fields, that every receiving application automatically reads it, or that the sidecar contains the complete Photos editing history. Its documented role here is IPTC metadata export.

Decide which information must travel

For a merchant catalog, useful descriptive fields may include a product description, approved keywords or other authorized metadata. These can help the recipient identify a source, but they do not prove that the photograph depicts the correct SKU.

Record which metadata fields are required by the recipient. Preserve the XMP companion with its corresponding original when those fields matter.

If the recipient needs only a rendered product image, the delivery requirements may differ. Do not indiscriminately remove the sidecar from the source archive simply because the final storefront does not display it.

Review private fields separately from approved public attribution. A metadata handoff should not expose unnecessary internal project names or sensitive location information.

Hypothetical catalog source delivery

Hypothetical illustration—not an executed Photos export: a merchant exports an unmodified photograph of a green ceramic mug. The Photos library record contains an approved description and keywords identifying the product family.

With Export IPTC as XMP selected, the proposed handoff contains Mug-01's image and a companion XMP file. The receiving editor is expected to verify the association and inspect the descriptive fields using a compatible application.

If the image opens correctly but the description is missing from the editor's interface, that does not immediately prove the sidecar was lost. Check whether the companion arrived, whether its association is intact and whether the receiving application supports the relevant fields.

The worksheet records the intended investigation, not a completed metadata inspection.

Verify the metadata after handoff

Keep a source identifier linking the photograph and XMP companion. Open the actual received image and inspect the metadata using a tool capable of reading the exported representation.

If the companion is missing, return to the original export and transfer process. If the companion exists but the receiving application ignores it, investigate application support rather than changing the photographic pixels.

Do not treat a matching keyword as sufficient proof of SKU identity. Compare the visible item with the authoritative product record.

When creating a public derivative, review the metadata on that exact output separately. The presence of an XMP sidecar beside an archival RAW does not guarantee that a later JPEG or CDN rendition contains those fields.

Approve the handoff when the original image, intended descriptive metadata and recipient interpretation have each been verified.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• Apple Photos User Guide — Export photos, videos, slideshows, and memories on Mac: Documents Export IPTC as XMP when exporting unmodified originals.