An ExifTool Alternative for the Browser

Start with what ExifTool does better

Phil Harvey's ExifTool has been the reference implementation for image metadata for two decades. It reads and writes around two hundred file types, including every RAW format that matters, and it exposes essentially every tag individually rather than treating metadata as one block to keep or discard.

If your job involves any of the following, close this page and use ExifTool — nothing in a browser comes close:

• RAW files: CR2, CR3, NEF, ARW, DNG, ORF and the rest.
• Editing individual tags rather than removing everything — fixing a wrong capture date, setting copyright across a shoot, correcting GPS.
• Recursive batch work across thousands of files, with conditions and scripting.
• Reading proprietary maker notes in detail, including lens corrections and shutter counts.
• Anything that needs to run unattended, in a pipeline, or on a schedule.

Where a browser tool is the better fit

The trade is reach and immediacy against power. A web tool cannot script, but it also does not need installing, updating, or a terminal — and that matters more often than technical people assume.

• Nothing to install, including on a machine you do not administer or a phone.
• No command line, which is the actual blocker for most people who need this once.
• Verification built into the flow: the cleaned file is re-read and the result shown, rather than you running a second command to confirm.
• You see every field before deciding, instead of choosing flags first and inspecting after.
• Batch up to 25 files with a per-file result and a ZIP, which covers the common case without scripting.

The one thing this does that ExifTool cannot

Run on a phone. A significant share of metadata problems are phone photos being shared from a phone, and ExifTool is not an option in that moment. Neither is any desktop application.

That is a narrow advantage, but it is the one that decides which tool gets used in practice for the single most common case.

How the categories differ architecturally

Most tools in this space fall into four groups, and the differences that matter are structural rather than featural. The table below compares the categories rather than ranking brands — a specific product's behaviour can change, but the architecture it chose usually does not.

The row worth reading twice is the last one. A server-side web tool has to receive your file to process it. That is not a criticism of any particular service's integrity; it is a description of where the file goes, and it is the difference this site exists to avoid.

A reasonable way to use both

These are not mutually exclusive, and the honest recommendation for a photographer is to use both. Keep ExifTool for the library: bulk corrections, RAW work, anything scripted.

Use a browser tool at the moment of sharing — the one-off photo going to a marketplace listing or a stranger, especially from a device where installing something is not on the table.