EXIF Viewer - Read Camera, Lens and GPS Data From Any Photo

Drop a photo and see everything the file is carrying: camera, lens, shutter, aperture, ISO, the date the shutter fired, and the GPS coordinates if they are still there. Nothing is uploaded. The bytes are read in your browser and the photo never leaves your device.

An empty result is the normal result. WhatsApp, Instagram, Facebook and X strip metadata when you upload, and screenshots never had any to begin with. If nothing comes back, the file was almost certainly stripped before it reached you.

Drag & Drop your photos here

or

From my Computer
By URL
From Google Drive
From Dropbox

Import from your computer, a public URL, Google Drive, or Dropbox.

JPG, PNG, WebP, TIFF, HEIC, AVIF, GIF, BMP - up to 100 MB per file

🔒 100% processed on your device ⚡ No upload, no network calls 🗑 Files are never stored on a server
Options

Common shows the tags people actually look for. All tags adds every named tag plus a raw dump with tag numbers and types.

Decimal is what a map search box wants. DMS is how the coordinates are actually stored in the file.

EXIF, XMP, IPTC, the ICC profile name, JPEG comments and PNG text chunks, straight from the raw bytes. Changing an option above re-renders what is already on screen. Your files are never read a second time.

Nothing here is changed, re-encoded or uploaded. To remove metadata rather than read it, use the EXIF remover.

Most photos that arrive through WhatsApp, Instagram, Facebook or X carry no EXIF at all, because those platforms strip it on upload. Screenshots never had any. An empty result almost always means the file was stripped before it reached you, not that the tool failed.

GIF and BMP cannot store EXIF at all. PNG stores EXIF only in the newer eXIf chunk, so most PNG files have none. Compressed PNG text chunks are read only where your browser supports DecompressionStream.

MakerNote is vendor specific and undocumented, so it is reported by size only and never decoded here. Decoding it wrongly would print fiction.

HEIC and AVIF metadata is read straight from the container. The picture is not decoded, so the preview comes from the embedded thumbnail when the file has one.

Dates come from the camera's own clock and time zone setting, which is often wrong. They are printed exactly as written in the file and never converted to your time zone. GPS coordinates are as recorded by the device, and accuracy varies from a few metres to a few hundred.

Editing a photo in almost any app rewrites or drops parts of the EXIF block. Absent tags do not mean the photo is fake.

Everything is processed locally in your browser. Nothing is uploaded to our servers.

This EXIF viewer opens the metadata block hidden inside a photo and prints it in plain language: the camera and lens that took it, the shutter speed, aperture and ISO, the exact moment the shutter fired, the orientation tag, and the GPS coordinates if they are still in the file. It reads the raw bytes in your browser, so nothing is uploaded and nothing is re-encoded. Drop a file from a camera, a phone, a scanner or a download folder and the answer appears immediately, with no button to press. It sits in the image metadata tools group alongside the EXIF remover, the DPI checker and the image info reader.

Here is the part most viewers never tell you: an empty result is the normal result. WhatsApp, Instagram, Facebook and X strip metadata the moment you upload, and a screenshot never carried any to begin with. So this page is built to explain a blank answer rather than shrug at it, and it still shows the XMP packets, IPTC fields, colour profile and PNG text chunks that often survive when EXIF does not. If you want the opposite job, removing what is there before you share a picture, use the metadata remover. If your file is a HEIC from an iPhone and another app refuses to open it, convert it first with HEIC to JPG. Everything here runs beside the rest of the image tools, including the government photo tools and the format converters.

8
Formats recognised by magic bytes
5
Metadata standards read per file
0
Bytes sent to any server
100 MB
Per file, read in small slices
🔍

Straight From the Bytes

The file is parsed as raw data, never drawn onto a canvas. Canvas discards metadata, which is why so many browser tools quietly report less than the file actually holds.

💬

Explains an Empty Result

No EXIF is the commonest outcome of all. Instead of a blank panel you get the reason, plus whatever XMP, IPTC, colour profile or PNG text did survive.

📍

GPS Two Ways

Coordinates appear as decimal degrees for pasting into a map box and as degrees, minutes and seconds, which is how the file actually stores them.

🔒

Nothing Leaves the Device

There is no upload, no queue and no third party script. Photos with location data are exactly the files you should never hand to a website, so this one does not ask.

How to Read a Photo's EXIF Data

Four steps, and the first one is the only one that needs you. There is no Read button because the file is parsed the moment it arrives.

📤

1. Add the Photo

Drag a file in, pick one from your computer, or pull it from a URL, Google Drive or Dropbox. Several at once is fine.

2. It Reads Itself

The format is identified from its first bytes, the metadata block is located, and the tags are decoded. No button, no waiting.

📋

3. Choose the Detail

Common shows the tags people look for. All tags adds every named field plus a raw dump with tag numbers and types.

💾

4. Copy or Export

Copy the whole report to the clipboard, or download it as a plain text file covering every photo you loaded.

Read a Photo's EXIF Now

What This EXIF Viewer Reads From Each Format

There is no before-and-after picture here, because nothing about your photo is changed. What varies is where each format keeps its metadata and how much of it survives. This is the capability map, taken from the shipped parser rather than from a specification.

Format EXIF is stored in EXIF read Also read Thumbnail Usual outcome
JPEG APP1 marker segment Full XMP, IPTC, ICC name, JFIF density, Photoshop 8BIM, comments Browser or IFD1 Rich if straight from a camera, empty if it came through a social app
PNG eXIf chunk, PNG 1.5 and later Full tEXt, iTXt, zTXt, pHYs, tIME, iCCP Browser Almost never has EXIF, often has text chunks naming the editor
WebP EXIF chunk inside the RIFF container Full XMP chunk, ICC profile chunk Browser Usually empty, because most WebP files are re-encodes made for the web
TIFF The file's own IFD0 Full XMP, IPTC, resolution tags, scanner fields IFD1 if present Nearly always populated, and the IFD often sits at the far end of the file
HEIC and AVIF Exif item located through the meta box Full Container brands and item list Embedded EXIF thumbnail only Rich on an iPhone original, and the picture is never decoded
GIF and BMP Nowhere, the formats have no EXIF container None to read Format and pixel dimensions Browser Reported as unsupported by the format, which is not the same as stripped

Read from the shipped parser, not from a wish list. Every row above is a code path in the tool on this page. Where a format cannot carry EXIF the result says so explicitly, because "not supported" and "stripped before it reached you" are two very different answers to the same blank panel. To remove what the table finds rather than read it, use the EXIF remover, and for resolution tags on their own see the DPI checker.

EXIF Viewer: Everything Your Photo Is Quietly Recording

Every time a camera or a phone takes a picture it writes a second, invisible document into the same file. That document is EXIF, and it can name the camera body, the lens, the shutter speed, the aperture, the ISO, the white balance, the firmware version, the body serial number, the second the shutter fired, and the latitude and longitude where you were standing. An EXIF viewer is simply a reader for that document, and this one reads it out of the raw bytes rather than through the browser's image decoder, because decoding a picture throws the metadata away.

The standard behind all of this is published by CIPA, the Camera and Imaging Products Association, as DC-008, and the structure it defines is borrowed from TIFF: a small table of tags, each with a type and a count, chained into sub-tables for exposure data and location data. That is why a JPEG, a TIFF, a WebP and a HEIC can all carry the same tag numbers even though the files look nothing alike from the outside. The Exif specification overview on Wikipedia is a readable summary of the tag structure and its version history if you want the technical background before the tags below start making sense.

What this page adds over a plain tag dump is honesty about the blank case. Most photographs that reach a normal person have been through at least one platform, and platforms strip metadata on upload. So this reader treats "no EXIF found" as a designed answer with a reason attached, and it still surfaces the XMP packet, the IPTC caption fields, the ICC colour profile name and the PNG text chunks that frequently outlive the EXIF block. When you want to remove that information instead of reading it, the EXIF remover strips it without re-encoding your picture. For resolution and print size on their own, the DPI checker is the narrower tool, and for format, colour depth and file integrity there is image info.

⚖️EXIF Viewer vs the Other Ways to Check a Photo

Approach Shows the full tag set What it costs you
This browser EXIF viewer Yes Nothing. The file is read locally and never uploaded.
Windows File Properties No Shows a curated handful of fields and hides GPS behind extra clicks.
macOS Preview inspector Partly Good on Apple formats, thin on XMP and IPTC, no raw tag numbers.
Phone gallery info panel No Usually four or five fields, and often a map you did not ask to load.
Upload-based EXIF websites Yes Your photo, and its coordinates, land on somebody else's server.
Desktop ExifTool command line Yes The most complete option, and an install plus a terminal to learn.
Reading the file in a hex editor Partly Total control, and you decode every rational number by hand.

The honest gap is the last row but one. A command line tool like ExifTool decodes vendor MakerNote blocks that no browser tool can, because those formats are undocumented and reverse engineered per camera brand. This page reports MakerNote by size and refuses to guess at its contents, which is the difference between a tool that is quiet about its limits and one that prints fiction. For everything the public standard defines, a browser reader is complete, and it has the advantage that a photo with GPS coordinates never leaves your device. If you also need to change the picture rather than inspect it, the image resizer and the crop tool sit in the same silo.


🔎When Reading the EXIF Is the Right Move

📷

Learning From Your Own Shots

The frame you liked recorded its own settings. Shutter, aperture, ISO, focal length and exposure compensation are all sitting in the file, so you can repeat what worked instead of guessing.

📍

Checking What You Are About to Share

Before a photo goes on a marketplace listing or a public post, look at the Location tile. If it says yes, the coordinates are usually the exact spot you were standing, including your own front door.

📄

Verifying a Photo Someone Sent You

Date taken, camera model and software fields help establish whether an image is an original or has been through an editor. They are evidence, not proof, and the page says so plainly.

🔧

Debugging a Sideways Photo

When an upload keeps appearing rotated, the Orientation tag is almost always the answer. Reading its value tells you whether the fault is the file or the software displaying it.


📦When There Is Nothing Left to Read

📱

It Came Through a Messaging App

WhatsApp, Instagram, Facebook and X remove metadata during upload. A photo forwarded three times has been stripped three times. The file is fine, the record of its origin is not.

🖼️

It Is a Screenshot

A screenshot is generated by the operating system, not by a camera, so there was never an exposure or a location to record. Expect dimensions and a colour profile and nothing else.

🎨

It Was Exported by an Editor

Save-for-web settings in most editors drop metadata deliberately to shrink the file. Sometimes a Software tag or an XMP packet survives, which this reader will still show you.

📋

The Format Cannot Store It

GIF and BMP have no EXIF container at all. That is reported differently from a stripped file on purpose, because "never had any" and "someone removed it" mean opposite things.


Why Read EXIF Here Rather Than Anywhere Else

🔒

Geotagged Photos Never Upload

The single worst file to hand to a stranger's server is one that contains your coordinates. This reader never sends it. Compare that with any site that asks you to upload first and report second.

🧠

It Reads More Than EXIF

XMP packets, IPTC caption and byline fields, the ICC colour profile name, JPEG comments, Photoshop resolution blocks and PNG text chunks are all parsed and grouped, not just the EXIF table.

Large Files Stay Fast

A 90 MB scan is not loaded into memory. The reader takes a small slice, finds the metadata offset and reads a window there, so a huge TIFF answers about as fast as a phone snapshot.

💬

Nothing Is Invented

Damaged tag tables produce a partial result and a note. Vendor MakerNote blocks are reported by size and never decoded. You get what is in the file, labelled honestly, or you get told why not.


What the EXIF Viewer Actually Does

  • Identifies the real format from the file's first bytes, so a PNG renamed to .jpg is still handled correctly.
  • Reads EXIF from JPEG APP1, PNG eXIf chunks, WebP EXIF chunks, TIFF IFD0 and the Exif item inside HEIC and AVIF containers.
  • Decodes the full tag table including the Exif sub-IFD, the GPS sub-IFD, the interoperability IFD and the thumbnail IFD.
  • Turns coded values into readable ones: 1/250 s, f/1.8, 24 mm with the 35 mm equivalent, and named strings for flash, metering and white balance.
  • Shows GPS as decimal degrees and as degrees, minutes and seconds, with altitude and the UTC timestamp when they are recorded.
  • Groups every result into Camera and Exposure, Image, Date and Time, Location, Software and Copyright, Description and IPTC, XMP and Other.
  • Offers an All tags mode that adds every named field plus a raw dump with hexadecimal tag numbers, types and counts.
  • Handles malformed metadata without crashing: bounds are checked, chains are capped, and a damaged block returns what it can with a warning.
  • Reads several files at once and exports one combined plain text report, or copies the whole thing to the clipboard.
  • Works with no network activity after the page loads, so it keeps working on a plane or on a train through a tunnel.

🔢How to Use the EXIF Viewer

  1. Add one photo or several Drag files onto the drop zone, or use the split button to pull them from your computer, a public URL, Google Drive or Dropbox. JPG, PNG, WebP, TIFF, HEIC, AVIF, GIF and BMP are all accepted, up to 100 MB each.
  2. Read the six summary tiles first Camera, lens, date taken, dimensions, file size and location give you the answer in one glance. If Location says yes, that is the line worth acting on before you share the picture anywhere.
  3. Switch to All tags when you need depth Common mode shows the fields people look for. All tags adds every named field and a raw dump with tag numbers, which is what you want when you are comparing two files or chasing an unusual field.
  4. Copy or download the report Copy All puts the full text on your clipboard. Download Report writes a plain text file covering every photo you loaded, in the detail level and coordinate format you currently have selected.

⚙️Technical Notes and Honest Limits

Two limits are worth stating in the open rather than in a collapsed panel. First, MakerNote is not decoded. Camera makers use private, undocumented layouts inside that tag, and decoding one brand's format against another's would print confident nonsense, so it is reported by byte count only. Second, dates and coordinates are shown exactly as the file records them, with no conversion to your time zone, because a camera's clock is frequently wrong and correcting it silently would make the tool less truthful, not more.

🗎 Why the file is read in slices instead of all at once

Metadata lives in a small region of a file, but not always at the beginning. A JPEG keeps it near the front, while a great many TIFF writers, scanner software especially, append the tag table after the image data. Loading a 90 MB scan into memory to read 4 KB of tags would be wasteful and slow, so the reader takes a small opening slice, finds the offset it needs, and then reads a window at that position. Peak memory stays roughly constant no matter how big the file is.

🖼️ Why HEIC and AVIF show a different kind of preview

Metadata in these formats sits in an Exif item that the reader locates by walking the container's box structure, which needs no decoder at all. Displaying the picture is a separate problem: most desktop browsers cannot decode HEIC, and pulling in a multi-megabyte decoding library to draw a small preview would be a poor trade on a page about reading bytes. Instead the preview comes from the thumbnail already embedded in the metadata, which most phone photos carry. If there is no embedded thumbnail you get the format name and the tags, which is what you came for.

🔧 What happens when the metadata is damaged

Broken EXIF is common, usually because a file was truncated in transfer or written by software that got a length wrong. Every offset and count is checked against the size of the block before anything is read, the chain of tag tables is capped so a self-referencing pointer cannot loop forever, and a failure returns whatever was parsed successfully along with a note saying the block is partly damaged. One damaged file never stops the others in a batch, and the tool never throws away a good partial answer just because the end of the block was unreadable.

🔐 What EXIF can and cannot prove

EXIF is written by the device and can be edited afterwards by anyone with the right tool, including this site's own metadata remover. A date and a camera model are useful supporting evidence and nothing stronger. Equally, missing tags are not suspicious on their own: almost every editor rewrites or drops parts of the block on save, and every social platform strips it. Treat the presence of consistent metadata as weak positive evidence and its absence as no evidence at all.


💡Real Situations This Page Handles

01

A seller in Jaipur photographs a scooter for a listing and wants to be certain the pictures do not carry the address it is parked at. The Location tile answers in one glance, and the EXIF remover clears it before upload.

02

A student submits an assignment photograph and the portal keeps showing it rotated. Reading the Orientation tag shows the file is tagged for rotation and the portal is ignoring it, which points straight at re-cropping the image as the fix.

03

A photographer compares two frames of the same scene to work out why one is sharper. All tags mode shows one was shot at 1/60 s and the other at 1/250 s, which settles it without opening a desktop editor.

04

A journalist receives a forwarded image and finds no EXIF at all. The result explains that messaging apps strip metadata on upload, so the blank is expected rather than evidence of tampering, and the investigation moves on.


- WHO USES THIS -

Built for Everyone in India

Photographers checking their own settings, journalists checking somebody else's, buyers checking a listing photo, and anyone who has just realised their holiday pictures might be carrying a home address.

Photographers Journalists and Fact Checkers Students and Researchers Online Sellers Legal and Insurance Teams Privacy Conscious Users Photo Editors and Retouchers Web and App Developers

FAQs - EXIF Viewer

EXIF is a block of information a camera or phone writes inside the image file at the moment of capture. It can hold the camera make and model, the lens, shutter speed, aperture, ISO, focal length, white balance, the date and time the shutter fired, an orientation flag, a body serial number, and GPS coordinates. The picture and this record travel together in one file until something removes the record.

Because something almost certainly stripped it before the file reached you. WhatsApp, Instagram, Facebook and X all remove metadata during upload, and a screenshot never had any to begin with, since it was drawn by the operating system rather than captured by a lens. An empty result is the most common outcome on this page. The tool explains the likely reason and still lists any XMP, IPTC, colour profile or PNG text that survived.

No. The file is read as raw bytes inside your browser and no copy is sent to any server, which matters more here than on most tools. A geotagged photograph is precisely the kind of file you should never hand to a stranger's website, because the coordinates are usually the exact spot you were standing. Once the page has loaded, the reader keeps working with no network connection at all.

Yes, when the coordinates are still in the file. The Location tile answers yes or no immediately, and the Location group shows latitude and longitude as decimal degrees for pasting into a map, as degrees, minutes and seconds, and with altitude and the UTC timestamp where the camera recorded them. Accuracy varies from a few metres to a few hundred depending on the signal at the time.

EXIF is read from JPEG, PNG, WebP, TIFF, HEIC, HEIF and AVIF files. The format is identified from the file's first bytes rather than its extension, so a PNG saved with a .jpg name is still handled correctly. GIF and BMP are recognised too, but neither format has an EXIF container, so the result says the format cannot store it rather than reporting it as stripped.

Cameras rarely rotate pixels. Instead they set an orientation tag telling the viewer to rotate the image on display, and software that ignores the tag shows the photo the way the sensor recorded it. Reading the tag here tells you whether the file is tagged for rotation and the app is ignoring it, or whether the pixels themselves need rotating with an editor or a crop tool.

MakerNote holds manufacturer-specific data in private, undocumented layouts that differ by brand and often by camera model. Decoding one vendor's structure against another's would produce confident, wrong output, which is worse than no output. This reader reports MakerNote by byte count and leaves the contents alone. Desktop tools such as ExifTool decode many of these blocks through years of reverse engineering, and that remains the right tool for that particular job.

Not on its own. The device writes those fields, and anyone with the right software can edit them afterwards. Dates come from the camera's own clock and time zone setting, which is frequently wrong. Treat consistent metadata as weak supporting evidence, and treat missing metadata as no evidence at all, because almost every editor rewrites parts of the block on save and every social platform strips it entirely.

Use the EXIF remover, which is the companion tool to this one. It strips the metadata by rewriting the file container rather than re-drawing the picture, so your image quality is untouched and the pixels come out byte for byte identical. It also verifies the result by running this same reader over the finished file, so you can see that nothing was left behind rather than taking it on trust.

EXIF is written by the camera and describes the capture: exposure, lens, time and location. IPTC is an older editorial standard carrying caption, byline, credit, keywords and location names, and is common in press and stock photography. XMP is an XML packet used by editing software for its own settings and rights information. A single file can carry all three, and this reader groups each one separately.

No. The file is opened for reading only and never written back, so the original is exactly as it was when you dropped it in. Nothing is drawn onto a canvas either, which matters because a canvas round trip discards metadata and re-encodes the picture. That is why several browser-based readers report fewer fields than the file actually holds. Here the bytes are parsed directly and left alone.

See What Your Photos Are Carrying

Camera, lens, exposure, date and GPS, read from the raw bytes in your browser. Nothing is uploaded, nothing is changed, and an empty result gets an explanation instead of a shrug. When you are ready to strip what you found, the EXIF remover does it without re-encoding the picture.

Open the EXIF Viewer