EXIF viewer: where, when and with what camera a photo was taken

What you get

• A plain summary: camera make and model, lens, the date and time taken with its time zone offset when the camera recorded one (for example 2026-07-14 18:32:05 (UTC+02:00)), shutter speed, aperture, ISO, focal length, pixel size and the software that last saved the file.
• One line about location. Either This photo contains a GPS location: 55.6761° N, 12.5683° E (with the altitude when it is stored) and a button that copies the coordinates, or No GPS location found in this file. Coordinates are shown as text only: this page draws no map, because a map would have to fetch tiles from someone's server and tell them where to look. Paste the copied numbers into a map app yourself if you want to see the spot.
• The picture. JPEG, PNG, WebP and AVIF are shown by your browser's own decoder, plain TIFF is decoded in the page, and a RAW file shows the largest JPEG preview the camera stored inside it.
• Every tag in a table you can search, grouped by where it lives: IFD0 (camera and file), EXIF (exposure and dates), GPS, XMP (editing apps' data, ratings, sometimes location), IPTC (captions, keywords, byline, copyright) and ICC (the colour profile).
• Save a copy without metadata (JPEG). Lossless: the image data is copied byte for byte, see below.
• Save the embedded preview as JPEG (RAW files). The camera's own JPEG, exactly as it is stored in the file.

How much a GPS tag gives away

Phones write the position into every photo unless location access for the camera app is switched off. Four decimal places of a degree, as shown here, pin a spot to about 11 metres north–south (one ten-thousandth of a degree of latitude is 11.1 m), which is one house on a street. 55.6761° N, 12.5683° E, the example above, is the square in front of Copenhagen City Hall.

Whether the location survives sharing depends on how the file travels. The big social networks generally remove it when they re-compress an upload. E-mail attachments, cloud-drive share links, AirDrop, and a chat app's "send as file" or "document" option pass the original bytes on unchanged, GPS included. On an iPhone, the share sheet's Options › Location switch leaves it out.

What "without metadata" removes and keeps

A JPEG is a list of segments followed by the compressed image data. The copy is made by leaving segments out, never by decoding and re-encoding the picture, so it loses no quality and the image data from the start-of-scan marker to the end-of-image marker is identical to the original's, byte for byte.

Removed

APP1 Exif: camera, lens, serial numbers, dates, GPS, and the small thumbnail inside Exif, which some editors leave showing the photo as it was before cropping. APP1 XMP: edit history, ratings, face-region names, sometimes location. APP13: IPTC captions, keywords, byline and copyright. COM comments. APP2 Multi-Picture data and anything after the end-of-image marker, where some phones store a second image such as a depth map. Every other APPn segment.

Kept, because the picture depends on them

APP0 JFIF (pixel density and aspect, 16 bytes, nothing personal). APP2 ICC_PROFILE: without it a Display P3 or Adobe RGB photo shows duller colours. The 12-byte APP14 Adobe marker, which says whether the three colour channels are YCbCr, RGB or CMYK: without it some Photoshop-saved JPEGs decode with wrong colours. None of these hold a camera, date, name or place.

Sideways photos

Phones usually store a portrait photo lying on its side and add an Orientation tag (value 6: turn 90° clockwise). The Orientation tag lives in Exif, so the stripped copy shows sideways. When the tag is not 1, the page says so and offers an upright copy instead. That copy is turned on a canvas and re-encoded as a new JPEG at quality 92, so it is not byte-identical, and the page labels it that way.

A photo with the camera's credit or copyright in it loses that too: stripping cannot tell your GPS from someone's byline.

RAW files: the preview inside

A RAW file holds the sensor's unprocessed readings, which need a raw developer (Lightroom, Capture One, darktable, RawTherapee, the camera maker's own software) to turn into a picture. Next to them, cameras store a finished JPEG so the camera's screen and file browsers can show something fast. This page finds that JPEG and shows it. It does not develop the RAW sensor data: what you see and save is the camera's own rendering, with its white balance and picture style baked in.

DNG, NEF, CR2, ARW (TIFF-based)

The file's image directories (IFD0, the ones after it, and their SubIFDs) are walked and every JPEG they name is collected, through the JPEGInterchangeFormat tags or a single strip compressed as JPEG (compression 6 or 7). Lossless JPEG streams, which DNG uses for the raw data itself, are skipped. Canon CR2 files keep a full-size JPEG in IFD0; Adobe DNG Converter writes none, a 1024-pixel one or a full-size one, as you chose when converting.

Canon CR3 (ISO base media, like MP4)

The THMB box holds a 160 × 120 thumbnail, the PRVW box a 1620 × 1080 preview, and the first track usually a full-size JPEG. The largest one that decodes is shown.

When nothing is named

The page falls back to the largest complete JPEG stream (FF D8 … FF D9) it finds anywhere in the file, and says so.

What it cannot do

• Develop RAW data. No demosaicing, white balance or exposure: only the camera's embedded JPEG is shown. A RAW file without one (rare) shows no picture.
• Strip metadata from PNG, WebP, HEIC or TIFF. The lossless copy is JPEG-only. For the others, export a fresh copy from an image editor with metadata switched off.
• Decode maker notes. The camera maker's private block (Canon, Nikon, Sony and others) often holds the shutter count and more serial numbers. It is not decoded or listed here, though the JPEG copy removes it with the rest of Exif.
• Video metadata. MP4 and MOV files carry their own location and dates in a different structure; the video and audio viewer reads those.
• Show a HEIC picture here. HEIC files get their metadata on this page; the picture is shown and converted by the HEIC viewer.
• Every TIFF variant. Plain TIFF (uncompressed, LZW, PackBits, Deflate, JPEG, fax) is decoded; only the first image of a multi-page TIFF is shown, 16-bit images are shown at 8 bits, and BigTIFF files (over 4 GB) are not recognised.
• AVIF in older browsers. AVIF pictures need Chrome, Edge, Firefox or Safari 16.4 or later; elsewhere you still get the metadata.