How XMP and sidecars work in photo archives
XMP is a flexible metadata format that can be embedded in media files or stored beside them as sidecar files. In migrations, sidecars often hold information that the media file does not contain.
Microsoft Store will be the recommended path when the link is available. The classic installer remains available from the site.
Unsigned .exe noticeThe .exe installer is not signed yet. Windows or the browser may show warnings during download or installation. To avoid those messages, use Microsoft Store once the link is available.
When this guide helps
This matters in professional photo tools, cloud exports and workflows where descriptions or edits live outside the original file.
If sidecars are separated from media, important context can disappear from the destination library.
What usually goes wrong
The most expensive mistakes happen when an entire batch is changed before the source metadata is understood. In large libraries, one wrong decision multiplies quickly.
- Deleting sidecars as if they were clutter.
- Renaming media without keeping sidecar relationships.
- Applying sidecar data to the wrong duplicate.
- Ignoring embedded metadata conflicts.
Recommended safe method
The most reliable path is to work from a sample, keep a backup and record each exception. That protects the archive and makes the result easier to explain later.
- Keep sidecars in the same folder tree as media.
- Match sidecars to files carefully.
- Apply metadata on a sample.
- Review unmatched files and conflicts.
How MetaVault Studio fits
MetaVault Studio supports sidecar-aware workflows so XMP and JSON metadata can be part of a controlled recovery process.
The focus is local processing: your photos and videos are not automatically sent to a server. The site and server handle license, purchase and support only when those flows are used.
Checklist before processing everything
- Do sidecar names match media names?
- Which fields are in XMP?
- Were conflicts resolved deliberately?
- Does the target app read the applied metadata?
How this appears in the MetaVault Studio workflow
The app is designed to import a folder, apply or extract metadata, track progress and review results through a report. That turns metadata repair into a verifiable process.
Transparency and limits
Not every lost metadata field can be reconstructed. When there is no reliable source, the best result is to separate the case for review instead of inventing information. Google, Microsoft, Apple, ExifTool and other names mentioned here belong to their respective owners; use is descriptive.
Related guides
Common questions
Can I process the whole library at once?
The safer path is to start with a sample. After dates, reports and exceptions are validated, the same profile can be applied to the full batch.
Does MetaVault visually change my photos?
The metadata workflow is meant to write or extract information, not recompress the visual content. Still, keep a backup and use copy mode when there is risk.
What happens to files without reliable metadata?
They should appear in the report or in review folders. This keeps uncertain files from silently contaminating the final result.