← Back to blog

Does Converting a Photo Remove EXIF Metadata?

Learn why image conversion is not a metadata-removal guarantee, see a tested HEIC-to-JPG comparison, and create verified sanitized copies on Windows.

By LocalFlux Editorial Team

WindowsPrivacy
LocalFlux workflow for does converting a photo remove exif metadata.
On this page
  1. Quick answer
  2. What EXIF metadata can reveal
  3. Our ordinary conversion test
  4. Create a sanitized copy with Share safely
  5. What Share safely does
  6. Why conversion behavior varies
  7. How to verify a photo before sharing
  8. Does uploading to social media remove metadata?
  9. Final checklist
  10. Publication evidence
  11. Practical checks before and after conversion

Quick answer

No, not reliably. Converting HEIC, JPG, PNG, AVIF, or another image format may preserve, transform, or drop metadata depending on the tool and settings. If privacy matters, use an explicit metadata-removal mode and verify the output instead of assuming that format conversion made the photo safe.

In our LocalFlux test, an ordinary HEIC→JPG conversion preserved the source DateTimeOriginal EXIF value. The Share safely path removed the EXIF profile and reported that the sanitized copy was verified.

What EXIF metadata can reveal

Exif is a camera-image metadata standard maintained by CIPA and JEITA. The current CIPA standards list identifies Exif 3.1 as the exchangeable image file format standard for digital still cameras.

Depending on the photo and device, metadata can include:

Not every photo contains all of these fields. The safe assumption is that you do not know until you inspect it.

Our ordinary conversion test

We added an EXIF-bearing HEIC fixture and ran a normal HEIC→JPG conversion.

Ordinary HEIC to JPG conversion ready

Ordinary HEIC to JPG conversion completed

ImageMagick metadata probes returned:

FileDateTimeOriginalProfile result
Source HEIC2020:12:03 15:04:31exif
Ordinary JPG2020:12:03 15:04:31exif

The conversion succeeded, but it did not remove the capture timestamp. That is the central lesson: a new extension is not proof of sanitization.

Create a sanitized copy with Share safely

  1. Add the image to LocalFlux.
  2. Expand Options.
  3. Turn on Share safely.
  4. Review the size preset and optional privacy-safe filename setting.
  5. Select Create safe copies.
  6. Wait for the queue to report that the safe copy was created and verified.

Share safely enabled before conversion

Verified sanitized copy completed

For the same fixture, the sanitized JPG returned no DateTimeOriginal value and no embedded profile in the metadata probe:

FileDateTimeOriginalProfile result
Share safely JPGAbsentNone reported

LocalFlux also reported: Safe copy created and verified · Private metadata removed. The original HEIC was left unchanged.

What Share safely does

For supported image routes, Share safely creates a new copy, applies orientation, normalizes the sharing output, strips embedded metadata, and verifies that disallowed Exif, IPTC, XMP, comment, label, and caption data are absent before reporting success.

It does not make the picture anonymous in every sense. The pixels can still reveal a face, address, screen, license plate, landmark, document, reflection, or other identifying detail. A filename can reveal information too unless you enable privacy-safe filenames or rename the copy carefully.

Why conversion behavior varies

Metadata can be stored in several structures, not just one EXIF block. Tools make different choices: some copy profiles by default to preserve photographic context, some remove a subset, and others rebuild metadata. Output formats also differ in what they can store.

That is why advice such as “PNG has no EXIF” or “screenshotting always removes metadata” is too broad. Use an explicit privacy workflow and inspect the exact output that will be shared.

How to verify a photo before sharing

Use at least two checks for sensitive material:

  1. Inspect file properties or a trusted metadata viewer.
  2. Confirm that GPS, capture time, device, author, comments, and XMP/IPTC fields are absent.
  3. Inspect the visible pixels for identifying information.
  4. Share the sanitized copy instead of the original.

For a Windows-specific walkthrough, see how to remove photo metadata on Windows 11.

Does uploading to social media remove metadata?

Do not rely on it. Services can change processing behavior, preserve selected fields internally, or generate downloadable variants with different properties. Sanitize before upload when privacy matters.

Final checklist

Get LocalFlux from the Microsoft Store

Publication evidence

The screenshots and measured results come from privacy-reviewed fixtures tested with LocalFlux 1.0.7.0. The source files, outputs, and reproducibility notes are available here:

Practical checks before and after conversion

The reliable workflow is to test a matrix of JPG, PNG, WebP, HEIC, and other intended formats; inspect EXIF, XMP, IPTC, GPS, orientation, comments, and container-specific fields in the actual output. This matters because changing a file extension does not preserve every property of the source. Decide what the destination actually needs, keep the source as the master, and use a small representative file before processing a large batch.

Before you start

Review the output

A successful status only confirms that an output was written. It does not prove that every font, frame, channel, page, formula, profile, tag, or accessibility feature survived. For important work, inspect representative outputs and retain the original until the delivered copy has been accepted.