UD Certificate Issuer

ProFree during beta

Issue verifiable certificates as sealed .uds documents with a unique certificate ID, recipient details, issuer, credit hours, and optional expiry.

Certificate type *

Recipient name *

Recipient email

Course / programme title

Issuer name

Issuing organisation

Issue date

Expiry date

Credit hours

Certificate ID (auto-generated if blank)

Runs in your browser. No data sent to any server. Part of the Universal Document™ ecosystem.

How UD Certificate Issuer differs from PDF certificates and Credly

PDF certificates can be forged in seconds. Credly badges require platform accounts. UD certificates are tamper-evident and verifiable by anyone with no account required.

PDF certificate

The most common format — and the easiest to forge. Anyone with Photoshop can produce an identical-looking certificate. There's no way for an employer or regulator to verify it hasn't been altered.

Credly / Acclaim digital badges

Cryptographically anchored badges requiring issuer accounts, platform integration, and recipient email addresses. Verification depends on Credly's platform remaining live and accessible.

UD Certificate Issuer — tamper-evident sealing

The certificate is sealed with a cryptographic hash at the moment of issue. Any modification to the recipient name, issuer, date, or achievement description invalidates the seal — detectable by UD Reader in one click.

UD Certificate Issuer — no platform dependency

The proof lives inside the .uds file. Verification works offline with UD Reader — no internet connection required, no Credly account, no issuer platform needed. The certificate survives platform shutdowns.