Metadata elements
Removes SVG <metadata> elements, including embedded RDF, Dublin Core, creator, rights, identifier, and editor workflow data.
Inspect well-formed UTF-8 SVG markup, remove non-rendered metadata elements and comments locally, and preserve accessibility titles and descriptions.
Private file workbench
We inspect one file at a time inside this browser. Nothing is uploaded.
SVG only · up to 25.0 MB
Removes SVG <metadata> elements and XML comments only. It preserves <title>, <desc>, scripts, event handlers, external references, embedded content, styles, and visible vector markup.
Supported cleanup
The tool validates the XML structure and removes precise non-rendered ranges without serialising or rebuilding the remaining vector markup.
Removes SVG <metadata> elements, including embedded RDF, Dublin Core, creator, rights, identifier, and editor workflow data.
Removes non-rendered comments that can retain names, project notes, generator details, source paths, or internal context.
Keeps <title> and <desc> elements because they can provide accessible names, descriptions, and meaningful document context.
Rejects malformed or non-UTF-8 SVG instead of rewriting it, then verifies that targeted metadata and comments are absent.
Know the boundary
Metadata removal does not make an untrusted SVG safe. Review active content, links, embedded resources, and accessibility text before publishing.
Where it helps
An SVG can look like a simple image while its XML source contains authorship, rights, project notes, identifiers, or editor-generated metadata.
Remove supported metadata and internal comments before adding SVG assets to a website, design system, public repository, or download pack.
Clear RDF creator, rights, date, identifier, and comment text before handing vector artwork to another party.
Remove metadata containers and export comments while retaining paths, shapes, styles, accessibility text, and the rest of the original XML.
Common questions
SVG is active XML content, not just an image. These boundaries keep metadata removal separate from security sanitisation.
SVG <title> and <desc> can provide accessible names and descriptions to assistive technology. Removing them by default could make the graphic less accessible, so this tool leaves them intact.
No. It removes <metadata> elements and XML comments only. Scripts, event attributes, foreign objects, external references, embedded images, styles, and visible content remain and must be security-reviewed separately.
No. The tool removes exact metadata and comment ranges from well-formed UTF-8 XML. It does not intentionally reformat, optimise, minify, or serialise the remaining markup.
Go deeper
Practical guidance for checking what the file carries, cleaning the supported metadata, and reviewing everything outside the tool's scope.
SVG workflow
Understand why metadata and XML comments can go while title and description elements stay.
Read the guideImportant boundary
Understand the difference between cleaning file properties and removing sensitive content from the document or audio itself.
Read the guideMore private file tools
Use the same local-first workflow for other supported documents and audio files.
Strip standard properties, XMP packets, application metadata, and the PDF file identifier.
Open toolClean DOCX properties, custom fields, preview thumbnails, and internal package timestamps.
Open toolClean XLSX document properties, custom fields, previews, and internal package timestamps.
Open tool