Read the Metadata of Several Photos at Once

What opening several is for

One photo at a time answers "what is in this file". Several answers a different question, and usually a more pressing one: which of these am I about to share, and which of them know where I was. The filmstrip marks every photo that states coordinates, so the answer is a glance rather than fifty separate readings. The map below puts the same information on a world outline, drawn in the page.

Two ceilings, because there are two ways to run out

Fifty photos, and half a gigabyte between them, whichever is reached first. Fifty pictures from a phone come to a couple of hundred megabytes and are fine; fifty scanned TIFFs at the single-file ceiling would be over three gigabytes and would take the tab with them. A count on its own is not a limit and neither is a total, so both are checked and a refusal says which one it was.

What can be done to all of them, and what cannot

Every JPEG that carries something to remove can be copied without it — EXIF, XMP, IPTC, the colour profile and comments spliced out of the bytes, every pixel left where it was, delivered as one archive. Nothing else can. Taking metadata out of a HEIC, PNG, WebP, AVIF, TIFF or GIF means redrawing the image, which changes it, and that is a cost worth confirming one photo at a time rather than for fifty at once behind a single button.

Questions about opening several

How many photos can I open at once?

Fifty, or half a gigabyte between them, whichever comes first. If a drop goes past either, the ones that fit are opened and the rest are reported with the reason, the count or the total. You are told which rule you hit rather than that some files were skipped.

Can I drop a folder instead of files?

No. What a browser hands over when you drop is a list of files, and this workspace does not walk a tree looking for more. Select the photos inside the folder instead; a normal multiple selection works, and so does dragging several at once.

Are the photos uploaded to read them?

No. Every file is read in your browser, and only the bytes that hold metadata are read at all for most formats. Nothing is sent anywhere — not to read them, not to draw the map, and not to build the CSV.

Can I get the results out as a spreadsheet?

Yes. The CSV export writes one row per photo, with a fixed set of columns: camera, lens, capture time, exposure, coordinates, tag count. That is a shape a spreadsheet can sort and filter. The complete tags, grouped as the table shows them, come out as JSON alongside it.

By file format

HEIC metadata viewer: Open a HEIC or HEIF and read its EXIF, GPS and Apple maker notes in the browser, even where the browser cannot display the image. Nothing is uploaded.
PNG metadata viewer: PNG has no EXIF segment. See the tEXt, iTXt and eXIf chunks a PNG is actually carrying, read locally in your browser. Nothing is uploaded.
WebP metadata viewer: WebP stores metadata in RIFF chunks, and only in its extended form. See what a WebP is carrying, read locally in your browser. Nothing is uploaded.
TIFF metadata viewer: TIFF is where EXIF came from. Read a TIFF's image file directories, tags and byte order in the browser, even though no browser can display one. Nothing is uploaded.
AVIF metadata viewer: AVIF uses the same container as HEIC and the opposite licensing, which is why your browser can display one. Read its metadata locally. Nothing is uploaded.
GIF metadata viewer: A GIF has no EXIF and no colour profile. See the comment and application extension blocks it does carry, read locally in your browser. Nothing is uploaded.
RAW metadata viewer: Most raw files are TIFF underneath, which is why their EXIF, GPS and maker notes can be read in a browser that cannot display one. Nothing is uploaded.