The complete metadata an iPhone writes into every photo
iPhone cameras write metadata according to the EXIF 2.32 standard, extended with Apple-specific MakerNote tags. The output format is JPEG for standard shots and HEIC (High Efficiency Image Container) for devices running iOS 11 or later with the default camera settings. Both formats carry the same core metadata blocks, though HEIC packs them into ISO BMFF boxes rather than JFIF markers.
The metadata splits into six practical groups. The first is device identification: the camera make tag is always "Apple", the camera model tag records the exact model string (for example "iPhone 15 Pro"), and the software tag records the iOS build number at capture time — not just the major version but the precise build, such as "17.5.1". The lens model tag records which physical camera was used: wide, ultra-wide, telephoto, or TrueDepth front camera. On ProRAW shots, additional tags record the aperture value, the maximum aperture, and a lens ID specific to the Apple sensor stack.
The second group is temporal data. Three timestamp tags coexist in every iPhone photo. The DateTimeOriginal tag records the local time at the moment the shutter fired, to the second. The DateTimeDigitized tag is usually identical on a direct capture but differs if the photo was scanned or imported. The GPSDateStamp and GPSTimeStamp tags record UTC time derived from the GPS signal — these can differ from the local DateTimeOriginal by the timezone offset. The OffsetTimeOriginal tag, added in EXIF 2.31, records the UTC offset as a string such as "+08:00". Taken together, the temporal tags give an unambiguous absolute timestamp regardless of timezone.
The third group is location data. When Location Services are enabled for the Camera app — which is the default on a new iPhone — every photo receives GPS latitude, GPS longitude, GPS altitude, GPS speed (in metres per second), GPS bearing (compass direction), GPS horizontal position error, and GPS measure mode. The GPS latitude and longitude are stored as degree-minute-second rational values with a reference tag (N/S and E/W). Converted to decimal degrees, these typically land within 3–5 metres of the actual capture position. The GPSAltitude tag records elevation in metres above sea level; the GPSAltitudeRef tag specifies whether the value is above or below sea level.
The fourth group is exposure and optics: shutter speed (ExposureTime), aperture (FNumber), ISO sensitivity (ISOSpeedRatings), exposure programme (auto, manual, aperture priority), metering mode, flash status, focal length in millimetres, focal length equivalent for a 35mm sensor, and white balance mode. These tags are useful for photography workflows but also fingerprint the camera hardware precisely — a lens focal length of 2.22mm is specific to the iPhone 13 main sensor, for example.
The fifth group is colour and rendering: colour space (sRGB or Uncalibrated for wide-colour), gamma, the embedded ICC colour profile (Display P3 on all iPhones since iPhone 7), pixel dimensions, and resolution unit. The embedded ICC profile adds roughly 4 KB to every file and contains the profile description string "Display P3".
The sixth group is Apple MakerNote data. This is a proprietary block that Apple embeds in an undocumented format. Partially reverse-engineered tags include HDR mode (single frame, bracketed, or processed), scene type, image unique ID, and the AE/AF metadata that drives the computational photography pipeline. The MakerNote block is typically 1.5–3 KB and travels with the file unless explicitly stripped.
Why iPhone metadata creates concrete privacy risks
The risks are specific and measurable rather than theoretical. A photo taken at your home address and shared publicly contains GPS coordinates accurate enough to plot on a street map. A photo taken at a medical clinic, a legal office, or a place of worship does the same. The timestamp cluster, combined with GPS, forms a location-time record: proof that you were at a specific place at a specific time. A series of photos from the same device, shared across different platforms over time, creates a movement pattern even if none of the individual photos is sensitive in isolation.
The device model and iOS build tags create a software fingerprint. Security researchers have noted that specific iOS build numbers correspond to narrow release windows, which allows an attacker who knows the iOS build embedded in a photo to narrow the likely capture date to within a few days — even if the timestamp tags have been manually altered. The combination of device model, build string, and GPS data forms a strong pseudo-identifier that links photos to a single individual across platforms.
Journalists, activists, domestic abuse survivors, and anyone whose physical location is sensitive have a direct need to strip location metadata before sharing. But the risk is not limited to high-stakes cases: stalking incidents have been documented where the attacker used EXIF GPS data from public social media posts. A 2021 analysis of publicly available images on a major forum found that 6% retained GPS coordinates — roughly 1 in 17 images. Given that iPhone is the most common camera used for uploaded photos, this translates to a concrete, recurring exposure for ordinary users.
The iOS share sheet does offer a "Remove Location" option when sharing via the native share extension. This strips the GPS tags but leaves the remaining EXIF block — device model, iOS build, timestamps, and optics data — intact. For many users, partial removal is sufficient. For cases where full metadata removal is required, a dedicated stripping tool that removes all EXIF, IPTC, and XMP blocks is necessary.
How to view and remove metadata from iPhone photos without leaving your browser
The tools on this site process files entirely in your browser tab using the File API and the Canvas API. The photo never leaves your device. The JavaScript reads the raw bytes of the file, locates the EXIF segment within the JFIF stream (or the BMFF metadata box for HEIC, after conversion), parses the tag values, and displays them. No upload, no server, no log of your GPS coordinates on a third-party system.
To view the metadata in an iPhone photo, open the photo metadata viewer and drop the file into the dropzone. The viewer lists every tag name, tag ID, and decoded value. GPS latitude and longitude are decoded to decimal degrees alongside the raw degree-minute-second rational form. Timestamps show both the raw EXIF string and the parsed UTC equivalent. The MakerNote block is shown as a raw hex dump since its structure is partially proprietary.
To remove only the GPS block and leave camera data intact, use the GPS removal tool. This preserves the focal length, ISO, exposure, and device model tags that photographers sometimes need for workflow or rights purposes, while stripping the seven GPS sub-tags (latitude, longitude, altitude, bearing, speed, GPS timestamp, and position error).
To remove the entire EXIF block — device model, iOS version, all timestamps, all GPS data, and the Apple MakerNote — use the EXIF removal tool. The output is a JPEG with only pixel data and a minimal JFIF header. File size typically drops by 30–80 KB depending on how much metadata the original carried.
To strip all metadata standards in a single pass — EXIF, IPTC caption data, XMP editing history from Lightroom or Darkroom, and the embedded ICC colour profile — use the strip all metadata tool. This produces the smallest possible output file with no embedded data of any kind.
For HEIC files from iPhone: the tools on this site accept JPEG and PNG directly. If your iPhone photo is in HEIC format, use the HEIC to JPEG converter first, then run the metadata removal step on the converted file. The conversion itself preserves the original EXIF block in the output JPEG, so the subsequent removal step will find and strip all tags.
HEIC vs JPEG: how iPhone packages metadata differently
iPhones running iOS 11 or later default to saving photos in HEIC (High Efficiency Image Container) rather than JPEG. The visual difference is negligible at normal viewing sizes, but the internal structure is completely different — and that structure affects where metadata lives, how tools read it, and what is required to strip it cleanly.
JPEG stores metadata in marker segments prepended to the compressed image data. The EXIF block sits in a segment starting with the 0xFFE1 marker, followed by the "Exif\0\0" header and a TIFF-formatted byte stream containing all the tag IDs, types, and values. GPS data lives inside this same TIFF stream, in an IFD (Image File Directory) pointer from the main EXIF IFD. Stripping EXIF from a JPEG means removing that 0xFFE1 segment and rewriting the surrounding JFIF markers — a well-understood, deterministic operation.
HEIC is built on the ISO Base Media File Format (ISOBMFF), the same container family used by MP4. It stores image data and metadata in typed "boxes" — chunks of binary data identified by a four-character type code. The EXIF metadata in a HEIC file lives in a meta box inside a nested ISOBMFF hierarchy. A top-level meta box contains an iinf item info entry pointing to an item of type Exif. The GPS coordinates, timestamps, device model, and all other EXIF tags are encoded in the same TIFF IFD format as in JPEG, but reached through this ISOBMFF navigation path rather than a JFIF marker scan.
This means a JPEG EXIF stripper that walks JFIF markers will not find or touch a HEIC file's metadata — the two containers are structurally unrelated. Any tool handling HEIC metadata must implement ISOBMFF box parsing, navigate the item hierarchy, and either remove or zero out the Exif item. iPhone also writes a separate XMP item inside the HEIC container — an XML block containing Dublin Core fields, Apple camera extension tags, and any Lightroom or Darkroom editing instructions. This XMP item sits independently from the EXIF item and must be stripped as a separate step.
To check which format your iPhone is using: Settings → Camera → Formats. "High Efficiency" saves HEIC; "Most Compatible" saves JPEG. You can also confirm by looking at the file extension after exporting to Files — HEIC files show as .heic or .heif. If your photos are in HEIC format, convert to JPEG using the HEIC to JPEG converter on this site before running any metadata removal step. The conversion preserves the full EXIF block in the output JPEG, so every tag — GPS, device model, timestamps — will be present and removable in the next step.
iOS sharing controls: how to prevent location from leaving your device
iOS provides three distinct layers of control over location data when sharing photos. Each layer operates at a different point in the pipeline, and each has a different scope.
The most upstream control is the Camera app's location permission. In Settings → Privacy & Security → Location Services → Camera, you can set the camera to "Never". This prevents GPS tags from being written at capture time. No GPS is recorded, so there is nothing to strip when sharing. The tradeoff is that geo-tagging in the Photos app's map view, and location-based albums created from photos, will stop working for new photos. This setting is appropriate if you consistently do not want location in your photos; for selective control, the per-share method below is more flexible.
The second layer is the per-share "Options" panel in the iOS share sheet. When you tap the share icon inside the Photos app, an "Options" row appears at the top of the share sheet — on iOS 13 and later it shows "Location: On" or "Location: Off". Tapping it opens a panel with a "Location" toggle and an "All Photos Data" toggle. Turning off "Location" strips the seven GPS sub-tags (latitude, longitude, altitude, bearing, speed, GPS timestamp, and horizontal position error) from the copy sent through that share action. Turning off "All Photos Data" strips the complete metadata block — GPS, device model, iOS build, timestamps, focal length, and the Apple MakerNote — from the shared copy. Your original file in the Photos library is not modified. The removal applies only to the copy delivered to the recipient.
The third layer is the destination channel itself. AirDrop sends the full original file including all metadata, unless you apply the share sheet Options before confirming. iCloud Photo Sharing and shared albums preserve full EXIF by default. Messages compresses photos on send but retains GPS tags if the compressed copy still carries EXIF. Email via Mail sends the original unless Options is applied first. The reliable four-tap workflow on any iOS 13+ device: open the photo → tap Share → tap "Options" at the top of the sheet → toggle "Location" off → choose the destination. No third-party app required.
One edge case to be aware of: screenshots taken on iPhone do not inherit the GPS tags from the original photo. If you screenshot a photo rather than sharing the original file, the screenshot will have a different DateTimeOriginal (the time of the screenshot), no GPS tags, and a device model reflecting the current iPhone rather than whatever took the original photo. This makes screenshotting a rough but effective stripping method for GPS, though it also resamples and compresses the image. For lossless stripping, the share sheet Options panel or a dedicated browser tool preserves image quality while removing only the metadata.
What actually happens when you drop a file into the browser tool
"Browser-local processing" is a claim many tools make. The specific mechanism matters because it determines whether your photo bytes travel over any network connection at any point during processing.
When you drop a file onto the dropzone on this site, the browser's File API passes the file object to the JavaScript running inside the page's execution context. The file is not touched by the browser's network stack. You can verify this yourself: open the browser's DevTools Network panel (Command+Option+I on Mac, then the Network tab), clear the log, then drop a photo. No outbound request carrying the photo will appear. The only network traffic visible will be from loading the page's own static assets, which completed before you dropped anything.
The JavaScript reads the file's bytes using FileReader.readAsArrayBuffer(), which produces a typed ArrayBuffer — a contiguous block of memory containing every byte of the image. For a JPEG, the code scans for the 0xFFD8 SOI marker at byte zero, then walks marker segments forward until it locates the 0xFFE1 EXIF segment. The EXIF segment contains the "Exif\0\0" header followed by a TIFF stream. The TIFF header's byte-order mark — little-endian0x4949 or big-endian 0x4D4D — determines how multi-byte values are read. The code then iterates through IFD entries (each 12 bytes: tag ID, data type, value count, and value or value offset) to extract individual tag values including GPS, timestamps, and device model.
To strip metadata, the code rebuilds the JPEG by copying only the segments it wants to keep — the SOI marker, a minimal JFIF APP0 header, and the compressed scan data — while discarding the EXIF APP1 segment, any IPTC APP13 segment, and any Adobe APP14 segment. The result is wrapped in a Blob with MIME type image/jpeg, and a download URL is created from that blob using URL.createObjectURL(). The blob lives only in the current tab's memory. When you close the tab or navigate away, the browser garbage-collects it. No copy of your photo is written to disk by the tool, cached on a server, or transmitted anywhere.
Processing time scales with file size: a 6 MB iPhone 15 Pro RAW-converted JPEG takes roughly 80–150 milliseconds in a modern browser, a 2 MB standard JPEG takes 20–40 milliseconds. Both complete before a round-trip network request to the nearest server would return. The absence of a network round-trip is not a performance trick — it is a structural consequence of the data never leaving the browser sandbox.