oktools

EXIF Viewer & Remover

See everything a photo carries — EXIF camera and exposure data, the GPS location, the camera maker’s own maker notes, IPTC and XMP captions, credits and edit settings, the ICC colour profile and how the file itself is encoded — in JPEG, PNG, WebP, HEIC, AVIF, TIFF and camera RAW files. JPEG, PNG and WebP can then be downloaded with all metadata removed, losslessly: the image data is copied byte for byte, never re-encoded. Your photos are read by your own browser and never uploaded.

Removal options

No photos yet

Add one or more photos above to see what they reveal. Each one is read the moment it arrives, and its clean copy is ready to download straight away.

How it works

The file is read as raw bytes and never decoded as an image. Its container is identified from its first bytes, not its name, and walked one structure at a time — JPEG marker segments, including those between the scans of a progressive JPEG; PNG chunks; WebP RIFF chunks; the boxes of a HEIC, AVIF or CR3 file, where the Exif and XMP data are items located through the iloc table; every directory and SubIFD of a TIFF, BigTIFF or TIFF-based RAW file — and each kind of metadata goes to its own parser. EXIF is a miniature TIFF file inside the image: a byte-order mark (II or MM) and directories of twelve-byte entries, followed from IFD0 into the Exif, GPS and Interoperability directories and on to the thumbnail. IPTC is read from the Photoshop resource blocks in APP13, honouring the character set it declares. XMP packets — including extended XMP split across several JPEG segments — are parsed as XML and flattened into prefix:name = value. A multi-segment ICC profile is put back together and its header and description read, and compressed PNG text and profiles are inflated with the browser’s own DecompressionStream. Every length and offset is checked against the bytes that are really there, and a directory that points back to one already read is refused, so a damaged or crafted file ends in a note, not a frozen tab.

Values are then turned into what a camera display would show, and the ones a camera implies but does not store are worked out. Fractions such as 10/2500 become 1/250 s; every enumerated tag becomes words; APEX shutter and aperture values stand in when the plain ones are missing; the 35 mm equivalent comes from its own tag or, failing that, from the sensor size the focal-plane resolution implies, and is labelled estimated; the field of view, crop factor, megapixels and aspect ratio follow from those. Capture time is shown with its sub-seconds and offset and converted to UTC. The camera maker’s private maker note is located the way each vendor frames it (Canon, Nikon, Sony, Fujifilm, Olympus/OM System, Panasonic, Pentax, Apple, Samsung — each with its own header and offset base) and its documented fields named, Canon’s settings arrays included. Where a vendor hides the useful fields, the ciphers ExifTool documents are applied: Nikon’s LensData and ShotInfo are decrypted with a key made from the camera’s serial number and shutter count, and the lens bytes are matched against ExifTool’s LensID table; Sony’s 0x9050 and 0x9400 blocks are deciphered (each byte b was stored as b³ mod 249) and read with the layout the model uses; Pentax’s shutter count is unscrambled against its date and time. Canon model and lens IDs become names, and when one LensType number is shared by several lenses the recorded focal range and aperture narrow the list. These name tables are loaded only when a file from that maker is opened. Text that is not UTF-8 is scored as Shift_JIS, EUC-JP, JIS, GB18030, Big5 and EUC-KR by which decoders read it cleanly and how much of it falls in each standard’s common characters; when two readings are close the winner is marked as a guess and the others are shown beside it. The file’s own structure is described too — JPEG encoding and a quality estimate, PNG chunks, WebP features, HEIF items and codec, TIFF directories, RAW format details — and fields that name a person, place or serial number are flagged, wherever they were found. The OpenStreetMap link is built from the coordinates, but nothing is loaded from it.

Removal — for JPEG, PNG and WebP only — reuses the same walk. Metadata parts are left out and every other byte is copied in order, so the compressed image data is untouched and the cleaned file decodes to exactly the same pixels. A JPEG keeps its JFIF header, its Adobe segment (which tells decoders how to convert the colours) and, unless you untick it, its ICC colour profile. Because dropping EXIF also drops Orientation, a photo that relied on it gets a new 36-byte EXIF block holding only that tag. A WebP has its VP8X feature flags and RIFF size rewritten to match, and anything stored after the end of the image — where some phones append a preview or a video clip — is removed as well.

Examples

Read the location from a phone photo

The GPS tags of a synthetic test image, pointing at open sea in the Pacific. The W reference makes the longitude negative, and the GPS time is always UTC, unlike the camera’s own clock.

GPS tags as stored
GPSLatitudeRef   N
GPSLatitude      12/1, 34/1, 5670/100
GPSLongitudeRef  W
GPSLongitude     98/1, 45/1, 4320/100
GPSAltitudeRef   0
GPSAltitude      125/10
GPSTimeStamp     12/1, 30/1, 5/1
GPSDateStamp     2024:05:01
GPS section
Position  12.582417, -98.762000
DMS       12° 34′ 56.70″ N, 98° 45′ 43.20″ W
Altitude  12.5 m above sea level
Time      2024-05-01 12:30:05 UTC

Decrypt a Nikon lens block

A synthetic Nikon type 3 maker note. LensData version 0204 and ShotInfo version 0220 are encrypted from their fifth byte, keyed by the serial number and shutter count stored in the same note. The decrypted lens bytes plus LensType form the key looked up in ExifTool’s LensID table. Nikon encodes focal lengths on a logarithmic scale, which is why 50 mm reads back as 50.4.

Maker note as stored
SerialNumber  1234567
ShutterCount  4321
LensType      6
LensData      30 32 30 34 87 BA 00 59 C5 44 86 2B 93 AA 8C 9D … (32 bytes)
ShotInfo      30 32 32 30 B6 94 30 68 E5 44 D6 7B 33 FE DC CD … (64 bytes)
Maker notes (Nikon)
Lens name (LensID)     AF-S Nikkor 50mm f/1.4G
LensID key             A0 54 50 50 0C 0C A2 06
MinFocalLength         50.4 mm
MaxApertureAtMinFocal  f/1.4
FocusDistance          1.00 m
Firmware               1.01

Look inside a HEIC

A synthetic HEIC built box by box: an hvc1 primary item with its properties, an Exif item stored in idat behind its 4-byte offset, an XMP item, a thumbnail and an alpha item. No clean copy is offered for it.

Boxes
ftyp  heic (mif1, heic)
iinf  1 hvc1, 2 Exif, 3 mime, 4 hvc1, 5 hvc1
iref  cdsc 2→1, cdsc 3→1, thmb 4→1, auxl 5→1
ipco  hvcC, ispe 4032×3024, colr nclx 12/13/6, pixi 8,8,8, irot 1,
      auxC urn:mpeg:hevc:2015:auxid:1
HEIF/AVIF structure
Primary item  #1, hvc1
Image size    4032 × 3024 px
Codec         HEVC Main profile, Main tier, level 3.0, 4:2:0, 8-bit
Colour        primaries SMPTE EG 432-1 (Display P3), transfer sRGB,
              matrix BT.601, full range
Rotation      90° anticlockwise
Items         5: 3 hvc1, 1 Exif, 1 mime
Thumbnails    #4
Auxiliary     #5 Alpha (urn:mpeg:hevc:2015:auxid:1)

Clean a JPEG and keep it upright

A synthetic 203.4 KB JPEG with EXIF (Orientation 6, GPS and a 4 KB thumbnail), an XMP packet, an ICC profile and a comment, cleaned with the default options. 208,297 bytes become 200,734: the three removed parts, less the 36 bytes added back.

Input
photo.jpg — 203.4 KB
Keep colour profile: on   Keep orientation: on
Output
photo-clean.jpg — 196.0 KB
Removed: EXIF (APP1) 4.4 KB, XMP (APP1) 3.0 KB, Comment (COM) 22 B
Added:   36-byte EXIF block with Orientation 6 (Rotated 90° clockwise)
Kept:    JFIF header, ICC colour profile, all image data

Supported formats

  • JPEG, PNG and WebP — read and cleanedJPEG (baseline and progressive) with EXIF, XMP and extended XMP, IPTC, multi-segment ICC profiles, comments and its frame structure; PNG and APNG with every text chunk and colour chunk; WebP in all three variants. These are the formats the lossless remover writes.
  • HEIC, HEIF and AVIF — read onlyBrands, items (iinf), locations (iloc versions 0–2, in the file or in idat), references (thumbnails, auxiliary alpha, depth and Apple gain-map images, grid tiles), properties (ispe, pixi, colr nclx and ICC, irot, imir, hvcC, av1C, auxC), the Exif and XMP items, and image sequences.
  • TIFF and BigTIFF — read onlyEvery page and SubIFD with its compression, photometric interpretation, bit depth, samples, planar configuration and strips or tiles; XMP (tag 700), IPTC (33723), Photoshop resources (34377) and ICC (34675).
  • Camera RAW — read onlyDNG, CR2, NEF, NRW, ARW, ORF, RW2, PEF, SRW, 3FR and ERF through their TIFF structure, Canon CR3 through its CMT1–CMT4 boxes, Fujifilm RAF through its header, directory and embedded JPEG. DNG version, CFA pattern, black and white level, as-shot neutral and colour matrices are listed, and the largest embedded JPEG preview is shown.
  • Maker notesCanon (including CameraSettings and ShotInfo), Nikon types 2 and 3 with the PreviewIFD, Sony, Fujifilm, Olympus and OM System with their sub-directories, Panasonic, Pentax (and Ricoh’s Pentax-format notes), Apple iOS and Samsung, with tag names from ExifTool’s and Exiv2’s documentation. Decoded further: Nikon LensData and ShotInfo (decrypted) with the lens name, Canon model and lens names, Sony 0x9050 and 0x9400 (deciphered) with shutter count and E-mount lens, Pentax shutter count, Fujifilm film simulation and dynamic range. Nikon type 1, Ricoh’s own format and other makers’ notes are listed entry by entry when they parse as a directory.
  • EXIF 3.0, IPTC-IIM 4.2, XMP and ICC v2/v4All EXIF directories and field types, every enumerated tag decoded; IPTC records 1 to 9 with the spec’s enumerations and ISO 2022 character sets (UTF-8, Latin-1, ISO-2022-JP, GB2312, KS C 5601); any XMP namespace; ICC header fields and desc/cprt text. Copy as JSON carries all of it.

Use cases

  • Selling something onlineA listing photo taken at home can carry the home’s coordinates to every buyer who saves the original. Check it here, then post the -clean copy.
  • Sending photos as filesEmail attachments, cloud-drive links and “send as document” in messaging apps deliver the original file, with the camera’s serial number and the photographer’s name. Clean a batch first and send the ZIP.
  • Checking where an image came fromCapture time with its time-zone offset, camera body and lens, editing software, Lightroom settings and agency credits help confirm or question a picture’s story — and a JPEG quality estimate hints at how many times it has been re-saved.
  • Debugging image pipelinesSee why a photo shows sideways (Orientation), why its colours shift (ICC profile, colour space), whether a JPEG is progressive or 4:2:0, or whether a PNG is animated, without opening a hex editor.

Limitations

  • Clean copies only for JPEG, PNG and WebPHEIC, AVIF, TIFF and RAW files are read and shown but not rewritten: RAW developers need the maker notes, and moving HEIF items or TIFF directories without re-encoding is not implemented. GIF, PSD, older RAW formats (Canon CRW, Minolta MRW, Sigma X3F, Phase One IIQ) and video are not read at all.
  • Maker notes are decoded only as far as they are documentedOnly fields with a documented layout are turned into words; the rest of a block is shown as bytes. Not decoded: Nikon ShotInfo beyond the firmware version, its ColorBalance block and Z-mount lens names; Sony 0x2010 and CameraSettings, and A-mount lens names; Canon LensInfo; Olympus and Panasonic lens and focus details beyond their plain tags; Apple’s binary property lists. A lens ID ExifTool lists for several lenses is shown with every candidate when the focal range and aperture cannot tell them apart. The lens and model names, cipher tables and block layouts come from ExifTool 13.63 by Phil Harvey, used under the Perl Artistic License; a camera or lens newer than that release shows its number. Besides synthetic test files, the decoding was checked against seven public-domain (CC0) RAW samples from raw.pixls.us — Nikon D7000, D750 and Z 6, Canon EOS 7D and 6D, Sony ILCE-6300 and ILCE-7M3 — where the decrypted Nikon lens data, the Canon model and lens names and the deciphered Sony lens names agreed with Exiv2 or with the file’s own lens tag; other bodies and firmware versions may lay a block out differently. A note whose offsets an editor broke is reported with warnings rather than guessed at.
  • Large RAW files are read wholeFiles are read into memory in one piece: up to 300 MB for view-only formats and 50 MB for JPEG, PNG and WebP. RAW sensor data and HEVC or AV1 image data are never decoded; a RAW or TIFF is shown through its embedded JPEG, and a HEIC only where the browser itself can draw it.
  • Text encodings are detected, not declaredEXIF does not say which legacy encoding its text uses, and EUC-JP, GB18030 and EUC-KR share most of their byte ranges: the same bytes are often valid in all three. Short strings are therefore marked “guessed”, with the other readings shown so you can pick the right one. Detection uses the browser’s own decoders and falls back to Latin-1 where one is missing. IPTC text follows its declared character set when 1:90 names one.
  • Estimates are labelled as suchThe JPEG quality assumes the IJG scaling most encoders use and can be off for files from encoders with their own tables. The estimated 35 mm equivalent relies on the focal-plane resolution, which some cameras report for the full sensor even in a crop mode.
  • Partial structure for XMP, IPTC and ICCXMP is flattened: nested structures appear as field=value lists and values longer than 4,000 characters are cut. IPTC record 6 has no datasets named in the spec, and record 8 object data is shown by size only. Only the ICC header and text tags are read, not the colour data. Anything shortened in the tables is complete in Copy as JSON.
  • Nothing in the pixels is touchedA visible watermark, a reflection, a street sign or anything hidden in the image data itself stays exactly as it was — that is the point of a lossless remover. Private PNG and WebP chunks pass through a clean copy unchanged, and the file name is not metadata here either: rename it yourself if it gives anything away.

Frequently asked questions

How do I see where a photo was taken?

Drop the photo onto this page. If the phone or camera saved its location, a GPS section appears with the latitude and longitude in decimal and in degrees, minutes and seconds, the altitude, the satellite time in UTC and, when recorded, the accuracy, speed and the direction the camera faced, plus an Open in OpenStreetMap link that puts a pin on the spot. If there is no GPS section, the location was never recorded — location services were off for the camera app — or an app removed it before the file reached you.

Does removing EXIF data reduce image quality?

Not here. The remover copies the compressed image data byte for byte and leaves out only the metadata segments around it, so the pixels in the cleaned file are exactly the ones in the original and the file shrinks only by the size of what was removed. That is different from opening a photo in an editor and saving it again, or from a compressor: those decode and re-encode the image, which drops metadata too but costs a little quality every time.

Do Facebook, Instagram and WhatsApp remove EXIF data from photos?

The big social networks generally strip EXIF, including GPS, from the copy other people see, because they re-compress every upload. That does not mean the platform never saw it: the original arrives on their servers first. And photos sent as files rather than as pictures — a WhatsApp or Telegram document, an email attachment, a shared cloud-drive link, a forum or marketplace that serves the original — reach the recipient untouched. Cleaning a photo before it leaves your device is the only way to be sure.

What information can photo metadata reveal?

More than most people expect: the make, model and often the serial number of the camera and lens, the date and time to a fraction of a second with the time-zone offset, every exposure setting, the editing software and sometimes every edit made in it, the photographer’s or owner’s name, captions, keywords and contact details added by an agency or editor, and on phones the GPS position, altitude and compass direction. The camera maker’s own maker note can add a shutter count, the exact lens, internal serial numbers and, on some cameras, a child’s name and age or a home town typed into the menus. Nikon and Sony encrypt parts of theirs, but that hides nothing: the key is the serial number and shutter count stored beside it, and this page decrypts those blocks like any other reader does. Many photos also carry a small preview image, which can still show what was cropped out of the final picture.

What is the difference between EXIF, IPTC and XMP?

EXIF is written by the camera at the moment of capture: settings, time, GPS, camera and lens. IPTC is the older newsroom standard for describing a picture — headline, caption, keywords, photographer, credit and copyright — usually added later by a person or an agency. XMP is Adobe’s XML format that can hold all of the above and more, including Lightroom and Camera Raw edit settings and an edit history. One file often carries all three, sometimes with conflicting values; this page lists each one separately and removes all of them.

Are my photos uploaded anywhere?

No. Files are read by your browser with the File API, parsed and cleaned in this page’s own JavaScript, and downloaded straight from memory; nothing is sent over the network. The map link is the only exception you control: it is an ordinary link, and the coordinates go to OpenStreetMap only if you click it.

Can I read HEIC, AVIF, TIFF and RAW photos, and clean them?

Read, yes: drop an iPhone HEIC, an AVIF, a TIFF or a camera RAW file (DNG, CR2, CR3, NEF, NRW, ARW, ORF, RW2, PEF, SRW, RAF, 3FR, ERF) and its EXIF, GPS, maker note, XMP and colour profile are shown, with the file’s own structure and its embedded JPEG preview. Clean, no: a clean copy is offered only for JPEG, PNG and WebP. RAW developers need the maker notes, and rewriting HEIF and TIFF files without re-encoding is not implemented here. To share a HEIC from an iPhone without its location, tap Share, then Options, and turn Location off — or export it as JPEG and clean that.