How it works

Built differently for each role.

Pick your role. The steps and answers are specific to how you use AcadCert.

Enter your registered address. A 6-digit one-time code is sent to you, no password to remember or lose.

Choose an upload mode

Single upload for one document. Smart Table to drop multiple files at once and auto-match them to students by filename. Bulk (CSV + ZIP) for large batches with a structured manifest.

Select the student and credential type

Pick from your institution's enrolled students. Choose Certificate, Degree, Diploma, Transcript, or Letter of Recommendation. An optional expiry date can also be set at this stage.

AcadCert signs the document

The PDF is hashed with BLAKE3, signed with your institution's private Ed25519 key, and independently timestamped by an RFC 3161 authority. The entire signing operation happens server-side. You never interact with the private key directly.

The student is notified and the credential goes live

It appears on their dashboard immediately. You can revoke or supersede any credential at any time. Every action is documented in the tamper-evident audit trail.

Three modes, each suited to different volume and workflow:

Single upload: Select one student, one document type, one file. Best for individual ad-hoc issuance.
Smart Table: Drop multiple files at once. The system auto-detects student names from filenames and lets you review, reassign, or remove matches before submission. Fastest for graduation batches where files are already named by student.
CSV + ZIP: Provide a CSV manifest mapping filenames to student emails, and a ZIP archive of documents. Batches upload directly to storage and process as background jobs, up to 1,000 documents and 5 GB per ZIP. Best for externally prepared batches or integration with your SIS.

PDF (up to 50 MB), DOCX (up to 20 MB), and JPEG or PNG images (up to 10 MB). Each file is validated before metadata is embedded and the cryptographic signature is applied. Unsupported or corrupted files are rejected before signing.

Yes. Revocation permanently marks a credential as invalid with a documented reason. Use this for errors, disciplinary actions, or any case where the credential should no longer be honoured. Supersession replaces a credential with an updated version while preserving the original for historical reference. Both actions are logged immediately and cannot be reversed.

Revoke the incorrect credential immediately with a clear reason (e.g. “Issued to wrong recipient, administrative error”), then issue a new credential to the correct student. The revocation reason is recorded in the audit log and visible to your institution's administrators.

Only students registered under your institution by an administrator. You cannot issue credentials to students at other institutions, and you cannot create student records yourself: that requires administrator access.

Prefer to see it rather than read about it? Walk through the whole issue, verify, and revoke flow yourself.

Try the live demo

Full FAQ·Security overview·Contact us