Skip to content
KBSize

View the EXIF data in a photo

Read what the camera wrote into a photo: model, lens, shutter, ISO, the second it was taken, and the coordinates if they are still there. Nothing is uploaded.

Choose a photo and everything stored inside it is listed here, in this browser. Nothing is uploaded.

What this photo is carrying

Camera

Waiting for a photo.

Exposure

Waiting for a photo.

Dates

Waiting for a photo.

Location

No location is stored in this file.

Shutter count

No shutter count is stored in this file.

Software

Waiting for a photo.

Your photo is never uploaded. It is read in this browser with the standard file API, and the cleaned copy is built here too, so there is no server involved at any point.

What a photo is carrying that you cannot see

A picture is not only pixels. Every camera and nearly every phone writes a block of notes beside the image — the body it came from, the settings it used, the moment the shutter opened and, if location services were on, the point on the earth it was standing on. None of it shows when you look at the photograph, and all of it travels when you send the file as a file.

This page reads that block and lays it out as cards: camera, exposure, dates, location, shutter count, software. Where a field is missing the card says so instead of leaving a blank you have to interpret. What you want is a decision — is this file safe to post — and a wall of forty raw tags is not one.

The photo is read here, not on a server

Most online metadata viewers are an upload form. To find out whether a file is safe to share you first hand it to a stranger in full, coordinates included, and then hope the retention promise underneath the button is true.

This one has no upload endpoint to send it to. The parser is JavaScript that arrived with the page, the browser’s own file reader turns your choice into bytes in this tab, and the bytes go nowhere else — your photo is never uploaded. Open the network panel while you choose a file and watch: nothing carrying the image is requested. Closing the tab is the entire deletion policy.

Coordinates, and why the map is a link

A camera does not store “51.5, −0.125”. It stores three fractions per axis and a separate letter for the hemisphere, which is the detail sloppy readers get wrong and park a London photograph in the wrong half of the world. The report does the arithmetic, shows the decimal degrees, and offers an OpenStreetMap link.

It is a link rather than a map that draws itself. An embedded map would request a tile server with the coordinates out of your file — very often a home address — the instant the report appeared, which is the exact disclosure somebody came here to avoid. Nothing is requested until you decide to click.

HEIC, screenshots, and files that come back empty

An iPhone photo is usually HEIC, and HEIC keeps its metadata inside a container this parser does not decode. The tool names the format and stops there rather than inventing a camera model for it. Export or share the picture as JPEG — “Most Compatible” on iOS, or Preview’s JPEG export on a Mac — and that file reads in full.

A photo that comes back with nothing in it is usually a photo that has already been through something. Social networks re-encode on upload, a screenshot was made by the operating system and never had a camera block, and a chat app that compresses has already dropped it. An empty report is an answer, not a broken viewer.

What each field in the report is telling you

The cards are the short version. These are the fields that say something about you or about the camera body, rather than about the photograph.

FieldWhat it isWhy it is on a card
GPSLatitude / GPSLongitudeWhere the camera was standing when the shutter openedYour address, if the picture was taken at home
DateTimeOriginalThe moment the exposure was made, to the secondWhen you were somewhere — and, by omission, when you were not
Make / ModelThe camera or the phone that produced the fileTies photographs posted under different names to one device
BodySerialNumberThe serial number of the camera body itselfTies every photograph that body has ever taken to each other
ImageNumberHow many times the shutter has fired, on the bodies that write itThe actuation count a used-camera listing is asked for
ThumbnailA second, smaller copy stored beside the pictureOn a cropped photo it can still show what was cut out

Common questions

Does my photo get uploaded to view its EXIF data?

No. The file is read in your browser and never leaves your device — there is no upload endpoint on this site to send it to. You can watch the network inspector while you choose a photo and see that the image bytes are not requested from anywhere.

What file types can it read?

JPEG, PNG, WebP and TIFF, including GPS and a shutter count when the camera wrote one. HEIC from an iPhone is recognised and reported as not parsed rather than guessed at; export it as JPEG and that file reads in full.

Why does my photo show no EXIF data at all?

Because something already removed it. Facebook, Instagram and X strip metadata when you upload, a compressed chat photo has been re-encoded, and a screenshot never had any. That is the expected result for those files, not a failure of the viewer.

Can I see where a photo was taken?

If the coordinates are still in the file, yes: they appear as decimal degrees with a map link you choose to open. If they were stripped, no tool can recover them from that copy — they were deleted, not hidden.

What is the smallest size an image can be compressed to?

There is no hard floor, but below roughly 10 KB a photograph has to become very small in pixel terms — around 200 by 150 — before it fits. Line art and signatures go far lower because they contain much less detail to store.

Everything else on the site