EXIF data is the metadata block embedded in a JPEG's APP1 segment, and IrfanView can read and display it directly without uploading the photo. To view EXIF data in IrfanView, open the JPEG in the program and use its built-in metadata dialog, which parses the local file in memory and shows camera make and model, capture time, exposure settings, lens data, and — when present — GPS coordinates. Because the parsing happens on the local machine, the photo never leaves your computer. The same common fields are also what a browser-based EXIF viewer reads when you open the same JPG in a tab, which is useful when you don't have IrfanView installed, are working on a Mac or mobile device, or want a quick check without launching a desktop application. Both approaches work on the same CIPA-published EXIF specification, so the list of recognized fields overlaps, even when the table layout, export options, and storage model differ.
View EXIF Data in IrfanView
IrfanView is a free Windows image viewer that has been distributed for over two decades, and one of its longstanding features is the ability to display EXIF metadata alongside the open picture. Under the hood, the program looks for the JPEG's APP1 segment, validates the "Exif" identifier and TIFF header, and walks the IFD0, Exif, and GPS directories using the same CIPA-defined tags that every compliant reader uses. The parsed values are then surfaced in a metadata dialog so you can see the camera make and model, the date and time the picture was taken, the exposure settings, the lens model, and any GPS coordinates that were written at capture time.
Since the parsing happens against the file already on disk, no upload is involved, and the photo is not modified by simply reading it. The general workflow is the same as for any EXIF-compliant viewer: open the picture, trigger the metadata view, and read the fields. Concretely, the steps look like this.
- Launch IrfanView and use its file picker to open the JPEG whose metadata you want to read.
- Open the metadata panel from the program's interface — IrfanView exposes EXIF data through a dedicated dialog reachable from the main menu or the toolbar, depending on the version.
- Read the camera, capture, lens, and any GPS fields the dialog surfaces, paying attention to coordinate values if the photo was taken on a phone or GPS-enabled camera.
- Close the JPEG file when you are done; the parsed values stay in the dialog and are not saved back to the file unless you explicitly export them.
If you only need a quick check and IrfanView is not installed, the same standard fields can be read by a browser-based EXIF Viewer without launching a desktop program.
When a Browser Tool Is the Easier Choice
There are several situations where reaching for IrfanView is awkward, and a browser-based reader is faster. IrfanView is Windows-only, so Mac and Linux users cannot install it at all; a browser tab is the simplest way to check a JPEG's metadata on those platforms. Mobile users on a phone or tablet often cannot run a desktop EXIF viewer, while a browser works on any device with a modern web engine. A browser tool also avoids downloading and updating an installer, which matters when you only need to peek at one file's metadata occasionally and do not want to add another program to a system that already has plenty.
Privacy is another reason. Both IrfanView and a browser-based reader run locally, so neither sends the JPEG to a server while parsing it. The difference is that a browser tab does not require an executable to be installed, and the parsed values stay in the current tab rather than being added to a desktop application's recent files list, settings, or jump lists. If you only want to confirm what a photo contains before sharing it, opening a single tab is often less friction than launching a full program, waiting for it to load, and then closing it again.
There is also a portability benefit. A browser-based reader can be opened on any device with a browser, including a borrowed laptop, a work terminal, or a friend's phone, without leaving traces behind. That makes it useful for quick checks on a single image — confirming whether a JPEG still has GPS coordinates, or whether a screenshot's metadata has been stripped by a messaging app — without committing to a software installation.
View EXIF Data in Your Browser
When you do not have IrfanView available, or you want a quick read of a JPEG without installing anything, the EXIF Viewer reads the same standard fields directly in your browser. The four steps below cover the entire workflow.
- Choose a local JPG or JPEG file up to 25 MiB. The tool reads the file's bytes from your device; it does not upload the image to a server.
- Review the recognized EXIF rows in the table, including camera make and model, capture time, exposure settings, lens model, and any GPS coordinates that were embedded in the file.
- Examine the GPS latitude and longitude carefully before sharing the photo or a screenshot of the metadata, because coordinates can disclose the precise location where the picture was taken.
- Switch to a full desktop metadata tool if you need unsupported formats, maker notes, or forensic evidence, because the browser reader is intentionally limited to common JPEG EXIF fields.
Each step is shown in plain language so the entire workflow fits in a short session: pick a file, scan the table, decide whether to share, and escalate to a heavier tool only if the bounded allowlist is not enough.
What the EXIF Viewer Detects
The browser tool follows the CIPA Exif 2.3 specification and only decodes a documented allowlist of common tags, validated against ExifTool's official tag table. Anything proprietary or out of range is rejected rather than guessed, so the parsed values are always paired with the tag names the spec defines. The following table shows the groups of fields the tool can surface when they are present in the JPEG you upload.
| Field group | Example fields | What it tells you |
|---|---|---|
| Camera identity | Make, model, software | Which device produced the file and the firmware or app that wrote it |
| Capture time | DateTimeOriginal, DateTimeDigitized, DateTime | When the shutter was pressed, when the scan finished, and when the file was last modified |
| Exposure settings | ExposureTime, FNumber, ISOSpeedRatings, FocalLength | How the picture was exposed |
| Lens and orientation | LensModel, Orientation, PixelXDimension, PixelYDimension | Glass used, which way is up, and the image's pixel size |
| Location | GPSLatitude, GPSLongitude, with N/S and E/W references | Where the camera was, with signed hemispheres applied |
Coordinates are converted from degrees, minutes, and seconds into signed decimal degrees using the stored N/S and E/W references, so a value of 51 degrees 30 minutes 26 seconds North becomes about 51.5072. A file may contain none, some, or all of these fields, and a stripped or never-populated tag simply produces an empty cell in the output table rather than an error. The reader also handles both little-endian and big-endian TIFF byte order, inline and offset values, ASCII, SHORT, LONG, RATIONAL, signed values, and the Exif and GPS subdirectories, so JPEGs from different cameras are parsed consistently.
Eight independent standard fixtures pin the core tag identifiers and types, and safety limits reject malformed segment lengths, directories with excessive entries, unsupported or oversized field counts, and offsets that point outside the selected file. Those guards are what let the tool stop at the first valid Exif APP1 segment and never execute any embedded metadata, which is meaningful when the file comes from an untrusted source.
When a Full Desktop Tool Is the Better Pick
The browser reader is intentionally bounded. It ignores proprietary maker notes, which are the per-vendor blocks that store detailed capture information on modern cameras, and it does not understand RAW, HEIC, PNG, WebP, video, or full XMP and IPTC containers. If you need any of that, the tool itself recommends moving to a maintained desktop application such as ExifTool, which keeps the full tag catalog and supports batch export, recursive directory scans, and command-line automation. For photographers who want a single program that can read everything in a folder at once, that desktop route is the right answer.
Forensic work is another boundary. Metadata is not proof of authorship, ownership, capture time, location, or authenticity: it can be missing, stale, edited, copied, or removed by messaging and social platforms. A bounded browser reader is fine for confirming what a JPEG contains before sharing it, but it should not be the basis for a claim about when or where a photo was taken. For chain-of-custody questions, preserve the original file and use a tool that exposes the raw bytes alongside the parsed values so the same input can be inspected again later.
There is also a coverage gap for very large files. The browser tool caps input at 25 MiB, which covers phone photos and most camera JPEGs, but a scanned plate or a stitched panorama can exceed that. In that case, the right move is either to pre-split the file with a tool that keeps the original bytes intact or to send it straight to a desktop reader that does not have the same size limit.
Privacy and GPS Coordinates
GPS metadata can disclose the precise location where a picture was taken, and that is the most privacy-sensitive part of EXIF. Both IrfanView and the browser EXIF Viewer will display latitude and longitude when they are present, so the safe step is to read them first and decide whether to strip them before posting. If you decide to remove them, do not just hide the field in a viewer — rebuild the file so the bytes themselves are gone. The companion EXIF Remover tool rebuilds the JPEG from its decoded pixels to drop the APP1 segment, which is the only way to be sure social and messaging platforms cannot recover the coordinates from the original upload.
The browser tool also keeps the byte-level work inside the current tab. The JPEG is read by JavaScript in the page, the fields are extracted, and the result is displayed without contacting a server. That matters when the photo contains sensitive content, because nothing about the image is shared with a third party just by opening it for inspection. The page never executes metadata and does not send the image to a server; the parsed values stay in the current tab until you close it.
One more thing to keep in mind is that EXIF timestamps can also leak information. Even when GPS coordinates are stripped, the DateTimeOriginal field can tell a recipient when the photo was taken, including the time zone if the camera was set to local time. If you want to share a photo without revealing when it was shot, you need to either rebuild the JPEG or run a metadata tool that lets you overwrite the timestamp with a chosen value before sharing.