Are these 27 fields the same across iPhones?

The exact count varies by model and iOS version. Newer iPhones write more (focus stack data, computational photography hints, deep fusion markers). Older iPhones write fewer. The structure is the same: location, device fingerprint, processing trail.

Does iCloud sync these fields between devices?

Yes. iCloud Photos preserves the EXIF block as-is. The metadata that leaks from one device leaks from all of them, and they can be surfaced in the Places, People and Memories views on any device on your Apple ID.

Can I prevent iOS from writing these fields in the first place?

Partially. Disable location services for the Camera app to stop GPS being written. The other fields (model, lens, software, thumbnail, timestamps) cannot be disabled — they are written unconditionally.

Do third-party camera apps leak the same fields?

They leak the same families of fields but with different implementations. Some respect the OS-level location permission; some embed their own version string. The safe assumption is that any camera app writes a similar block.

Does removing these fields hurt the photo in any way?

No. The pixels are untouched. EXIF, XMP and IPTC are separate blocks layered onto the file; removing them does not change how the photo displays. You lose only the metadata itself.

Explainer

What metadata does an iPhone leak?

A modern iPhone embeds roughly 27 metadata fields in every photo — GPS coordinates with altitude and heading, exact device model, lens identifier, exposure settings, software version, and a small preview thumbnail. None of it is necessary for the photo to display; all of it travels with the file.

The 27 fields a modern iPhone embeds

Every JPEG or HEIC out of an iPhone carries a structured block of tags. They split into three groups: location, device fingerprint and processing trail.

Location: latitude, longitude, altitude, GPS direction, GPS speed (when moving), GPS timestamp, GPS reference (above/below sea level).

Device fingerprint: make (Apple), model (iPhone 15 Pro Max), camera body serial number (sometimes), lens identifier (24mm f/1.78 main camera), focal length, focal length in 35mm equivalent, software version (iOS 17.x), Apple Maker Note (proprietary block with burst, Live Photo and focus stack IDs).

Processing trail: capture timestamp (down to milliseconds), modify timestamp, original timestamp, exposure time, ISO, f-number, exposure bias, flash mode, white balance, metering mode, embedded thumbnail (160×120 preview).

Most of these are written automatically. None of them is required to display the photo on any platform — they exist purely for cameras and editors that want to interpret the shot.

Three real-world leak scenarios

Scenario 1: a stalker uses the GPS on your photo. A journalist published a piece on covering her location; the photo she posted with the article carried home coordinates accurate to four metres. Within a day a stalker showed up.

Scenario 2: device fingerprint correlation. Two pseudonymous accounts share photos. The cameras carry the same body serial number. Within a few days an investigator links the accounts to the same iPhone and to the same Apple ID.

Scenario 3: the thumbnail leak. A celebrity edits an iPhone photo to crop out a sensitive detail. The 160×120 embedded thumbnail still shows the original. A few hours after posting, the uncropped thumbnail is everywhere.

How to audit a photo before sharing

Open exifsweep.com/app in your phone's browser. Drop the photo. The viewer shows every EXIF, XMP and IPTC field found.

Walk the list. GPS first — confirm what was captured. Device fingerprint next — model, lens, software. Then the timestamps — note that "original" and "modify" can disagree by hours, revealing edit time.

Finally, the embedded thumbnail. If you cropped, edited or redacted the photo, check that the thumbnail does not show the original. If it does, strip it.

For shares you care about, audit before posting and strip the whole block. For shares you do not care about, strip anyway — the cost is a few seconds.

Audit a photo from your iPhone →

Frequently asked questions

Are these 27 fields the same across iPhones?: The exact count varies by model and iOS version. Newer iPhones write more (focus stack data, computational photography hints, deep fusion markers). Older iPhones write fewer. The structure is the same: location, device fingerprint, processing trail.
Does iCloud sync these fields between devices?: Yes. iCloud Photos preserves the EXIF block as-is. The metadata that leaks from one device leaks from all of them, and they can be surfaced in the Places, People and Memories views on any device on your Apple ID.
Can I prevent iOS from writing these fields in the first place?: Partially. Disable location services for the Camera app to stop GPS being written. The other fields (model, lens, software, thumbnail, timestamps) cannot be disabled — they are written unconditionally.
Do third-party camera apps leak the same fields?: They leak the same families of fields but with different implementations. Some respect the OS-level location permission; some embed their own version string. The safe assumption is that any camera app writes a similar block.
Does removing these fields hurt the photo in any way?: No. The pixels are untouched. EXIF, XMP and IPTC are separate blocks layered onto the file; removing them does not change how the photo displays. You lose only the metadata itself.