Supported format

Remove metadata from HEIF files

HEIF stores images and metadata as connected items, so a field view alone cannot describe the whole container. ScrubMetadata inspects supported items, properties and references locally and removes only assessed privacy structures. Review the independent residual result and any unsupported container variation before deciding whether the output can be disclosed.

HEIF image and metadata relationships

HEIF can store Exif, XMP, identifiers and descriptive metadata in separate items connected by references, locations and properties. ICC data, auxiliary images and provenance containers also need assessment. Read the item and container findings together; removing a displayed field alone does not account for the connected structure.

Exif/XMP and descriptive metadata
ICC attributes, item properties and identifiers
Meta boxes, item references/locations, auxiliary images, UUID and provenance containers

Supported HEIF removal scope

Only privacy items, boxes and properties identified by the current parser are within the removal claim. Independent verification then examines the output for supported residuals, parser errors and unassessed structures. The file cannot receive a verified clean result merely because a familiar extension or one metadata item was recognised.

HEIF image structures and relationships

The assessed path keeps structural image data and the item relationships needed by that image. Those relationships have their own dispositions and must remain valid after removal. Retained structure does not establish support for every HEIF brand, codec or application variation; inspect the report and open the processed image.

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

HEIF container limits

The independent parser checks the actual brand and item graph, including the arrangement of location, property and reference boxes. Unknown items, unsupported arrangements or ambiguous relationships cannot inherit support from the filename. Follow the reported disposition; no universal codec, container or platform compatibility claim is made for the extension.

The parser must recognise the actual brand and assess its items, boxes, properties and references.
Unknown items, unsupported box arrangements and ambiguous relationships cannot inherit support from the filename.
The independent result must report no supported privacy residuals, errors or unassessed structures.
No universal HEIF container, codec or platform compatibility guarantee applies.

Questions about HEIF metadata

Why is HEIF assessed as a container as well as a set of fields?

Its image and metadata can be separate items connected by locations, properties and references. Removing a displayed field alone does not establish that the connected privacy item is gone.

Does a .heif filename establish support for every container variation?

No. The independent parser checks the actual brand and item graph. Unsupported or unknown structures cannot inherit support from the extension.

A supplier image from another application

Representative scenario

A supplier sends a HEIF image exported by a different application. Inspect the item and container findings and check that the actual brand and relationships were assessed. Review the independent result and processed image before the responsible person decides whether to use that file in the proposed disclosure.

How to review file metadata before disclosure

Process HEIF files in your workspace

Supported HEIF 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