OXPS Content Provenance
Sign, embed, and verify C2PA manifests in OXPS files (.oxps)
What Is OXPS Provenance?
Open XML Paper Specification format for fixed-layout documents. OXPS provenance covers print-ready documents and archival content.
With Encypher, OXPS 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 OXPS file for free, without authentication.
How C2PA Manifests Are Embedded in OXPS Files
- MIME Type
- application/oxps
- File Extensions
- .oxps
- Embedding Method
- Custom JUMBF/COSE structural embedding within the OpenXPS 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 OXPS files, the manifest is stored using custom jumbf/cose structural embedding within the openxps 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 OXPS Provenance
- Print-ready documents
- Archival documents
- Fixed-layout publishing
How to Sign OXPS Content with Encypher
OXPS signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your OXPS 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.oxps" \ -F "title=My OXPS Content" \ -F "action=c2pa.created" \ -o signed.oxps
Verify OXPS Provenance (Free)
Verification is free and requires no authentication. Any third party can verify a signed OXPS file to confirm its origin, check for tampering, and read the embedded rights information.