SVG Content Provenance
Sign, embed, and verify C2PA manifests in SVG files (.svg)
What Is SVG Provenance?
Scalable Vector Graphics format for resolution-independent images. SVG provenance protects logos, icons, illustrations, and data visualizations.
With Encypher, SVG files carry their own cryptographic proof of origin. A C2PA manifest is embedded directly into the file, recording who created it, when, and whether it has been modified. Anyone can verify a signed SVG file for free, without authentication.
How C2PA Manifests Are Embedded in SVG Files
- MIME Type
- image/svg+xml
- File Extensions
- .svg
- Embedding Method
- JUMBF data encoded and stored in SVG metadata element
- Container Type
- JUMBF (XML metadata)
- Verification Pipeline
- c2pa-python (native C2PA library support)
The C2PA manifest contains a JUMBF (JPEG Universal Metadata Box Format) store with COSE-signed claims. For SVG files, the manifest is stored using jumbf data encoded and stored in svg metadata element. The signing process does not alter the image content itself. The manifest is metadata, not a modification of the pixels.
Use Cases for SVG Provenance
- Logos and brand assets
- Icons and UI elements
- Data visualizations
- Technical illustrations
- Interactive graphics
How to Sign SVG Content with Encypher
SVG signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your SVG file, and the API returns a signed copy with an embedded C2PA manifest.
curl -X POST https://api.encypher.com/api/v1/sign/media \ -H "Authorization: Bearer YOUR_API_KEY" \ -F "file=@example.svg" \ -F "title=My SVG Content" \ -F "action=c2pa.created" \ -o signed.svg
Verify SVG Provenance (Free)
Verification is free and requires no authentication. Any third party can verify a signed SVG file to confirm its origin, check for tampering, and read the embedded rights information.