What Is an XMP Sidecar File?
An XMP (Extensible Metadata Platform) sidecar file is a small text file (usually 1-5 KB) that sits next to your photo and contains metadata about it. Instead of writing keywords and descriptions directly into your RAW file, the metadata lives in a separate .xmp file with the same name.
For example:
DSC_4521.NEF ← Your original RAW file (untouched)
DSC_4521.xmp ← Sidecar with keywords, ratings, edits
When Lightroom, Capture One, or any XMP-compatible software opens DSC_4521.NEF, it automatically reads DSC_4521.xmp and applies the stored metadata — keywords, star ratings, color labels, develop settings, and more.
Why XMP Sidecars Matter for Race Photographers
Non-Destructive Workflow
Your original RAW file is never modified. This is critical for archival integrity — you can always return to the pristine original, and you can delete/recreate the XMP sidecar without any risk to the photo data.
Multiple Metadata Sources
Different tools can read and write to the same XMP sidecar. RaceTagger writes race number keywords, Lightroom adds develop settings and star ratings, and everything coexists in one file.
Portable Metadata
XMP sidecars travel with your photos. Copy the NEF + XMP together to a backup drive, and the metadata comes along. Move to a different computer, and Lightroom reads the sidecar automatically.
Safe for AI Processing
When RaceTagger processes your photos and writes results as XMP sidecars, your RAW files are completely untouched. If you don't like the results, simply delete the XMP files and start over. Zero risk.
XMP vs EXIF vs IPTC: Clearing the Confusion
These three terms overlap and confuse many photographers. Here's the simple version:
EXIF — Technical camera data (shutter speed, aperture, ISO). Written by your camera. Embedded in the file. You generally don't edit this.
IPTC — Content description (keywords, caption, credit, copyright). Written by you or your software. Can be embedded in the file or stored in XMP.
XMP — Adobe's metadata container format. Can hold IPTC fields, Lightroom develop settings, star ratings, color labels, and custom metadata. Can be embedded in the file OR stored as a separate sidecar.
The practical takeaway: XMP sidecars can contain your IPTC keywords (like race number tags) without modifying the original photo file. It's a container format, not a competing standard.
How RaceTagger Uses XMP Sidecars
When you choose XMP sidecar mode in RaceTagger:
- AI analysis runs on your photos (using embedded JPEG previews from RAW files)
- Results are matched against your CSV participant database
- XMP sidecar files are created next to each photo
- Each sidecar contains: structured keywords (numero_51, pilota_name, team_name, categoria), a formatted description, and the RaceTagger analysis results
Your RAW files remain completely untouched. The sidecars are tiny text files that add negligible storage overhead.
XMP Sidecars in Lightroom Classic
Lightroom Classic has a specific relationship with XMP sidecars:
Reading sidecars on import: When you import a folder, Lightroom reads any existing XMP sidecars automatically. RaceTagger keywords appear in your Library immediately.
Writing sidecars from Lightroom: By default, Lightroom stores metadata in its catalog database, not in XMP files. To write XMP sidecars: Catalog Settings → Metadata → check "Automatically write changes into XMP."
Updating after RaceTagger: If photos are already in your Lightroom catalog and you run RaceTagger afterward, use Metadata → Read Metadata from Files to refresh the catalog with the new XMP data.
Conflict handling: If both Lightroom's catalog and the XMP sidecar contain metadata, Lightroom asks which to keep. Generally, choose "Import Settings from Disk" to accept the RaceTagger keywords.
XMP Sidecars in Capture One
Capture One also reads XMP sidecars, though the integration differs slightly:
- Capture One reads XMP keyword data on import
- Develop settings from XMP are partially compatible (basic exposure, not advanced edits)
- Keywords and IPTC data transfer reliably
When to Use XMP Sidecars vs Direct EXIF Writing
| Scenario | Recommended | Why |
|---|---|---|
| Archival workflows | XMP sidecar | Original RAW untouched |
| Quick delivery workflows | Direct EXIF | One file to manage, not two |
| Testing/experimenting | XMP sidecar | Delete sidecars to start fresh |
| Photos already in Lightroom catalog | XMP sidecar | Less risk of catalog conflicts |
| Sharing files with other photographers | Direct EXIF | Metadata travels in single file |
If unsure: Start with XMP sidecar mode. It's non-destructive, reversible, and safe. You can always switch to direct EXIF writing once you're confident in the results.
FAQ
Do XMP sidecar files increase storage requirements significantly?
No. Each XMP sidecar is typically 1-5 KB. For 10,000 photos, that's about 10-50 MB of additional storage — negligible compared to the RAW files themselves (which might total 200-500 GB).
What happens if I move a RAW file without its XMP sidecar?
The metadata in the sidecar is lost for that file. Always move RAW files and their XMP sidecars together. Most file managers handle this correctly if the files share the same base name.
Can I edit XMP sidecar files manually?
Yes — they're plain XML text files. However, editing them manually is error-prone and unnecessary. Use your photo software or RaceTagger to write them correctly.
Do XMP sidecars work with JPEG files too?
Yes, though for JPEG files it's more common to embed metadata directly since JPEG is already a "processed" format. XMP sidecars work with any image format.
Try non-destructive AI tagging. Download RaceTagger free → — XMP sidecar mode writes race number keywords without touching your RAW files. 500 tokens on signup + 100 free analyses every month.