How to View EXIF Metadata in HEIC Photos from Your iPhone

HEIC is the default image format on iPhone for a reason. Introduced with iOS 11, it stores the same visual quality as JPEG in roughly half the file size by using HEVC-based intra-frame compression. That efficiency is great for storage, but it also creates friction when you want to see what the camera actually recorded. A HEIC file on an iPhone is not just pixels. It contains a container with multiple image items and metadata streams, including EXIF, XMP, and IPTC blocks. EXIF is the part most people care about: camera model, lens, exposure time, aperture, ISO, focal length, focus mode, white balance, flash status, GPS coordinates if location services were enabled, and the original creation timestamp down to subseconds. For journalists, archivists, lawyers, and forensic analysts, those fields are the difference between a picture and a verifiable record. The problem is that Apple’s Photos app on iOS and iPadOS surfaces only a curated subset of that information, and it hides technical details behind a tap that many users never find. On Windows, the native Photos app historically did not understand HEIC at all until the HEIF extension was installed, and even then metadata visibility is limited. That mismatch is why people searching how to view EXIF data of HEIC iPhone photos end up with half-solutions that work on one OS but not another, or tools that strip metadata on export. Understanding where the metadata lives and how to read it without altering the file is the first step toward reliable documentation.

iOS makes it intentionally quiet.

On an iPhone, open Photos, select the HEIC image, tap the info button at the bottom, and you will see a summary of what Apple chooses to show. Camera model, exposure, aperture, ISO, focal length, and location if present. That view is convenient but incomplete. It does not display the full EXIF tag set, it does not show MakerNote data, it does not expose XMP or IPTC fields in a structured way, and it offers no export of the raw metadata. If you need a complete inventory for verification, you have to move the file off the device or use a tool that can parse the HEIF container directly. AirDropping to a Mac preserves the original file, while sharing via Messages or social apps often re-encodes and strips metadata. That is a practical example of why the method of transfer matters as much as the viewer you use. Keeping the original bit-for-bit copy is essential if you intend to compare hashes later.

Moving the file to a Mac is the most reliable first step for most iPhone users. macOS has native HEIF support since High Sierra, and Preview will open HEIC without conversion. Select the image in Finder, press Command+I to open Get Info, and scroll to the More Info section. You will see basic EXIF fields such as Date Created, Camera Model Name, Exposure Time, F Number, ISO, and GPS coordinates when available. This is still a summary, not a full dump. For a complete view, the free app Image Capture or the command line tool exiftool is the standard. With exiftool installed via Homebrew, a command like exiftool -a -u -g1 image.HEIC will list every tag group, including MakerNotes specific to Apple, and will show duplicate tags. The output is plain text and can be saved as evidence. If you prefer a graphical interface, apps like ExifToolGUI or Photo Investigator provide the same depth without typing commands. The key point is that macOS preserves the original HEIC container when you copy via Finder or AirDrop, so the metadata you read is the metadata that was written by the iPhone.

Windows users face a different set of constraints. Until the HEIF Image Extensions from the Microsoft Store are installed, Windows will not even render HEIC thumbnails. After installing the extension, the native Photos app can open HEIC, but right-click Properties Details shows only a limited metadata pane. For a full EXIF read, you need third-party software that understands HEIF containers. ExifTool runs on Windows via command line or via a GUI wrapper, and it reads HEIC exactly as it does on macOS. Adobe Lightroom Classic also imports HEIC and surfaces EXIF in its metadata panel, though it may write XMP sidecars on import. If you want a forensic approach that documents integrity alongside metadata, an online platform that computes cryptographic hashes while extracting metadata can be useful. FilesAudit is one such platform where you can upload a file to extract its metadata, hashes, and AI-provenance evidence and receive a timestamped PDF report. That report documents the technical state of the file at the time of analysis, which is helpful when you need to show that a photo was examined without modification.

Checking metadata online is convenient, but you should understand what is preserved. Browsers cannot render HEIC natively in all cases, so an online viewer must decode the HEIF container server side. Reputable services will process the file in memory and not store it permanently, and they will present the EXIF, XMP, and IPTC blocks in a readable format. This is where the FilesAudit platform becomes practical for non-technical users who need a clear report. It supports HEIC and more than 200 other formats across images, video, audio, documents, and archives, and its supported formats page lists the exact types it can parse. The platform does not determine legal ownership or authenticity by itself. It documents technical evidence: the metadata tags that are present, the SHA-256 and MD5 hashes of the file, and a timestamp of analysis. Those fingerprints help verify whether two files are identical or have been modified, which is the foundation of any later legal or editorial judgment.

A practical workflow that many journalists and researchers use looks like this. First, export the original HEIC from iPhone using Files app to a cloud drive or via a USB cable, avoiding any in-app share sheet that re-encodes. Second, compute a baseline hash immediately after export using a tool you trust. Third, open the file in a dedicated metadata reader on Mac or Windows to export the full EXIF dump as text. Fourth, if you need a shareable, tamper-evident record, run the file through a verification service that produces a PDF report with metadata, hashes, and timestamp. That report can be attached to case files or published alongside an article. The same workflow applies if you later convert HEIC to JPEG for compatibility. Conversion will change the file hash and may discard or rewrite metadata. Documenting both the original HEIC and the converted JPEG with separate reports makes the lineage explicit. This is especially important for copyright disputes and digital investigations where the question is not just what the photo shows, but whether the file has been altered since capture.

Comparing methods quickly clarifies trade-offs. Native iOS info is fast but limited. macOS Get Info and Preview are free and built in but summarize. exiftool is exhaustive and scriptable but command line. GUI tools are user friendly but sometimes hide MakerNotes. Online viewers are accessible from any device but require you to trust the provider’s privacy policy. Desktop forensic suites offer bulk analysis and chain of custody features