DOCX Content Provenance
What Is DOCX Provenance?
DOCX document format. DOCX provenance protects business documents, contracts, and enterprise content.
With Encypher, DOCX 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 DOCX file for free, without authentication.
How C2PA Manifests Are Embedded in DOCX Files
- MIME Type
- application/vnd.openxmlformats-officedocument.wordprocessingml.document
- File Extensions
- .docx
- Embedding Method
- Custom JUMBF/COSE structural embedding within the OOXML 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 DOCX files, the manifest is stored using custom jumbf/cose structural embedding within the ooxml 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 DOCX Provenance
- Business documents
- Contract drafting
- Enterprise content
- Legal drafting
- Collaborative documents
How to Sign DOCX Content with Encypher
DOCX signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your DOCX 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.docx" \ -F "title=My DOCX Content" \ -F "action=c2pa.created" \ -o signed.docx