Inkscape Custom SVG Metadata Extensions Explained

When saving a drawing as a native “Inkscape SVG,” Inkscape embeds proprietary XML namespaces and metadata directly into the standard SVG structure to preserve editing state, parametric shapes, and GUI configurations. This article breaks down the custom namespaces Inkscape uses—primarily inkscape and sodipodi—and details the specific attributes, elements, and metadata tags injected into standard SVG code.

The Custom XML Namespaces

Standard SVG documents adhere to the W3C specification under the default XML namespace. Inkscape augments this by declaring two primary custom namespaces in the root <svg> element:

In addition to these, Inkscape often references standard metadata namespaces, including RDF (xmlns:rdf), Dublin Core (xmlns:dc), and Creative Commons (xmlns:cc).

Workspace and Editor State (<sodipodi:namedview>)

Inkscape stores user interface and viewport parameters within a <sodipodi:namedview> element. This block contains settings that standard SVG renderers ignore, including:

Layer Management

SVG specifications do not include a dedicated <layer> element; all hierarchical grouping is handled by the standard <g> tag. Inkscape simulates layers by tagging standard group elements with custom attributes:

Parametric Geometry and Node Metadata

When raw paths are drawn or primitive shapes are created, Inkscape saves the parametric variables necessary to re-edit them later using interactive handles:

Live Path Effects (LPE)

Inkscape’s Live Path Effects perform non-destructive modifications on paths. Because web browsers only render the computed geometry stored in the standard d attribute, Inkscape stores the underlying non-destructive parameters separately:

Standardized Document Metadata

Inkscape includes a <metadata> tag within the root SVG containing Dublin Core and Creative Commons schemas. This section commonly contains:

Managing Custom Metadata

These extensions ensure full non-destructive editability inside Inkscape without breaking web compatibility, as standard SVG renderers simply ignore unrecognized XML namespaces.

To create smaller, web-optimized files without proprietary tags, export the file via File > Save As and select Plain SVG or Optimized SVG, which strips all inkscape:* and sodipodi:* extensions while preserving the rendered visual output.