Read every tag in your HEIC.
safe · secure · no server · works offline · fast
…or paste a file you copied in Finder, or just start typing at the cursor.
↓ scroll for about & FAQsafe · secure · no server · works offline · fast
…or paste a file you copied in Finder, or just start typing at the cursor.
↓ scroll for about & FAQMost online tools show a HEIC’s camera make, model and date and stop there. OmniViewer reads every EXIF tag in every directory — IFD0, the Exif SubIFD, the GPS IFD, Interop and the thumbnail’s IFD1 — and shows all of them: exposure time, aperture, ISO, focal length and its 35 mm equivalent, metering mode, flash, orientation, resolution, colour space, white balance, sub-second and UTC-offset timestamps, GPS latitude, longitude, altitude, map datum and timestamp. Tags we have no name for are still listed, by their tag id, with their raw value — nothing is dropped for being unrecognised.
Each value is shown twice where it helps: the raw literal
as the camera wrote it (19/10) and the
interpreted reading (f/1.9). An
All metadata table below the cards lists every field
grouped by the block it came from, with a filter box.
An XMP packet is not just “present”: it is parsed into individual properties with their namespaces kept, Apple and vendor namespaces included, and you can switch between Parsed XMP and the raw packet. The container’s own facts — brands, the primary item, tile grid, colour profile, bit depth, thumbnails, depth maps and HDR gain maps — get their own read-only section, because they are HEIF structure and not EXIF tags.
In a HEIC the EXIF and the XMP are separate items stored alongside the image, so Clear identifying takes each whole item — and the tab says so rather than pretending a single field can be deleted. The clean copy is downloaded with those items overwritten with zeros in place, so every box offset stays valid and the coded image is copied through byte-for-byte: the picture is pixel-identical and no quality is lost. No upload, no server, no conversion to JPG — and it works on a photo of any size, because the metadata lives in a small box at the front of the file.
It’s one lens on OmniViewer’s HEIC Viewer — EXIF/GPS & Structure: drop a file and every tab is one click away. OmniViewer opens every file format, entirely in your browser — no upload, no server.
No. OmniViewer is a static page with no server-side processing: your HEIC is read directly by your browser and never leaves your computer. Even the metadata stripper works locally, assembling the clean copy from byte slices of your original file.
A HEVC-coded image wrapped in an ISO-BMFF container — the same length-prefixed "box" grammar as MP4. Where MP4 describes a timeline of tracks, HEIF (the format; HEIC is the HEVC-coded flavour) describes a set of items. One small meta box near the front lists every item — an hvc1 coded image, a thumbnail, an Exif block, a grid of tiles — plus where each item’s bytes live in the mdat and the properties (dimensions, HEVC config, rotation) attached to each.
Yes — that is the point. OmniViewer opens the HEIC directly: it reads the item structure, the EXIF, the HEVC profile and the dimensions, and previews the picture where your browser can decode HEIC. Nothing is converted or uploaded. If you specifically need a JPG, that is a separate export step this tool deliberately does not do — it inspects the original.
Almost every iPhone photo does. The EXIF — camera make and model, lens, timestamp, exposure, and frequently the GPS position where the photo was taken — is stored as a separate Exif item in the file, referenced from the image. OmniViewer decodes what it finds and shows a verdict the moment the file opens.
Open the ITEMS tab and click "Download clean copy" (or use the Remove buttons on the METADATA privacy card). The EXIF and any XMP item are overwritten with zero bytes in place: every box offset and item location stays exactly where it was, so the file stays valid and the coded image is copied through byte-for-byte. The GPS coordinates are physically gone and the picture is pixel-identical.
Because HEIC stores its pixels as HEVC (H.265) video frames, and only some browsers can decode that: Safari and recent Chrome/Edge builds can, Firefox and older browsers cannot. When your browser can’t decode it, OmniViewer says so — and the ITEMS, METADATA, STATS and hex tabs still read the file’s structure, dimensions and metadata, because those come from the container, not the coded pixels.
Effectively unlimited. The meta box that holds the whole item structure sits near the front of the file, before the coded pixels in mdat, so the item list, dimensions, EXIF and clean-copy stripper cost a handful of tiny reads at any size. The preview relies on your browser’s decoder; the items, stats, hex and raw views work regardless.
HEIF is the container format (ISO/IEC 23008-12); HEIC is HEIF with the images coded using HEVC (H.265), which is what Apple devices produce. AVIF is the same container with AV1-coded images. OmniViewer detects the family from the ftyp brand and opens .heic and .heif the same way.
