Open Badges

← Credentials

Open Badges is an open standard for describing an achievement as a portable, machine-readable record. Mozilla started it in 2011; the 1EdTech Consortium (formerly IMS Global) now maintains it. A badge states who issued it, who earned it, what had to be done to earn it and, optionally, the evidence. Because the format is public and vendor-neutral, a badge earned on one platform can be displayed, checked and stored on another.

This page draws on the Badges guide v1.1 (EUNIS SIG, July 2026), Badges and Digital Credentials in Higher Education, published by the EUNIS Special Interest Group – Mobility & Digital Credentials (EUNIS SIG), and on the 1EdTech specification documents listed under Sources.

An Open Badge is not the same as a simple digital badge. A digital badge can be little more than an image inside one learning platform. An Open Badge carries structured metadata, can be verified by any party (at least for issuer and recipient), and is not tied to a single vendor. The word “open” is about portability and interoperability; it says nothing about how demanding the criteria are.

Open Badges 3.0: what changed

1EdTech announced the final release of Open Badges 3.0 on 29 May 2024, together with Comprehensive Learner Record (CLR) 2.0, which was developed alongside it. The specification has been maintained since through document revisions and errata rather than new version numbers: the current text (document version 1.4.5, June 2026) is still “Open Badges 3.0”, and the JSON-LD context has moved through point versions up to context-3.0.3.json. The change from 2.x is structural, not cosmetic: every Open Badges 3.0 credential is a W3C verifiable credential.

AspectOpen Badges 2.0 / 2.1Open Badges 3.0
Data model1EdTech’s own JSON-LD vocabulary: Assertion, BadgeClass, IssuerW3C Verifiable Credentials Data Model 2.0: OpenBadgeCredential (also AchievementCredential) with an Achievement inside credentialSubject
VerificationMostly hosted: the verifier fetches the assertion from the issuer’s URL; signed JWS assertions optionalCryptographic proof carried by the credential. Certification tests Data Integrity proofs (eddsa-rdfc-2022 or ecdsa-sd-2023); the specification also describes a VC-JWT encoding
Issuer identityAn HTTPS URL pointing to an issuer profileA Profile identified by a URL or a DID (for example did:web or did:key), with keys resolvable for verification
RecipientUsually a hashed email addressA subject identifier, preferably a DID, so the holder can prove control in a presentation
Holder controlBadge lives on the platform or in a “backpack”; the learner shares a linkLearner holds the credential in a wallet and presents it, optionally inside a verifiable presentation
Status and revocationRevocation list published by the issuer, checked onlinecredentialStatus with W3C Bitstring Status List (BitstringStatusListEntry, purpose revocation) as the tested and recommended option
Wallet compatibilityBadge-specific backpacks and the 2.1 Badge Connect APIAny wallet that handles W3C VCs with the supported proofs, plus the 1EdTech OAuth 2.0 API for transfer between platforms

Open Badges 3.0 as a W3C verifiable credential

In practice, an Open Badges 3.0 credential follows the issuer, holder and verifier triangle described on Verifiable credentials. Its @context lists the W3C credentials v2 context and the Open Badges 3.0 context, and its type includes VerifiableCredential and OpenBadgeCredential. The issuer signs it; the learner keeps it; any verifier can check the signature, the validity dates (validFrom, validUntil) and the status entry without asking the issuer to vouch for it. 1EdTech also publishes schemas for VCDM 1.1, so older credentials can still be read.

Three related pieces complete the picture. An EndorsementCredential lets a third party, such as a professional body, sign a statement supporting a badge, an achievement or an issuer. CLR 2.0 bundles many achievement credentials into one signed learner record, using the same achievement model, so a transcript-like record and individual badges share one vocabulary. And the 1EdTech conformance programme certifies three roles (Issuer, Displayer and Host, the last including the API service consumer and provider requirements); certified products appear in the 1EdTech directory. A Displayer, for instance, must show valid, expired and revoked badges correctly and support both Data Integrity cryptosuites.

Because it uses JSON-LD contexts and a detachable proof, Open Badges 3.0 sits squarely on the W3C-VC side of the two stacks, not the SD-JWT VC side. That is what makes it technically compatible with European Digital Credentials in the DC4EU/EBSI lineage, which build on the same data model. Compatibility with the EUDI Wallet is a separate matter. Today the binding annexes of the wallet implementing regulations name SD-JWT VC and ISO/IEC mdoc, and the Architecture Reference Framework (ARF v3.0) treats W3C VCDM as optional and only for non-qualified attestations. That is not the end of the story: a recital of Implementing Regulation (EU) 2026/1731 notes that W3C VCDM is the reference format for attestations in education and says EUDI Wallets should also support it once new W3C VCDM profiles are available. See EUDI Wallet for the details.

What Open Badges 3.0 still does not provide

  • European Learning Model semantics. There are no native fields for EQF level, ECTS workload, assessment method or a quality assurance reference. Those belong to the ELM, which European Digital Credentials implement.
  • Legal standing. A valid signature proves integrity and origin, not legal effect. Open Badges 3.0 confers no status as a qualified electronic attestation of attributes under eIDAS 2.0, and no link to EU trusted issuer registries.
  • EU microcredential conformance. The 2022 Council Recommendation on micro-credentials lists mandatory elements that a badge alone cannot express in a recognised, comparable way.
  • A production profile with EDC. No established interoperability profile between Open Badges 3.0 and EDC is yet in production use; harmonisation is ongoing.

What Open Badges can and cannot guarantee

Open Badges are good at making learning visible. They give structure to recognition that would otherwise go unrecorded, they can be launched quickly with modest governance, and they suit non-formal and informal learning, extracurricular activity, skills and professional development. Issuer and recipient can be checked: through the hosted assertion in 2.x, and cryptographically from 3.0 onwards, provided the issuer runs proper key infrastructure.

They do not, on their own, secure recognition within EU administrative and recognition procedures, legal validity under eIDAS 2.0, cross-border comparability, or enforcement of quality assurance. Their social value is real, but it depends on platforms more than on frameworks: if the hosting platform changes its terms, is sold or closes, a 2.x badge that relies on hosted verification can stop working. Version 3.0 reduces that risk, because the proof travels with the credential, but only while the issuer’s keys and status list stay resolvable.

Where Open Badges add most value

Use caseFitWhy
Skills visibility and professional profilesHighSimple to share on professional networks; employers recognise the format
Milestones and motivation during a courseHighMarks participation and progress as it happens
Non-formal and informal learningHighCriteria can be set locally with little overhead
Volunteering, leadership, extracurricular workHighFast to launch; no quality assurance procedure needed
Continuing professional developmentHighAlready used by many national CPD schemes
Formal microcredentials under the 2022 RecommendationNot conformantELM fields missing; use EDC
Cross-border recognition and Erasmus processesLowNot part of the EU recognition infrastructure

The two formats are not rivals. A common pattern is to issue the EDC as the formal institutional record and an Open Badge that points to it for the learner’s public profile; or to use badges for milestones during a programme and an EDC at completion. A short way to remember it: the badge is the view, the EDC is the evidence, and governance supplies the trust. See The combination model for the scenarios in detail.

What Open Badges demand from institutions

The technical bar is far lower than for EDC, but a badge programme still has running costs and decisions that belong to governance, not IT.

RequirementWhat it involves
Issuing serviceAn LMS plug-in or a separate platform, plus a defined process for who issues what, and on which criteria.
Hosting and keysFor 2.x, assertions must stay online; for 3.0, issuer keys, DID documents and status lists must stay resolvable. With a third-party host, secure continuity in the contract.
Criteria and evidenceWritten criteria for every badge type. A badge without them tells a reader nothing and will be ignored.
Expiry and revocationA policy on validity periods and grounds for revocation, decided by the institution rather than left to platform defaults.
Data protectionA GDPR data processing agreement with any external provider: names, emails and achievements are personal data.
Issuing authorityClear rules on who may create a new badge type and issue in the institution’s name, to prevent badge sprawl.
CommunicationA plan for telling learners what badges mean and how to use them; otherwise many are never claimed or shared.

As the Badges guide puts it, “Open Badges are not plug-and-play.” The technology is easy to start; the institutional commitment is the same as for any other form of recognition.

Key points

  • Open Badges 3.0 (1EdTech, final release May 2024) makes every badge a W3C verifiable credential; the current text aligns with VCDM 2.0.
  • Verification moves from fetching a hosted assertion to checking a cryptographic proof; revocation uses Bitstring Status List.
  • Open Badges 3.0 belongs to the W3C-VC stack and shares its foundation with DC4EU/EBSI credentials, which makes combination feasible.
  • Technical compatibility is not semantic or legal equivalence: no ELM fields, no eIDAS standing, no microcredential conformance.
  • Badges show and motivate; EDCs accredit. Most institutions will benefit from both.

Sources

← Credential lifecycle  ·  Credentials  ·  European Digital Credentials →