Direct answer
EXIF and related image metadata can reveal facts about how a file was captured or edited, and GPS metadata can reveal a location when it is present. Not every image contains the same fields. Screenshots, exports, edited copies, and images passed through different applications may carry different metadata from the original camera file.
The safest practical question is not “Does every photo contain EXIF?” but “What does this particular file contain, and do I want to share it?”
What EXIF data is
EXIF, short for Exchangeable Image File Format, is a set of image metadata fields commonly used by cameras and imaging software. Metadata is information stored in the file structure around the image data. It is different from the visible pixels that make up the photograph.
EXIF is only one metadata family. Images can also contain IPTC, XMP, ICC color-profile information, format-specific chunks, thumbnails, and application or vendor data. Which families exist depends on the device, software, and file format. The CIPA Exif standards and ExifTool documentation describe these fields and metadata families in more detail.
What information can EXIF reveal
| Metadata | What it may indicate | Important qualification |
|---|---|---|
| GPS coordinates | The location recorded by a device or application | Only when GPS data exists and is accurate enough to be useful. |
| Camera make and model | The device family or capture source | Some workflows remove or replace these fields. |
| Capture or modification time | A timestamp associated with capture, editing, or export | The field name and workflow determine what the time means. |
| Orientation and capture settings | How the image should be displayed and some camera settings | These are technical clues, not a complete account of the scene. |
| Software or editing information | That a program or workflow touched the file | Availability and accuracy vary by application. |
GPS and location
GPS fields can contain coordinates or related location information. If present, they may disclose where the device recorded the image. A photo does not need to display a map for its file metadata to contain location data.
GPS was not generated in the controlled ZANCTA experiment described below. This guide therefore explains how to inspect GPS metadata, but it does not claim that the experiment demonstrated GPS removal.
Camera, device, and software information
Make and Model fields can identify a camera or device family when those fields are present. Software or editing fields may indicate that an application exported or modified the file. These clues are not always present, and they do not necessarily identify a person by themselves.
A file can also disclose information through its filename, visible content, or later processing by the service receiving it. Metadata is one part of the sharing decision, not the whole decision.
Dates and times
A file may contain fields such as a camera capture time or a software modification time. Treat the meaning cautiously: a clock can be wrong, an application can rewrite a timestamp, and different fields can describe different stages of the workflow. A timestamp can describe timing, but it should not automatically be treated as proof of physical location.
Metadata is not the same as image content
Removing metadata does not remove information visible in the photograph. Faces, street signs, addresses, documents, screens, landmarks, uniforms, and text inside the image remain pixels. A recipient may also learn from the filename or from information the receiving platform generates after upload.
Metadata cleanup can reduce embedded information in a copy of the file; it does not make the image itself anonymous or guarantee what another service will do with it later.
How to inspect metadata yourself
Use a metadata inspector on the exact file you plan to share. Look for GPS, camera/device fields, capture and modification times, software, IPTC, XMP, and profile information. Different tools expose different families, so an empty result in one viewer is not automatically a complete inventory.
ExifTool is a widely used command-line inspector with documentation for EXIF, GPS, IPTC, XMP, ICC profiles, and format-specific data. The ExifTool tag reference is useful when you need to understand a field rather than just see that a file contains metadata. The Library of Congress Exif reference provides additional format context.
What metadata-cleaning tools actually do
A cleaner may remove selected metadata blocks directly, or it may decode and re-encode the image so that much of the original file structure is not carried into the output. Re-encoding can change file size, compression, quality, color-profile information, or other container details.
A successful cleanup of one field does not establish removal of every metadata family. Inspect the output again when the sharing risk is significant, and keep the original separately if you still need its capture information.
What ZANCTA EXIF Cleaner does
ZANCTA EXIF Cleaner accepts JPG/JPEG, PNG, and WebP images. The current limits are 50 MB per file, up to 20 files, and a maximum decoded dimension of 12,000 × 12,000 pixels. HEIC, SVG, RAW, and PDF are outside this image cleaner path.
The implementation decodes the image in the browser, draws it to a canvas, and re-encodes it in the same image family where supported. JPEG and WebP use a quality value around 0.92 in this path. PNG is re-encoded without a JPEG/WebP quality parameter. This describes the implementation; it is not a claim that every possible metadata family is removed.
To perform the cleanup, use the EXIF Cleaner tool or read the separate removal guide.
Controlled ZANCTA production observations
The following observations came from the Phase 8F research harness at https://zancta.tech/tools/exif-cleaner using Chromium via Playwright. The run was timestamped 2026-09-14T18:29:17.883Z and recorded commit 256d1ba022c87f15b353ed4410cb89ae9563e5b6. The fixtures were synthetic; no personal photographs or real GPS coordinates were used. The results are controlled production observations, not an exhaustive metadata-removal benchmark.
| Metadata or observation | What it can mean | Evidence scope and limitation |
|---|---|---|
| JPEG: 3,202 → 2,424 bytes; 320 × 200 before and after | The tested re-encode reduced this fixture’s file size. | One synthetic JPEG; not a general compression result. |
| JPEG Make, Model, DateTime, DateTimeOriginal absent after processing | Those inserted fields were not present in the inspected output. | Pillow inspection; not exhaustive metadata coverage. |
| WebP: 1,220 → 1,474 bytes; 320 × 200 before and after | The tested re-encode increased this fixture’s file size. | One synthetic WebP; not a general compression result. |
| WebP inserted EXIF fields absent after processing | The tested synthetic EXIF fields were not present in the inspected output. | Other WebP metadata families were not exhaustively tested. |
| PNG: 2,014 → 3,758 bytes; 320 × 200 before and after | The tested PNG re-encode increased this fixture’s file size. | One synthetic PNG; not a general compression result. |
| PNG Software, Comment, and Creation Time absent after processing | Those inserted textual fields were absent in the inspected output. | Other PNG chunks and metadata families were not exhaustively tested. |
ICC profile information was observed in the JPEG and WebP output inspection. That is one reason this evidence should not be summarized as “all metadata removed.”
What this experiment does not prove
- It does not demonstrate universal GPS removal; no reliable GPS fixture was generated.
- It does not establish complete IPTC, XMP, MakerNotes, C2PA, or JUMBF removal.
- It does not establish complete ICC-profile behavior across browsers and formats.
- It does not predict every camera, application, browser, device, or future implementation.
- It does not make a photo anonymous or establish complete privacy.
Practical checklist before sharing a photo
- Inspect the exact file you plan to share.
- Check GPS specifically if location exposure matters.
- Review camera/device fields and timestamps where relevant.
- Inspect the visible image for faces, addresses, documents, screens, signs, landmarks, and text.
- Clean a copy when appropriate, then inspect the output again for higher-risk sharing.
- Remember that the receiving platform may process or add information independently.
Related resources
Use the EXIF Cleaner when you need to process a supported image. The removal guide covers that workflow. For the broader browser-processing boundary, see local processing.
If you want to examine network behavior independently, use the browser file-upload verification guide. For format tradeoffs, see JPG vs PNG vs WebP.
Bottom line
EXIF and related metadata can reveal useful or sensitive information when those fields are present, including location, device, timing, and software details. Inspect the actual file before sharing. Metadata cleanup can reduce embedded information, but it is not the same as removing what the image visibly shows or guaranteeing what another service will do later. The ZANCTA observations above are specific to controlled synthetic fixtures and the tested fields, not a universal removal guarantee.
Sources
- CIPA Exif standards — Exif specifications for digital still cameras.
- Library of Congress: Exchangeable Image File Format — format reference and standards context.
- ExifTool application documentation — metadata families and inspection capabilities.
- ExifTool tag reference — tag and format details.
- IPTC Photo Metadata Standard — broader photo metadata context.