EXIF Viewer
Inspect EXIF, GPS, IPTC, XMP and ICC fields returned by the reader. Coverage depends on the file format and metadata structure.
Initializing the tool… Tool ready
Wait for the controls to become available before choosing or dropping files. If this takes too long, check your connection or script blocker and reload.
You can now select files or run checks. Your files are not selected or processed automatically.
What would you like to do?
Choose a file to view its returned fields and sharing checklist.
Switching tasks keeps the files and comparison selections in this page. It does not run a cleanup or upload images.
Try a licensed camera sample
Load a public example directly into this viewer. Nothing downloads until you click Load; existing files stay in this page. No photo upload.
Metadata-reduced, primary-image-only derivatives, not unchanged camera originals. Original-file results, editing refusals and licenses are in the linked report. These copies do not demonstrate shutter-count decoding or original-file compatibility.
Olympus OM-D E-M10
3,760,768 B · JPEG
Photo credit: tomasz przechlewski · CC BY 2.0
Source, license and test reportSony A7 IV (ILCE-7M4)
19,240,086 B · JPEG
Photo credit: Santhosh Notagar99 · CC BY 4.0
Source, license and test reportDrop your images here
or click to browse
Select JPEG, PNG, HEIC, TIFF or WebP; readable metadata depends on reader support
Local session only: up to 20 files, 30 MiB per file, 150 MiB total including copies. Re-encoding is limited to 40 megapixels. Files are processed sequentially and are not stored by this tool. Clear or leave this page to release them.
Reading diagnostics distinguish format limits, unreadable input and returned fields; a parse failure alone does not prove file damage.
CSV is UTF-8 with a BOM. Every metadata key and value receives a visible “text: ” prefix for text viewing in spreadsheets; CSV cells are therefore not raw values. JSON keeps the reader-returned fields and values without this prefix. Neither export covers all possible metadata.
All capabilities & limits
Selective EXIF cleanup · JPEG without re-encoding
Choose standard EXIF fields to remove. By default, keep the author, copyright, capture date, exposure settings and orientation. The source file is never overwritten.
EXIF only: XMP, IPTC, MakerNotes and embedded thumbnails remain and may contain personal information. Check the comparison below. Unsupported structures are rejected, not silently re-encoded. Other formats can use the separate re-encoding option.
Compare original and sharing copy
Add an original and the copy you plan to share to compare readable metadata.
Compare decoded dimensions, exact file sizes and synchronized close-ups of the two selected files.
Select the original and the recipient-downloaded copy above, then compare their bytes locally. A matching name or preview is not a file-identity check. Runs only when clicked, up to 30 MiB per file; no image upload.
Only parsed fields returned by this reader are compared. Removed means returned for the original but not for the sharing copy; it does not verify removal across all metadata containers. Missing fields do not guarantee that a file is safe to share. The presence list is a prompt for review, not a severity score. Zero GPS coordinates are valid location values.
Before-sharing review
Decide what to keep, remove or inspect next. This is a review checklist, not a safe-to-share verdict.
Metadata sources & raw-value differences
Inspect recognized EXIF, XMP and Photoshop/IPTC segments separately in JPEG, without merging their fields. Other formats keep the existing merged view.
JPEG only. Each physical segment is read independently. Extended XMP and other APP/COM segments are inventoried, not decoded here. Missing fields do not prove absence. At most 64 segments / 4 MiB of segment data; larger inventories are not inspected.
Download synthetic EXIF/XMP exampleRemove selected JPEG metadata containers
Delete whole selected segments without re-encoding. Nothing is selected by default. EXIF (including orientation), ICC color profiles, JFIF, Adobe decoder data and unknown segments are retained.
This can erase rights, captions, editing settings or auxiliary-image descriptions. Photoshop removal is NOT IPTC-only. EXIF GPS, MakerNotes, embedded EXIF thumbnails and unknown segments may remain. Coding-byte equality does not certify identical appearance or safe sharing. Multi-picture MPF and malformed JPEG structures are rejected.
Initializing the tool… Tool ready
Wait for the controls to become available before choosing or dropping files. If this takes too long, check your connection or script blocker and reload.
You can now select files or run checks. Your files are not selected or processed automatically.
Hands-on: why location can remain after EXIF cleanup
Run three real checks on a public synthetic JPEG. EXIF GPS and XMP GPS are separate sources; deleting one does not delete the other.
This experiment never reads or changes files in the viewer workspace above. It fetches only the fixed public sample after you click. Names, dates and GPS 0,0 are invented; this is not a real camera photo.
1. Read the original
Verify the sample SHA-256 and read its two location sources.
Not run
2. Remove EXIF GPS only
Keep XMP, EXIF author and date. Observe whether location is still readable.
Not run
3. Remove XMP and recheck
Remove all recognized XMP segments, including their creator credit. Recheck what remains.
Not run
A result is shown only after the actual reader runs. No selected location fields returned is not a complete privacy check: unknown segments, embedded/auxiliary images and visible content may remain. Coding-byte equality is not a guarantee of identical display, anonymity or camera compatibility. Real files need their own review.
Public fixture reference · CC0-1.0Inspect the file you plan to share
Select an image, review the GPS, date/time, camera and all-fields tabs, and note any owner, serial or Software values. Metadata is editable; a capture time without a UTC offset is not an unambiguous instant, and recorded coordinates are not proof of where someone was.
The viewer reads the selected file in your browser without uploading it for parsing. Format and field support vary: an empty tab or failed read does not prove that all metadata is absent. Compare the original with the actual exported or recipient-downloaded copy. JSON preserves the returned fields and values; spreadsheet-text CSV adds a visible text: prefix to metadata cells and is not a raw-value format. Neither is a complete forensic record. Local processing is not a guarantee of device security or anonymity.
In the cleanup task, preview which selected standard EXIF records can be removed before creating a copy. No-match and unsupported structures are explained before generation; other metadata sources remain a separate check.
Whole-container cleanup previews the exact segments and bytes to remove and the segments that remain. It does not interpret every segment or remove all personal information.
Remove individual files from this page without clearing the whole workspace. Disk files are not deleted. Missing comparison members must be reselected; names are never used to guess an original.
Find returned fields by original key, localized name or value. Search spans all merged fields of the current file, not every physical metadata source. Filtering does not narrow cleanup choices or full-field JSON/CSV exports. Selected-field exports require their own explicit selection.
Nothing is selected by default. Choose from the currently displayed fields; changing the search, category or file clears this selection. Nothing is uploaded or removed from the photo.
The comparison summary omits metadata values and file names. The full report includes both. Neither changes or uploads your photos.
Find comparison rows by change state and original or localized field name. Search matches names only, not metadata values; it stays in this page, not in URLs or saved settings.
Swap the comparison baseline and copy in one step. Files and generated-copy origins are not changed. Byte-check results, image-view controls and field filters reset; run the byte check again if needed.
Focus a batch on location, identifiers, dates or text. Failed reads remain visible as unknown, not negative results. This uses only the merged fields returned by the current reader.