HEIC file inspection
Check HEIC Photo Metadata Without Converting It
Check the HEIC file you intend to share before converting it just to make a viewer accept it. This browser tool reads supported HEIC EXIF/GPS fields as categories, not HEIC XMP/IPTC or every tag. A conversion is a new file that needs its own check; a readable preview is not proof of complete metadata coverage.
By Qingxin Studio, the developer of HushPic · Updated
Keep the original and identify the attachment
Find the actual image you intend to send. A library thumbnail, a JPEG export, and a HEIC original are not interchangeable inspection targets. Keep the original unchanged while preparing any sharing copy so you can compare the versions or choose another export deliberately.
Apple documents that some sharing and transfer paths may convert HEIF images to a compatible format. Check the selected attachment's format and do not assume that every recipient receives the same file your library displays. Changing the filename alone is not a conversion or a privacy operation.
Start with the supported HEIC check
Choose the HEIC file in the browser metadata checker, within the tool's 20 MB limit. Wait for a completed result, then read the four category indicators. A Found label says a matching populated field was read; it does not show a full tag inventory or publish the field's value.
The photo, filename, and extracted values are not sent to this site's analytics. The checker is a read-only browser task, not an uploader or converter. Clear result removes the displayed categories, and selecting another image replaces the result rather than creating a file history.
Know the container-specific limits
The exifr parser's support table lists HEIC EXIF/GPS reading but not HEIC XMP or IPTC. The website therefore cannot use an empty HEIC result to certify that those other metadata families are absent. It also does not inspect the visible picture for addresses, faces, or text.
Do not equate parser support with every possible variant being readable. A damaged or unusual file can fail, and a successful category check is still narrower than a full technical inventory. Use the method and limits section when deciding whether the information shown is sufficient for your purpose.
Handle failure without manufacturing a clean result
If the file cannot be checked, there is no usable category result. Confirm that the selected item is a supported image and within the stated limit. Do not rename it as JPEG or repeatedly change the input merely to obtain a reassuring Not found label.
If you intentionally export to JPEG or another format for compatibility, retain the HEIC original and inspect the export separately. The result then describes that export only. This website cannot reconstruct what was dropped, retained, or changed between the two files from category labels alone.
Separate metadata reading from image preservation
A parser being able to read fields does not mean an editor can safely rewrite the file while keeping its display properties. Before adopting a converted or cleaned copy, inspect orientation, dimensions, appearance, and any features important to your image. A normal preview is not a measurement of every color or HDR property.
HushPic only adds copies that pass its supported processing and verification checks to the sharing set. Follow the actual compatibility outcome and any normalization notice; this guide does not promise universal HEIC variant support, original-format output, or HDR preservation on every device.
Review the copy and the next destination
For supported cleanup, select the image in HushPic and inspect its generated result. Suggested visual masks can miss details, so use Review / Adjust where needed and regenerate after changes. The browser checker itself does not clean metadata, mask pixels, or verify a written output.
Share or save the current prepared copy, then ensure the attachment is that version rather than the original or an earlier export. If you edit or export again afterward, repeat the relevant checks. File compatibility, supported metadata coverage, and visible privacy are separate decisions.
Sources
This guide is published by Qingxin Studio, the developer of HushPic. Product claims describe our supported workflow, not independent certification. Our review checklists are practical first-party guidance; linked platform sources support only the mechanisms they describe. Automatic checks may miss details. Read our content and corrections policy.