OXPS content provenance
Content provenanceContent provenance: The record of where a piece of content came from and how it changed, carried with the content itself. for OXPS files is a signed C2PA manifestC2PA manifest: The signed label itself: a small package inside a file that records who signed it, what they declared and how to check it. inside the file. Anyone can check who signed it and whether it changed, for free.

- File
- .oxps, .xps, MIME typeMIME type: The standard name for a file format, such as image/jpeg or audio/wav, that software uses to decide how to read a file.
application/oxps - Where the label sits
- Inside the file, in its own entry inside the ZIP package that holds the pages.
- Standard
- C2PAC2PA: The Coalition for Content Provenance and Authenticity: the group that publishes the open standard for content labels., the open standard for content labels.
- Made for
- Print-ready pages, Archives, Fixed-layout documents
What Encypher supports for OXPS
- SignSupported
Encypher signs OXPS files under C2PA 2.2 and 2.4.
- CheckSupported
Free in the browser checker, with no account.
- Formal conformanceNot yet
Not in our formal conformance record. That record is a narrower test than signing and checking.
How to check a OXPS file
Open the free checker.
It runs in your browser. No account needed.
Open the checkerAdd your OXPS file.
Drop it in or pick it from your device.
Read the result.
It shows who signed and what they declared, such as AI use. It also shows if the file changed.
Where the label sits in a OXPS file
The file is a ZIP package of entries. The label is one entry of its own.

OXPS (OpenXPS) is a fixed-layout page format, like PDF. Windows printing and some archives use it.
What keeps the label on a OXPS file

- Sending and saving the file keep the label.
- Changing the text after signing shows as a change.
- Printing, scanning or exporting to another format makes a new file without the label.
For engineers
Show the technical detail
- Embedding
- JUMBF manifest store in the META-INF/content_credential.c2pa entry of the OpenXPS ZIP package
- Accepted MIME types
- application/oxps, application/vnd.ms-xpsdocument
- Signing versions
- C2PA 2.2, 2.4
- Verification
- Any version. The checker reads any C2PA manifest it can parse, and the report names the version it checked against.
curl -X POST https://api.encypher.com/api/v1/sign/media \
-H "Authorization: Bearer $ENCYPHER_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-F "file=@example.oxps" \
-F "title=My OXPS file" \
-F "action=c2pa.created"curl -X POST https://api.encypher.com/api/v1/public/verify/media \
-F "file=@signed-example.oxps" \
-F "mime_type=application/oxps"Support rows come from the live API capability matrix. Full reference: C2PA media types.
Create. Mark. Endure.
Sign your first OXPS file free. Checking stays free for everyone.