Moodle Digital Badges: How to Issue Verifiable Credentials

If you run a Moodle site, you already have a badge engine sitting inside it, most admins just never turn it on. Moodle introduced Open Badges support back in version 2.5 (2013), and the feature has been quietly improved across every major release since. By Moodle 4.x, the badging module is mature, stable, and genuinely useful for issuing verifiable credentials to learners without buying additional software.

That said, Moodle badges have real limitations. The design editor is basic, the analytics are thin, and the learner experience around sharing on LinkedIn is rougher than it should be. So this guide covers both sides: how to get Moodle's native badging working properly, and when it makes sense to extend it with a dedicated platform.

What "Verifiable" actually means in the Moodle context

The word "verifiable" gets thrown around a lot in credentialing, so it is worth being precise. Moodle badges are verifiable in the IMS Global Open Badges 2.0 sense. When Moodle issues a badge, it creates a badge assertion, a JSON-LD document hosted on your Moodle server, that contains:

• The recipient's identity (hashed email address)
• The badge class definition (name, description, image, criteria URL)
• The issuer profile (your institution's name and URL)
• The issue date and optional expiry date
• A cryptographic signature if baking is enabled

Anyone can take a badge PNG issued by Moodle, upload it to an Open Badges validator (such as the one at openbadgesvalidator.io), and confirm whether it is genuine. That is what makes it verifiable. The badge cannot be meaningfully faked because the assertion lives on a URL that only your server controls.

What Moodle badges are not, at least not natively, is W3C Verifiable Credentials (VC). That standard, which uses Decentralised Identifiers (DIDs) and cryptographic key pairs held by the recipient, goes further. As of Moodle 4.5, native VC support is not in the platform. If you need W3C VC compliance, you would need a third-party integration or a separate credentialing platform.

Step-by-Step: enabling Moodle digital badges

Before any badge can be created or issued, you need to confirm that the feature is enabled at both the site level and the course level. These are separate switches and both must be on.

Understanding Moodle badge criteria in detail

Criteria are the heart of any automated badge system. Moodle gives you several types, and understanding the nuances prevents headaches later.

Course completion

This is the most straightforward trigger. When a learner meets all the conditions set in the course completion rules, activity completion, grade, self-completion, Moodle awards the badge. The badge evaluates whenever a completion event fires, so there is usually no perceptible delay between the learner finishing and the badge appearing in their profile.

Activity completion

You can require completion of one or more specific activities (quizzes, assignments, lessons, SCORM packages) with optional grade conditions. The criteria editor lets you choose whether any one of the selected activities must be completed (OR logic) or whether all of them must be completed (AND logic). This is useful for multi-module credentials.

Manual award

A teacher or manager with the appropriate role can award a badge manually. This is the right approach for credentials where human judgment matters, peer presentations, capstone projects, observable skills. You can configure which roles are permitted to issue each badge under the criteria settings.

Competency completion

If your Moodle site uses the competency framework (under Site Administration → Competencies), you can tie badges to demonstrating one or more competencies. This is the most sophisticated option and works well for skills-based programmes where a single course does not tell the full story.

Site badges vs. course badges

Moodle supports two distinct badge scopes, and choosing the right one matters for your credential architecture.

If you are building a programme badge that requires learners to complete three separate courses, use a site badge with multiple course completion criteria. Course badges cannot reach outside their own course.

How the verification chain works

When Moodle issues a badge, it bakes the assertion data into the PNG image file using steganography, specifically, the Open Badges specification's baking approach that stores a JSON-LD assertion URL (or the assertion itself) in the image metadata. Here is what happens end to end:

1. Learner earns badge, Moodle creates a BadgeAssertion JSON-LD object and stores it in the database, hosted at a unique URL on your Moodle server.
2. Badge is baked, Moodle embeds the assertion URL into the badge PNG. The learner downloads this baked PNG from their profile.
3. Learner shares badge, They upload the PNG to LinkedIn, their portfolio, or an email signature.
4. Employer or institution verifies, They upload the PNG to an Open Badges validator. The validator extracts the assertion URL from the image, fetches the JSON-LD from your Moodle server, and checks the issuer, recipient hash, and signature.
5. Verification confirmed, As long as your Moodle server is live and the assertion URL is accessible, the badge verifies successfully.

Designing effective Moodle badge images

Moodle's built-in badge image editor is minimal, you upload an image file, and that is essentially it. The platform does not have a badge design canvas. This is one of the more significant gaps for institutions that want credentials to look credible and branded.

A few practical rules for badge images:

• Use SVG or high-resolution PNG: Moodle accepts both. SVG scales infinitely, so it looks sharp at any size on a LinkedIn profile or CV.
• Keep it square: The standard badge display is square. Non-square images will be letterboxed, which looks unprofessional.
• Include your institution's name or logo: The badge image is often the first thing an employer sees. Make it identifiable at a glance.
• Avoid text-heavy designs: At 90×90 px (the minimum display size), any more than four or five words of text becomes illegible.
• Use colour consistently: Assign badge colours by credential level (e.g., bronze/silver/gold) or by programme area so recipients can build a coherent display of their achievements.

If your team has design capacity, create badge templates in Figma or Illustrator and export them as SVG. If not, free tools like Canva have badge templates that can be adapted, just make sure the final export is clean and the institution name is legible.

Moodle badges vs. dedicated credentialing platforms

Native Moodle badges work well for straightforward use cases. But they have real gaps that become apparent once you start scaling or when recipients want a better sharing experience. Here is an honest comparison.

For small institutions or single educators issuing a few dozen badges a year, Moodle's native tools are perfectly adequate. For larger programmes, or anywhere the learner experience and credential longevity genuinely matter, layering a dedicated platform on top of Moodle is worth the investment.

Platforms like IssueBadge.com offer a free starter plan that lets you test the workflow before committing. The typical integration pattern is: Moodle triggers the award (via course completion or a grade threshold), and a webhook or manual CSV export sends that data to the credentialing platform, which handles the hosted badge page, recipient email, and sharing.

Issuing badges at scale: practical considerations

Once your badge setup is working for a handful of learners, you will inevitably face scale questions. Here are the issues that trip up most institutions when they move from pilot to production.

Cron job frequency

Moodle evaluates badge criteria via its cron scheduler. By default, Moodle's cron runs every minute, but badge processing may be batched. On busy servers, there can be a lag of minutes to hours between a learner meeting the criteria and the badge actually appearing. If learners expect their badge immediately on completing a course, test your cron setup thoroughly. Increasing cron frequency or manually running php admin/cli/cron.php can help during high-volume periods.

Email deliverability

Moodle sends badge award notifications via email. If your server's outbound email is not configured with proper SPF, DKIM, and DMARC records, these notifications will land in spam. This is a system administration issue, not a badge issue, but it affects the perceived quality of the credential programme significantly. Use a transactional email service (Mailgun, Postmark, SendGrid) connected to Moodle's SMTP settings to ensure reliable delivery.

Backpack integration

Moodle lets learners push badges to an Open Badges backpack. The original Mozilla Backpack was discontinued; the current standard is Badgr Backpack (now Canvas Credentials). In Moodle 4.x, you can configure the backpack URL under Site Administration → Badges → Backpacks. Learners can then export their Moodle badges to their backpack and include them in cross-institutional displays.

Badge expiry and revocation

Moodle supports expiry dates on badges, which is important for credentials that need renewal (CPD, compliance training, first aid certification). When a badge expires, the assertion remains on the server but carries an expiry date in the metadata, validators will show the badge as expired. Moodle does not currently support revocation of individual badge assertions from the admin UI without direct database intervention. For credentials where revocation is important, a dedicated platform with proper revocation tooling is a better fit.

A real-World configuration example

Consider a university running a 10-week online data science course in Moodle. Here is how a reasonably sophisticated badge setup might look.

Badge configuration:

• Badge type: Course badge
• Criteria: Course completion (which is itself triggered by: all quizzes submitted + final exam ≥ 70% + peer assignment marked complete)
• Expiry: None (programming fundamentals do not expire)
• Image: Institution-branded hexagon badge with the Python logo and institution name, exported as SVG from Figma
• Issuer email: credentials@university.edu

After enabling the badge, the institution tested with three dummy accounts and verified the badges at openbadgesvalidator.io. They also set up their Moodle SMTP to route through Postmark, so badge notification emails arrive reliably. Learners receive an email notification, log in to Moodle, and download their baked badge PNG from their profile. The institution added a note in the course completion message pointing learners to a guide on adding the badge to LinkedIn.

This setup required about two hours of configuration, cost nothing beyond the existing Moodle server, and has been running reliably for two cohorts. That is what Moodle native badging looks like at its best.

FAQ: Moodle digital badges