ExifTool vs ExifVision: command-line power vs browser-local privacy

ExifTool is the reference implementation of photo metadata tooling. Written by Phil Harvey and maintained since 2003, it's a Perl command-line utility that reads and writes every metadata format that has ever existed in a camera file — EXIF, IPTC, XMP, MakerNotes for hundreds of camera bodies, GeoTIFF, ICC profiles, and dozens more. If you need to script batch operations across ten thousand RAW files, or extract a proprietary Nikon MakerNote tag that no other tool understands, ExifTool is the answer.

ExifVision is a browser-local metadata explorer built for a different job: giving anyone with a photo a fast, private, forensic-grade dossier — without installing anything, without a terminal, and without ever uploading the image.

## When ExifTool wins

- Batch automation. `exiftool -gps:all= *.jpg` strips GPS from every JPEG in a folder in one line. Wire it into a shell script, a Makefile, a CI pipeline. - Every tag under the sun. ExifTool parses obscure MakerNotes that no GUI covers — useful for camera repair, RAW conversion research, or forensic work on specific bodies. - Writing metadata back. ExifTool can add captions, copyright, GPS, and custom XMP fields. ExifVision only reads and removes; it does not author metadata. - Server-side pipelines. If you're processing images on a server (photo hosting, DAM, moderation), ExifTool is the workhorse behind the scenes.

## When ExifVision wins

- Privacy by construction. ExifVision runs entirely in your browser. The image never leaves your device — no upload, no server, no logs, no third-party analytics on your file. For journalists, activists, lawyers, and anyone handling sensitive material, that's non-negotiable. - Zero install. Open the site, drop a photo, get the report. No Homebrew, no Perl, no PATH surgery. Works on a locked-down work laptop, on a phone, on a Chromebook. - Human-readable forensics. ExifTool prints tag/value pairs. ExifVision turns them into a privacy score, a GPS Intelligence panel with reverse geocoding and nearby landmarks, an AI-assisted geolocation when GPS is absent, manipulation-detection heuristics (double JPEG compression, thumbnail mismatch, quantization anomalies, copy-move indications), and one-click scrubbing. - Comparison and batch review in a UI. Diff two photos side-by-side, or drop a folder to triage what needs cleaning. - Shareable dossiers. Export the whole analysis as JSON, CSV, TXT, or PDF for a report, a legal exhibit, or a story.

## Feature-by-feature

| Capability | ExifTool | ExifVision | | --- | --- | --- | | Read EXIF / IPTC / XMP | ✅ (exhaustive) | ✅ (all common tags) | | Read proprietary MakerNotes | ✅ (hundreds of cameras) | Partial | | Write / edit metadata | ✅ | ❌ (read + strip only) | | Strip metadata | ✅ (surgical, per-tag) | ✅ (GPS-only or all) | | Batch processing | ✅ (shell-native) | ✅ (in-browser batch route) | | GPS reverse geocoding | ❌ | ✅ (address, elevation, timezone, landmarks) | | AI geolocation when GPS is missing | ❌ | ✅ | | Manipulation / tamper heuristics | ❌ | ✅ | | Privacy score | ❌ | ✅ | | Install required | Yes (Perl + binary) | No | | Data leaves your device | Local by default | Never | | GUI | No (CLI + third-party wrappers) | Yes (web) |

## They're complementary, not competitors

The honest answer to "ExifTool or ExifVision?" is usually both. Photographers and DAM admins live in ExifTool. Investigators, reporters, and privacy-conscious end users want a dossier and a scrub button, not a Perl script — and they want the file to stay on their machine. ExifVision is designed for that second audience: everything ExifTool can tell you about a single photo, plus the forensic context, presented in a browser tab that never phones home.

If you already know ExifTool, keep using it for scripting and writing. Reach for ExifVision when you need a fast, private, presentable read on a specific image — or when you want to hand a non-technical colleague something they can drop a photo into and understand in ten seconds.