Capture and location details
EXIF fields may include a camera or phone model, capture time, lens settings, and GPS coordinates. Whether these values exist depends on the device and how the image was exported.
Inspect supported EXIF, GPS, XMP/IPTC, text, and embedded credential fields in a photo. The report helps you understand what the file contains before you share or edit it.
Inspection runs locally in your browser. The selected image is not uploaded or changed.
or choose one from your device
JPG · PNG · WebP · HEIC/HEIF · AVIF · Up to 20 MB eachInspect supported EXIF, GPS, text, XMP, and embedded credential containers. Available fields vary by file; generator compatibility is not guaranteed.
Select a supported image to see detected metadata fields. Nothing is uploaded.
EXIF fields may include a camera or phone model, capture time, lens settings, and GPS coordinates. Whether these values exist depends on the device and how the image was exported.
XMP or IPTC data can contain captions, author or rights details, software names, editing notes, and other descriptive fields. A software field alone does not prove who created an image.
Some files include structured Content Credentials or related provenance data. Their presence is not by itself proof of AI authorship, and this viewer does not validate credential signatures.
A metadata report groups values by the file container that stores them. The examples below are common, but a particular image may contain only some of these fields. Values describe file data; they do not independently prove who made the image or whether it is authentic.
| Container | Common examples | What a value may tell you | What to review before sharing |
|---|---|---|---|
| EXIF / GPS | Capture date, camera or phone model, lens settings, orientation, and coordinates | How a camera recorded the image and, when location was enabled, where it may have been taken | Check location and time for details you do not want to disclose publicly; retain useful capture data when needed. |
| XMP | Software name, description, editing history, keywords, prompts, or generation parameters | What a workflow or application recorded as descriptive information about the file | Treat values as editable statements. A software or prompt field alone does not establish authorship. |
| IPTC | Caption, creator, copyright notice, rights usage, and contact details | Attribution or licensing information supplied by a creator or publishing workflow | These details can be important for credit and permissions; decide whether to retain them before sharing. |
| C2PA Content Credentials | A manifest and structured provenance assertions associated with the image | Information about recorded creation or editing steps, when a compatible credential is present | Presence is not an AI-authorship verdict. This viewer does not validate signatures or external records. |
| Display and file structure | Color profiles, orientation, transparency, and format-specific values | Details some software uses to display the image as intended | These values may be functional rather than personal; do not assume every field is sensitive or safe to discard. |
This order is a review aid, not a risk score. What matters depends on the audience, the reason you are sharing the image, and whether you need to preserve a record of its source.
GPS coordinates can reveal where a photo was taken; timestamps can add context about a routine; device, author, and private-note fields may disclose details that are not visible in the picture. Review each value before sharing. Creator, rights, and provenance information can also be important to preserve for attribution or recordkeeping.
Metadata is stored differently across image formats and export workflows. Saving, editing, converting, or sharing a photo may preserve some fields while rewriting or dropping others. A viewer can also recognize only the containers and field layouts it supports. For a useful comparison, inspect the exact file copy you plan to send and note whether it has been edited or exported since the original was created. The report describes that copy, not every earlier version in its history.
The report is limited to supported metadata fields and file structures. It is not a forensic scan, AI-authorship detector, pixel-watermark detector, or credential signature verifier. A field can be absent, rewritten by an app, or stored in a layout this tool does not recognize. An empty report is not proof that a file has no metadata or provenance information.
Need to clean supported fields after reviewing them? Open the metadata remover. It creates a separate copy and leaves the original unchanged.
This viewer reports supported EXIF, GPS, XMP/IPTC, text, and recognized embedded credential fields found in a selected image. It does not inspect every possible file record.
No. Inspection runs locally in your browser. This page does not modify the selected image or create a cleaned copy.
No. Metadata can provide clues about file history, but fields can be missing or changed. This viewer does not determine authorship or detect pixel-level watermarks.
No. It means no supported fields were reported in the layouts this implementation recognizes. Other tools may expose different information.
A screenshot is normally a new image rather than the original camera file, so it should not be expected to retain all of the original EXIF or provenance fields. It may have metadata of its own; inspect the screenshot you intend to send.
It depends on the app, settings, version, and sharing method. Sending as a photo can behave differently from attaching a file. Inspect the actual saved or received copy because app behavior can change.
Some services process uploaded images, but the exact result varies and can change. This viewer checks the local file you select; it cannot inspect the platform’s stored or published copy.
Viewers can differ in supported formats, containers, and parsing rules, and apps can rewrite metadata during export. This report lists only fields this implementation recognizes; a missing value is not proof that no other metadata exists.
No. It can report recognized credential data in a supported file, but it does not verify signatures, fetch external manifests, or establish the truth of an assertion.