Why Metadata Matters in Image Conversions

Every photograph carries a digital fingerprint that goes far beyond the pixels you see on the screen. EXIF (Exchangeable Image File) tags store technical details such as exposure, camera model, and GPS coordinates, while IPTC fields hold creator information, copyright notices, and keywords. When an image is transformed from one format to another—say, from RAW to JPEG, or from PNG to WebP—those embedded details can be lost, altered, or stripped entirely. The consequences are practical: a photographer may lose proof of authorship, a news outlet might discard date stamps that verify the timeliness of a shot, and a mapping service could lose geolocation data that powers location‑based features. In workflows that involve bulk processing, archiving, or publishing, preserving this metadata isn’t a cosmetic concern; it’s a compliance, legal, and discoverability issue.

Understanding What Gets Lost

Different containers treat metadata differently. A RAW file (e.g., .CR2, .NEF) often bundles a full suite of EXIF tags alongside proprietary camera data. When you export to JPEG, most software retains the standard EXIF fields but may discard proprietary maker notes. Converting to lossless PNG strips almost all EXIF by design, because the PNG specification stores only a limited set of textual chunks. WebP, being a newer format, welcomes a subset of EXIF but many tools forget to copy it over. IPTC, stored in the XMP block of many formats, suffers a similar fate when a conversion pipeline doesn’t explicitly map it. Knowing which fields survive in which target format is the first line of defense.

Choosing the Right Destination Format

If retaining the full gamut of metadata is non‑negotiable, avoid formats that inherently discard it. Lossless formats such as TIFF (with "TIFF/EP") and JPEG‑2000 preserve both EXIF and IPTC intact, provided the conversion tool respects the container. For web‑oriented distribution where size matters, stick with JPEG or WebP but plan to re‑inject metadata after compression. Some workflows adopt a two‑step approach: first, convert the visual data into a size‑optimized image, then copy the original metadata block into the new file using a dedicated tool.

Preparing Your Source Files

Before any conversion, create a reliable inventory of the metadata you need to keep. Tools like exiftool (exiftool -j *.jpg > metadata.json) can dump all EXIF and IPTC tags into a JSON file. Review the output for fields that are critical—author, copyright, GPS, lens specifications. If you discover inconsistencies (e.g., missing GPS in a batch), correct them now. Consistency at the source reduces the chance of accidental loss downstream.

The Conversion Pipeline: A Practical Blueprint

Extract Metadata – Run exiftool -tagsFromFile source.jpg -all:all -b > meta.xmp. This creates an XMP sidecar that holds every transferable tag.
Convert the Image – Use a conversion utility that offers a metadata‑preserve flag. ImageMagick (magick source.tif -quality 85 destination.jpg) does not preserve EXIF by default; you must add +profile "*" to retain all profiles, or more safely, -strip only when you deliberately want a clean image. libvips (vips copy source.tif destination.webp[Q=80]) also allows --exif to copy the block.
Re‑inject Metadata – After the visual conversion, apply the sidecar: exiftool -tagsFromFile meta.xmp -overwrite_original destination.jpg. This overwrites the placeholder EXIF with the original data.
Verify Integrity – Run a diff on the metadata: exiftool -j source.jpg > src.json && exiftool -j destination.jpg > dst.json && diff src.json dst.json. Any missing fields should be flagged immediately.

Adhering to this four‑step pattern keeps the conversion stateless: you never rely on the converter to do the right thing automatically; you explicitly manage the metadata yourself.

Batch Processing Without Losing Data

When thousands of images need to be transformed, manual sidecar handling becomes impractical. Shell scripting or a language like Python can orchestrate the workflow. Below is a concise Bash loop that respects the blueprint:

#!/usr/bin/env bash
for src in *.tif; do
  base=$(basename "$src" .tif)
  exiftool -tagsFromFile "$src" -all:all -b > "${base}.xmp"
  magick "$src" -quality 85 "${base}.jpg"
  exiftool -tagsFromFile "${base}.xmp" -overwrite_original "${base}.jpg"
  rm "${base}.xmp"
done

In Python, the piexif library can read and write EXIF dictionaries directly, while Pillow handles the visual conversion. The key is to keep the metadata object in memory and write it back after the image data has been processed, thereby eliminating the need for temporary sidecar files.

Edge Cases and Common Gotchas

Color Profiles – ICC profiles are often stored alongside EXIF. If you convert to a format that doesn’t support ICC (e.g., GIF), the profile is discarded. In such cases, embed the profile into the new file using exiftool -icc_profile=original.icc destination.gif.
Orientation – Cameras record orientation in EXIF. Some converters automatically rotate the pixel data but then delete the orientation flag, resulting in a double‑rotated image when viewed elsewhere. Always check the final image with identify -verbose (ImageMagick) to ensure the orientation tag matches the visual orientation.
GPS Precision – Latitude/longitude stored as rational numbers can be rounded during naive copying. Preserve the exact rational representation by using exiftool’s -gps:all= syntax rather than converting to decimal strings.
Privacy – GPS tags can expose location data inadvertently. If you are sharing images publicly, consider stripping location fields after copying the essential rights metadata. A command like exiftool -gps:all= -overwrite_original *.jpg removes geotags while leaving author and copyright intact.

Leveraging Online Services While Keeping Control

When an on‑premise solution is infeasible—say, a small design studio without a dedicated server—cloud converters can fill the gap. Services that run entirely in the browser, such as convertise.app, avoid uploading files to remote servers, thereby preserving privacy. However, even in‑browser tools may not copy metadata automatically. The safest approach is to perform the visual conversion online, then re‑attach the original EXIF/IPTC block locally using a desktop tool, thus keeping the sensitive data out of the network path.

Auditing and Documentation

For organizations that must demonstrate compliance (e.g., news agencies, legal evidence handlers), maintaining an audit trail of the conversion is essential. Record the checksum of the source (sha256sum source.jpg > source.sha256) and the checksum of the converted file (sha256sum destination.jpg > dest.sha256). Store the metadata JSON (exiftool -j source.jpg > source_meta.json) alongside the checksums. When questioned, you can prove that the visual content changed only as intended and that the metadata remained unchanged.

Future‑Proofing Your Workflow

The standards governing metadata evolve. XMP, introduced by Adobe, is now the lingua franca for IPTC and other rights metadata, and many newer formats (WebP, HEIF) support XMP natively. Build your pipeline to prioritize XMP sidecars because they survive format migrations better than proprietary EXIF blocks. Additionally, keep your tooling up‑to‑date: newer releases of exiftool, ImageMagick, and libvips add support for emerging tags and improve the fidelity of metadata copying.

Summary

Preserving EXIF and IPTC metadata through image format conversions is a disciplined process, not an incidental feature. By extracting metadata first, converting the visual payload with a tool that respects profiles, and then re‑injecting the original blocks, you retain the full documentary value of each image. Batch scripts automate the routine, while checksum logging and sidecar archives provide the auditability required by organizations that rely on accurate provenance. Whether you run the pipeline locally or use a privacy‑focused browser tool like convertise.app, the essential principle remains the same: treat metadata as a first‑class citizen, not an afterthought.

How to Preserve Image EXIF and IPTC Metadata When Converting Files