How Moodle issues certificates with the Custom Certificate plugin: dynamic fields, verification codes, expiry and recertification, bulk issuance, and branded output you own.
Got an LMS decision on your plate?
45-minute call. Plain-English audit. Fixed-price quote if there's a fit, or a "no" if there isn't. No deck. No pitch.
How digital badges and verifiable credentials prove real skills, tie to recertification, and stay yours when you own the platform.
How to automate training recertification so certifications never lapse silently — and nobody works on an expired credential.
The default Moodle reports show completions. Here's how to get the audit-ready, role-filtered compliance reporting your leadership actually asks for.
For a lot of training, the certificate is the deliverable — it's what a learner keeps, what a manager files, and what an auditor asks for. Moodle can generate certificates natively, tie them to real course completion, stamp them with verification codes, and drive recertification off their expiry dates. The difference between doing that well and doing it badly usually comes down to whether you own the platform and configured it deliberately, or you're renting a credentialing add-on that charges per certificate.
This post covers how certificates work in Moodle, how to make them verifiable and expiry-aware, and why owning the setup matters for compliance-grade records. It pairs with our digital badges and credentials guide and our training recertification tracking guide.
Modern Moodle certificate management is built on the Custom Certificate plugin (mod_customcert), which superseded the older Certificate module. The essentials:
Because it's a Moodle activity, issuance is driven by the same completion engine that governs the rest of the course — one source of truth, not a bolt-on.
Two capabilities turn a nice-looking PDF into a compliance-grade record:
Together they answer the two questions an auditor actually asks: is this real, and is it still current.
Certificates rarely stand alone. In a well-built Moodle they connect to the wider credentialing picture:
The three aren't competitors — a single completion can issue a certificate, award a badge, and mark a competency at once. See our digital badges guide and Moodle competencies guide for how the pieces fit.
For an organization pushing thousands of completions, a few operational details matter:
Renting certificate management through a SaaS LMS or a standalone credentialing tool introduces two problems that compound over time:
On a Moodle you own, the templates, the verification endpoint, the issuance history, and the underlying completion data are all yours. You can rebrand, re-issue, verify, and export without asking a vendor — and without a bill that scales with your compliance obligations. That's the same own-vs-rent logic that governs the rest of the platform, applied to the artifact people actually keep.
Moodle handles certificate management properly when it's built on completion-gated issuance, verification codes, and expiry-driven recertification — and when you own the templates, the verification endpoint, and the history. Done that way, certificates stop being decorative PDFs and become a verifiable, current, exportable part of your compliance record, with no per-certificate meter running against you.