Remove metadata from SVG files

SVG metadata beyond the drawing

An SVG can contain comments, editor details and RDF or XMP metadata within its XML. It can also contain descriptive text, identifiers, embedded images or external references. Those structures have different meanings. Inspect the report alongside the drawing so visible content, accessibility descriptions and metadata are not treated as interchangeable.

• RDF/XMP properties, title, description, comments and identifiers
• XML metadata/namespaces and editor-specific attributes
• Scripts, event handlers, external references, data URIs and embedded images

Supported SVG metadata removal

The supported path removes assessed XML metadata, RDF or XMP structures, private extension elements and identified privacy attributes. Only privacy-bearing comments are removed. Native titles and descriptions outside those containers remain content. Review the drawing and descriptions; a removed metadata element does not account for every embedded structure.

SVG structure and retained descriptions

The output must retain a parseable SVG root and the supported drawing structures needed by the assessed file. Native titles and descriptions outside removed metadata containers remain content. This does not guarantee unchanged drawing behaviour. Open the processed drawing and review its descriptions and removed attributes before approving disclosure.

• A parseable SVG root and namespace.
• The supported drawing structures required by the assessed output.

SVG blockers and content review

Malformed XML, scripts, event handlers and external references are refused on this path. Embedded data references remain unassessed and block processing. Native drawing titles and descriptions still need your review. A technical metadata result does not establish anonymity or assess every personal detail in the visible drawing or descriptive text.

• Native titles and descriptions outside removed metadata containers are retained as content; review them for personal information and accessibility meaning.
• Identified privacy attributes and private extension attributes can be removed; inspect the resulting drawing without assuming unchanged behaviour.
• Malformed XML, scripts, event handlers and external references are refused. Embedded data references and unknown structures block processing as unassessed.
• The workflow does not establish anonymity or that every SVG is safe to open.