Key takeaways
- EXIF is metadata embedded in JPEG and HEIC files — timestamp, device, exposure settings, orientation, and on phones usually GPS coordinates.
- A photo sent by messaging app or email attachment can reveal where your home, school or workplace is; phone cameras write location by default.
- Most social platforms strip EXIF on upload; direct file sharing — email, cloud links, messaging 'document' mode — does not.
- Viewing metadata needs no software: an in-browser EXIF reader shows every field without the photo ever leaving your device.
- Stripping is simple and lossless to the pixels: re-encoding without metadata (a convert or compress pass) yields a clean file.
What EXIF Actually Is
Exchangeable Image File Format — a standard block of key-value pairs the camera writes into the file when it saves. In a JPEG it lives between the header and the image data; HEIC carries the same ideas in its own container. The fields fall into four groups, and knowing the groups covers almost every question anyone has about a photo's innards.
The camera report: make, model, lens, focal length, aperture, shutter speed, ISO, exposure compensation — the information that lets a photographer reverse-engineer someone's settings from a posted picture. The timeline: capture date and time, plus creation and modification stamps, often with sub-second precision and a timezone offset. The geometry: pixel dimensions, orientation flag (the field that makes phone photos rotate correctly in some apps and wrongly in others), and a thumbnail. And the location: GPS latitude, longitude, altitude, plus the bearing the camera was pointed — written whenever the phone had a fix when the shutter fired.
How to Read It (No Software Required)
Desktop: Windows shows a summary in a file's Properties → Details tab; macOS exposes the full set in Preview's inspector (Tools → Show Inspector → the EXIF camera tab). Both hide the GPS block unless you dig, which is itself a hint about how invisible this data usually is.
The complete picture needs a real reader — an online EXIF viewer parses every tag including the ones the OS summaries omit. On this site the reader runs entirely in your tab: it parses the file's header with JavaScript, so the photo (and its location data) never travels anywhere. That privacy property is unusual for a metadata tool and matters more than it sounds: you are about to inspect files that contain your home coordinates.
What to look for when it is your photo: the GPS block (latitude, longitude, altitude and direction — the full 'where and which way'), the exact capture datetime, and the device string. Those three are the fields with real-world consequence; the rest is camera trivia.
Stripping: When and How
Before posting a photo anywhere the original file will travel — a marketplace listing, a PDF you email, a file link in a chat — a strip pass is thirty seconds of hygiene. Two routes work: any re-encode that does not carry metadata forward (converting the photo with most browser tools produces a rebuilt file whose header is written fresh), or a dedicated scrub. On this site, running the photo through the compressor or a format converter yields a rebuilt file; verify with the EXIF viewer on the output, which is the only honest way to know a strip happened.
One professional reason to keep EXIF, so the guide is not one-sided: copyright and provenance workflows depend on capture data, some jurisdictions and stock platforms value it, and photographers routinely check a file's metadata to spot their own images scraped and reposted. The decision is per-audience: family and public get stripped files; your own archive keeps everything.
Prevention beats removal for phones that allow it: iOS Settings → Privacy → Location Services → Camera → Never writes no GPS at capture; Android's equivalent sits in the camera app's location-tagging toggle. Photos taken after that simply never carry the coordinates you would otherwise have to scrub.
The Orientation Trap and Other EXIF Curiosities
The most common EXIF-related bug people actually hit: a photo that looks upright on your phone and sideways on a website. The pixels are stored landscape; an orientation tag tells displayers to rotate. Apps that respect the tag show it right; servers that read pixels but ignore the tag bake it wrong. The fix when you are the one uploading: rotate-and-bake the orientation with the rotate tool, so the pixels match every viewer's assumption.
Curiosity tier, since once you can read EXIF you will read all of it: the thumbnail inside full-size files (a hidden 160 px preview, sometimes of the scene before you cropped), the sequence counter that reveals a burst's frame number, lens serial numbers on some systems, and the quiet DRM-adjacent fields — GPS being the one with consequences, and the reason this section exists at all.
Frequently asked questions
The questions people ask most about exif data: what your photos secretly carry (and how to read or strip it), answered directly.