How to what hidden metadata in svg files reveals about your workflow
- Step 1Inspect an SVG export — Open any Figma or Illustrator SVG in a text editor. Look at the root <svg> tag — you'll see xmlns declarations revealing the design tool, and a <metadata> block with creator information.
- Step 2Identify sensitive metadata — Look for: generator attributes (Illustrator 28.0, Figma 1.x), sodipodi: and inkscape: namespaces, dc:creator, cc:Work, and rdf:RDF blocks, which can contain author names and file paths.
- Step 3Decide what to keep — Accessibility metadata (<title>, <desc> with meaningful content) should be kept. Editor-specific namespaces, version numbers, and generator credits can be safely removed.
Frequently asked questions
What does a typical Figma SVG export contain?+
Figma exports include xmlns:xlink, a comment with the Figma version, and sometimes rdf: metadata blocks. They're cleaner than Illustrator but still carry unnecessary namespace declarations.
What does Adobe Illustrator embed in SVG?+
Illustrator embeds extensive metadata: cc:Work blocks with author and rights info, dc:format, rdf:RDF elements, xmp:CreatorTool (showing the exact Illustrator version), and proprietary ai:* namespace attributes.
Can SVG metadata expose internal company information?+
Yes. Some older Illustrator versions embed the file system path where the SVG was saved (e.g., /Users/designer/Company/ProjectName/). This reveals directory structures and project names.
Is scrubbing SVG metadata required for GDPR?+
Not legally required, but recommended. If SVGs are published on your website and contain personal data (e.g., author names), scrubbing supports GDPR's data minimisation principle.
Privacy first
Every JAD SVG tool runs entirely in your browser using the DOM API and Canvas. Your SVG files never leave your device — verified by zero outbound network requests during processing.