What Metadata Survives a HEIC-to-JPG Conversion
iPhone Camera defaults to HEIC. Exporting JPEG for compatibility is routine. Many converters copy the EXIF box into APP1 — GPS included. “I already converted it” is not a substitute for stripping the JPEG.
Ready to clean a photo? MetadataWipe processes JPEG and PNG files locally — no account and no server upload.
Open MetadataWipe toolHEIC (HEIF) is the iPhone Camera default since iOS 11: a different container from JPEG, with EXIF in ISOBMFF-style boxes rather than a JPEG APP1 segment. The rest of the world still asks for JPG. Conversion is the everyday fix — Mail, a Windows PC, a CMS, a printer kiosk. Conversion is also where people invent a privacy story: JPEG feels like a “simple” file, HEIC felt “Apple-ish,” so the tags must have fallen off. They often did not. A competent converter’s job is to preserve capture time and orientation so the photo still sorts and rotates. GPS is sitting in the same metadata family. Many libraries copy the lot.
How to strip HEIC-origin files in general is strip EXIF data from HEIC. How iPhone and Android headers differ structurally is metadata differences between iPhone and Android photos. This page is the conversion event: what typically survives the hop into JPG, and why that hop is not a wipe.
What a typical converter copies
Standard EXIF that users notice: DateTimeOriginal, Orientation, Make (Apple), Model (iPhone version string), and — if present — GPSLatitude, GPSLongitude, and related GPS IFD tags. Color profile (ICC) may be converted or attached so the JPEG does not look wrong. Thumbnail EXIF in the JPEG can duplicate a small preview; that preview is pixels, not a second GPS, but it is another place people forget a cover if they redacted the main image in a tool that left the embedded thumbnail alone. MetadataWipe’s rebuild is about not copying typical tag blocks into the cleaned download; conversion tools are about producing a compatible picture, which is the opposite incentive.
MakerNotes are the messy middle. Apple’s MakerNote is a binary blob (Live Photo identifiers, HDR pipeline flags, and similar). Some JPEG exporters copy it into EXIF tag 0x927C. Some drop it because it is awkward. Dropping MakerNotes while keeping GPS is common. That is not “cleaned.” That is “the converter did not want to deal with Apple’s blob.” XMP (including some depth or edit history) may copy, flatten, or vanish. Do not use “Get Info looks emptier” on Windows as proof GPS is gone; Windows has historically been uneven at HEIC and at showing GPS.
What sometimes gets dropped — and what never should be assumed dropped
Dropped (sometimes): HEIF-specific boxes that have no JPEG equivalent, Live Photo pairing UUIDs if the exporter writes a still-only JPEG, certain Apple proprietary fields, depth maps. Not a privacy guarantee: GPS, timestamps, and device model. Those fields have well-known JPEG homes. If the converter is “good,” it keeps them. If you needed GPS gone, you must strip after convert, or use a stripper that reads HEIC and writes a clean JPEG in one documented pass — then still verify.
iOS share sheets that offer “strip location” are GPS-only options, and only on some surfaces (Mail has had a location switch). They are not a full EXIF diet. Convert plus “hide location on this send” can still leave DateTimeOriginal and Model on the JPEG, and it does not rewrite the HEIC in the library.
How to convert, then actually strip
- Export a JPEG you will send (Photos export, Most Compatible going forward, or a converter you already use). Note the new filename so you do not mix it with the HEIC.
- Open that JPEG in the MetadataWipe tool. If GPS still shows, conversion copied it. That is normal, not a failure of the converter.
- Strip locally. Typical EXIF/IPTC/XMP are not copied into the cleaned download.
- Re-open the cleaned JPEG. If tags remain, you dropped the wrong file (often the HEIC or a second export).
- Send the cleaned JPEG. The HEIC in iCloud Photos is still tagged. Conversion never edited it.
If you still need a HEIC-oriented walkthrough, use strip EXIF data from HEIC. If you are choosing between iPhone and Android header layouts, use iPhone vs Android photo metadata. Stay here when the sentence you were about to trust was “it’s a JPG now.”
Mistakes that treat JPG as a privacy format
Emailing a converted JPEG and deleting nothing from Photos. The library original remains geotagged.
Using a web “HEIC to JPG” site for a photo you would not want that site to keep. Convert on the device; then strip here locally.
Checking the HEIC in an old Windows build, seeing no tags, converting, and skipping the JPEG check. The OS failed to parse HEIC. The JPEG may be full of EXIF.
Most Compatible as a wipe. It is a format switch. Strip the JPEGs it writes if they will travel.
Redacting pixels on the JPEG and skipping the strip because “conversion probably handled it.” Conversion probably copied GPS. Two jobs.
Related guides
See also:
Frequently asked questions
Does saving a HEIC as JPEG remove GPS?
Often no. Photos, Preview, ImageMagick, and many “convert to JPG” share sheets copy DateTimeOriginal, GPS, Make, and Model into the JPEG. Some paths drop MakerNotes or XMP and keep GPS. Some poorly written converters drop everything. You cannot know which you used without inspecting the JPEG.
Is iOS “Most Compatible” (JPEG from Camera) already clean?
No. Most Compatible changes the capture format to JPEG. It still writes EXIF. Location Services still writes GPS if Camera is allowed to use location. You get a more compatible container, not a privacy wipe.
Why doesn’t MetadataWipe open HEIC directly?
The homepage tool rebuilds JPEG and PNG in the browser. Convert or export a JPEG first, then strip that file — and verify the JPEG, because conversion may have copied the tags you care about.
Does MetadataWipe send the JPEG to a server after conversion?
No. The strip runs in browser memory on this device.
Remove EXIF data, GPS location, and common photo metadata in your browser.
Try MetadataWipe free