Skip to main content

EXIF viewer online

View, search, and export metadata from your JPEG images. Supports batch viewing, GPS maps, and visual camera settings.

Free & unlimited
All processing happens in your browser. No data is sent to any server.

Every JPEG your camera or phone writes carries an EXIF block: which body and lens took it, at what shutter speed and aperture, at what ISO, on what date, and — if location was on — exactly where. This page reads that block with piexifjs inside your browser, groups it into image, camera-settings and GPS sections, names every tag it recognises and lists the rest by tag number so nothing is hidden. Drop several photos at once and each gets its own card with a preview. GPS coordinates are converted to decimal and shown with a location map and links. Exports are per file as JSON or CSV, or one JSON for the whole batch.

Key facts about EXIF viewer online

Key facts about EXIF viewer online
Parserpiexifjs, reading the APP1 EXIF segment out of the JPEG in this tab
FormatsJPEG only — .jpg and .jpeg. PNG, WebP, HEIC and camera raw files are not read
Size limit50 MB per file, checked before reading
BatchDrop or select several photos at once; each becomes its own expandable card with a thumbnail
Sections0th (image), Exif (camera settings), GPS (location) and 1st (thumbnail IFD)
Named tagsMake, model, lens make and model, body serial number, software, orientation, resolution, artist, copyright, date and time, date original, date digitized, shutter speed, aperture, ISO, exposure bias, focal length, flash, white balance, metering mode, exposure program, scene type, colour space and pixel dimensions
Unknown tagsAnything not in the name table is still listed, labelled by its numeric tag id, so a proprietary maker note field is visible rather than silently dropped
GPSDegrees-minutes-seconds rationals plus the N/S and E/W reference are converted to signed decimal degrees
Map previewA static map image is requested from staticmap.openstreetmap.de with the photo coordinates in the URL, plus outbound links to OpenStreetMap and Google Maps
Per-file exportJSON as a label-to-value object, or CSV with a Field and Value column, named after the photo
Batch exportOne JSON keyed by file name, containing every readable field of every loaded photo
CopyAny single field copies with one click; copy all puts every field as label: value lines on the clipboard

What happens to your file

The photo is read with FileReader and decoded by piexifjs inside this tab; the image bytes never leave your machine, and the JSON and CSV exports are built in page memory and downloaded locally. One thing does cross the network, and only when a photo actually contains GPS: the location preview is a static map image fetched from staticmap.openstreetmap.de, and that request carries the latitude and longitude in its URL. The photo is never sent, only the coordinates it contains, and only for the map thumbnail. If that is not acceptable, read the decimal coordinates in the table and avoid the map view.

About this tool

  1. 1

    Drop one photo or many

    Drag .jpg or .jpeg files onto the page or browse for them. Files over 50 MB are refused up front rather than failing halfway through.

  2. 2

    Read the summary first

    Each card leads with the fields people actually want: camera, lens, shutter, aperture, ISO and date. The full tag grid sits underneath.

  3. 3

    Open the full tag list

    Every tag found is listed under its section — image, camera settings, location and thumbnail. Tags with no friendly name appear by number, which is where maker-specific data shows up.

  4. 4

    Check for GPS

    If the photo has location, the coordinates are shown in decimal along with a map preview and links out to OpenStreetMap and Google Maps.

  5. 5

    Copy or export

    Copy one field, copy every field as text, or download JSON or CSV. With several photos loaded, the batch JSON export gives you one file keyed by photo name.

Specs & compatibility
Accepted extensions.jpg, .jpeg
Maximum file size50 MB per photo
Files at onceNo fixed cap; all are held in memory together
Metadata standardEXIF in the JPEG APP1 segment, TIFF-structured IFDs
Not readXMP, IPTC, ICC profile contents, and maker notes beyond their raw tag numbers
GPS outputSigned decimal degrees, plus altitude when present
ExportsJSON per file, CSV per file, JSON for the batch
NetworkNone, unless a photo has GPS and you view the map thumbnail
Browser supportAny modern browser, desktop or mobile
Cost / accountFree, unlimited photos, no signup
  • A photo with no EXIF at all has usually been through a messaging app or a social platform — most of them strip the block on upload.
  • The body serial number is a real tag and it is in the list: check it before publishing photos you would rather not have traced to your camera.
  • Date original is when the shutter fired; date digitized is when the file was written; date and time is the last modification. They differ on scanned and edited images.
  • If focal length looks wrong for the field of view, the lens was on a crop-sensor body — EXIF records the true focal length, not the equivalent.
  • Batch-load a shoot and export the batch JSON to get a single record of settings for every frame, which is the fastest way to review what you shot at.
  • Tags shown only by number are usually maker notes; the value is often an internal code rather than something meaningful.
  • To check whether an image you are about to publish is clean, run it through the EXIF remover and reopen the result here — an empty table is the proof.
  • Full EXIF tag list by section
  • Named camera, lens and exposure fields
  • Unknown tags shown by id
  • GPS as decimal degrees with map links
  • Batch loading with per-photo cards
  • Copy a field or copy everything
  • JSON and CSV export per photo
  • Batch JSON export
  • Finding out what camera, lens and settings produced a photo you like.
  • Checking whether an image you are about to publish still carries GPS coordinates.
  • Recovering the true capture date of a photo whose file timestamp has been rewritten.
  • Reviewing the settings across a whole shoot by loading the folder and exporting batch JSON.
  • Confirming a supplied image is an original camera file rather than a re-saved copy.
  • Documenting evidence about an image without uploading it to a third-party service.
No. The file is read locally with FileReader and the EXIF block is decoded by piexifjs inside this browser tab, so the image itself never leaves your machine and the JSON and CSV exports are generated locally too. The single network request the page can make is the static map thumbnail shown when a photo contains GPS: that URL carries the coordinates from the photo, not the photo. Skip the map view if even that is more than you want to share.
Because something stripped it, or it never had any. Most social networks and messaging apps remove the EXIF block when you upload or send an image, so a photo that came to you through one of them will usually be bare. Screenshots have no camera metadata to begin with, and many export pipelines drop it deliberately. If the file also opens with no camera or date information in your operating system preview, the block is genuinely gone.
No. The reader works on the APP1 EXIF segment of a JPEG, so only .jpg and .jpeg files are accepted. HEIC photos from an iPhone, PNG screenshots, WebP images and camera raw formats such as CR3, NEF and ARW all store metadata differently and are not supported here. For an iPhone HEIC, convert it to JPEG first — the conversion normally carries the EXIF block across.
As accurate as the fix the camera had. The EXIF GPS tags store latitude and longitude as degrees, minutes and seconds with a hemisphere reference, and the viewer converts that to signed decimal degrees, which typically resolves to a few metres. Accuracy degrades indoors, in cities and when a phone falls back to network positioning, and some cameras write the position of the last fix rather than of the shutter press.
They are tags that exist in the file but are not in the viewer name table — most often maker notes, the manufacturer private block where lens correction data, focus points and shooting-mode codes live. They are listed rather than hidden so you can see that data is present, but the values are internal codes that only the manufacturer software interprets reliably. The named fields above them cover everything standard.
Use the EXIF remover on this site, which strips the same block locally and lets you choose what to remove: camera identity, exposure settings, GPS, dates, author and copyright, or everything. For a JPEG it rewrites only the metadata segment, so the pixels are untouched and there is no re-encoding loss. Reopen the cleaned file here afterwards — an empty table is the confirmation that the strip worked.

Related tools

View all

Part of File viewers that open the file in your browser

Related categories1

Updated

We use anonymous analytics to improve ToolChamp. No personal data is stored or sold. Privacy Policy