ODT Content Provenance
Sign, embed, and verify C2PA manifests in ODT files (.odt)
What Is ODT Provenance?
OpenDocument Text format for open-standard word processing. ODT provenance covers government documents, open-source workflows, and cross-platform document exchange.
With Encypher, ODT 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 ODT file for free, without authentication.
How C2PA Manifests Are Embedded in ODT Files
- MIME Type
- application/vnd.oasis.opendocument.text
- File Extensions
- .odt
- Embedding Method
- Custom JUMBF/COSE structural embedding within the ODF ZIP container
- Container Type
- Custom JUMBF/COSE
- Verification Pipeline
- Custom JUMBF/COSE structural verification (Encypher implementation)
The C2PA manifest contains a JUMBF (JPEG Universal Metadata Box Format) store with COSE-signed claims. For ODT files, the manifest is stored using custom jumbf/cose structural embedding within the odf zip container. The signing process does not alter the document content itself. The manifest is metadata, not a modification of the content.
Use Cases for ODT Provenance
- Government documents
- Open-source workflows
- Cross-platform documents
- EU institutional documents
How to Sign ODT Content with Encypher
ODT signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your ODT 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.odt" \ -F "title=My ODT Content" \ -F "action=c2pa.created" \ -o signed.odt
Verify ODT Provenance (Free)
Verification is free and requires no authentication. Any third party can verify a signed ODT file to confirm its origin, check for tampering, and read the embedded rights information.