Skip to main content

Supported format

Remove metadata from HEIC files

An HEIC image can carry Exif, XMP, location fields and connected metadata items. ScrubMetadata processes supported items and containers in your browser, then checks the output independently. Apple feature signatures do not prove complete payload coverage. Review auxiliary structures and unresolved findings before the authorised person decides whether to disclose it.

HEIC metadata and connected items

An HEIC can carry Exif, XMP, location fields and identifiers in items connected to the image. Thumbnails, auxiliary images and item properties require container assessment as well as a field list. Inspect the report for the actual structures found; an Apple feature signature only indicates something to review.

  • Exif/XMP, location and device/identifier fields
  • Item properties, thumbnails and auxiliary-image relationships
  • Privacy-bearing meta/UUID/JUMBF structures

Supported HEIC removal scope

Removal is limited to parser-identified privacy items, boxes and properties. The independent verifier then parses the processed file and reports supported privacy residuals, errors and unassessed structures. A field disappearing from a summary is insufficient: the connected containers must have an assessed disposition before the result is treated as verified clean.

Retained HEIC image structures

The assessed native path retains structural image data and the item locations, references and properties required by that image. Retention must match the parser's assessment. It is not a promise of complete Live Photo, Portrait or depth-map understanding, nor a guarantee that every image quality or device feature is preserved.

  • Assessed structural image data.
  • The item locations, references and properties required by the assessed native image.

HEIC limits and Apple feature indicators

Live Photo, Portrait, depth-map and biometric signatures are review indicators rather than proof of complete payload coverage. Unknown boxes, item types, properties or ambiguous relationships can prevent a verified clean result. Read those findings and the parser outcome; the filename does not establish universal support across Apple image variants.

  • Live Photo, Portrait, depth-map and biometric signatures are review indicators, without complete payload coverage being implied.
  • Unknown boxes, items or properties, ambiguous references and parser errors prevent a verified clean result.
  • The independent result must report no supported privacy residuals, errors or unassessed structures.
  • No universal Apple-feature removal, location precision or image-quality guarantee applies.

Questions about HEIC metadata

Does a detected Portrait or Live Photo signature prove the payload was removed?

No. Such signatures indicate structures to review. The parser reports only assessed items and containers; unsupported or ambiguous structures cannot be represented as removed.

What prevents a verified clean HEIC result?

The independent verifier must parse the output and report no supported privacy residuals, parser errors or unassessed structures. Otherwise the result remains review-required.

An iPhone image proposed for disclosure

Representative scenario

An iPhone HEIC is proposed as a rights-request attachment. Inspect location and identifier findings and review any auxiliary-item or Apple-feature indicators. Read the independent result for unresolved structures, then open the processed image before the authorised person decides whether the file is ready for the intended disclosure.

How to review file metadata before disclosure

Process HEIC files in your workspace

Supported HEIC files are inspected and cleaned in your browser. Raw file bytes and raw metadata are not sent to ScrubMetadata servers, and only minimised evidence is recorded after processing.

  • Raw file processing stays local
  • Device-verified access
  • Accounts approved by a person
Request access

Already approved? Sign in

Remove HEIC metadata in your browser · ScrubMetadata