XMP Metadata Sidecar
Photo Sidecars & CameraXMP is a metadata framework; .xmp can be an image sidecar carrying descriptions, rights or editing settings, not pixels. Stored information depends on the producer/features and need not reproduce every edit alone.
- What it is used for
- Metadata and editing-setting interchange
- What the file contains
- Text
All sections, questions and sources
Content reviewed： · Editor：Kai
Opening steps
Choose your environment or purpose to see its steps.
Menu labels and support vary by app, OS and version. Preserve the original before making changes.
Troubleshooting by symptom
- Edits not applied: check image pairing, import/read settings and stored metadata scope.
- Different rendering elsewhere: verify application-specific setting support.
- Partial edits: check whether catalog/ACR or other companion information is required.
- Latest catalog edits absent in XMP: inspect write timing/status.
- Reading XMP reverts edits: disk values may be older; inspect the pre-change backup.
- Photo XMP rejected as a preset: distinguish preset serialization from image sidecars.
Image + XMP → rendered image
- Supply the image and required companions in the producing environment and inspect edits.
- Export JPEG/TIFF and review dimensions, color and retained public metadata.
- Inspect edits, ratings, keywords and appearance at the destination; retain source image/catalog backups.
Renaming cannot create an image; rendered pixels do not preserve equivalent editability, and cross-app settings have limits.
Sidecars versus presets
XMP supports multiple metadata uses, including image edits and presets; identify purpose from provenance and corresponding images.
Applications can differ in metadata/edit interpretation; compare appearance even when the file parses.
Source for these steps：Adobe · XMP Developer Center / Adobe · Save metadata to external sidecar files
Catalog-to-disk synchronization direction
Writing and reading move data in opposite directions; back up before old sidecar values can replace current edits.
Current Lightroom Classic edits may involve companions beyond XMP; inspect required files/catalog coverage for migration.
Source for these steps：Adobe · XMP Developer Center / Adobe · Save metadata to external sidecar files
Related-format differences
| Format | Main role | What to check |
|---|---|---|
| XMP | Metadata/presets | Identify purpose/matching image |
| RAW | Source image | Pixels/capture data |
| LRCAT | Photo catalog | Catalog state is separate |
Handling and security
Review location/author/description privacy and retain matching image companions/backups.
Questions and answers
Can XMP display a photo alone?
The original image is required.
Does it include every edit?
Some applications/features need other information.
Will another app render identical color?
Check its support and interpretation of the settings.
Can XMP alone recreate a RAW image?
Pixels reside in the source image; retain it together with its XMP.
Does XMP hold all Lightroom information?
Some catalog-specific information/edits require other storage; XMP is not a complete catalog replacement.
Format facts: name, steward and MIME type
- Formal name
- Extensible Metadata Platform
- Steward / specification
- Adobe
- MIME type
- Depends on the producer or server; an extension alone does not establish a MIME type.
Primary and official sources
- Official documentationXMP Developer Center
Official XMP metadata documentation.
Adobe · Link checked： - Software documentationSave metadata to external sidecar files
Explains XMP/ACR sidecar metadata.
Adobe · Link checked：