Open a HEIC or HEIF photo and read its embedded camera metadata, make, model, exposure and GPS where present, plus a map of the file's box structure.
No file loaded yet.
The top-level boxes of the file will be listed here, whether or not EXIF extraction succeeds.
This viewer parses the HEIC file’s ISOBMFF structure directly, byte by byte, rather than decoding the image. It walks the top-level boxes (such as ftyp and meta) and always shows that box map. It then looks inside the meta box — allowing for its four version/flag bytes — for the item information and item location boxes, follows the location data for the item typed “Exif” (construction method 0, data-reference 0), and parses the embedded TIFF record it points to: the IFD0 fields, the Exif IFD reached through its pointer tag, and the GPS IFD where present. The honest scope: HEIC layouts vary by phone maker and app, so the Exif item cannot be located in every file. When that happens the page still shows the box map as confirmation of the file structure and reports the metadata as not found. Some files store no EXIF at all, and values that are absent are shown as absent, never estimated. Image decoding, thumbnails and conversion are outside this tool’s scope.
Does this viewer show the photo itself? No. It reads metadata only and does not decode the HEIC image. The embedded EXIF record and the file's box structure are what it reports.
Why might the camera fields be empty even though the box map shows? HEIC layouts vary by phone maker, and the EXIF record is located through the file's item location data. When that record cannot be located, the box map still confirms the file structure, and the table says the EXIF item was not found instead of inventing values.
Is the photo uploaded anywhere? No. The file is parsed locally in the browser, byte by byte; nothing, including any GPS coordinates in the file, is sent to a server.