PDF certificates vs. verifiable credentials.
A PDF shows information to a human reader; a verifiable credential proves it to software. PDFs can be edited and must be confirmed by the issuer. Verifiable credentials are signed, checked automatically, let the holder share only what is needed, and can be revoked.
Comparison
- Authenticity: PDF relies on appearance or a portal link. Verifiable credential: digital signature of the issuer.
- Verification effort: PDF needs a manual check or a call. Verifiable credential: automatic, in seconds.
- Privacy: PDF discloses everything. Verifiable credential: the holder chooses which fields to share.
- Revocation: PDF cannot be withdrawn once sent. Verifiable credential: status list shows it is revoked.
- Machine readability: PDF is a document. Verifiable credential: structured data with shared semantics.
- Dependence on the issuer: PDF with a portal link breaks if the portal goes away. Verifiable credential: the proof stays with the holder.
When a PDF is still useful
A printable version remains useful for people and processes that are not digital yet. Many institutions issue both: the verifiable credential as the proof, and a PDF as a human-readable copy.
Moving from PDFs to verifiable credentials
Start with one certificate type that is frequently checked by third parties, define its fields, and issue it to a small cohort alongside the existing PDF. Measure how many learners claim the credential and how verifiers use it before scaling.
Questions
Can a signed PDF do the same?
A signed PDF proves the file has not changed, but it still shows all data to everyone, is hard for software to read, and cannot be selectively disclosed or checked against a revocation list in a standard way.