In 2015, a certificate of completion from an online course carried meaningful weight on a LinkedIn profile. By 2026, most certificates carry roughly the weight of a well-designed PDF — which is to say, almost none. This isn't a complaint about course quality. It's a coordination problem: the signal value of a completion certificate collapsed when anyone could buy any course, click through to the certificate, and claim the achievement on a CV. Recruiters learned faster than the credential infrastructure could adapt.
What's emerging in response is a different category of credential entirely — one designed to be verifiable rather than issued. The distinction matters more than it sounds. This piece walks through what a verifiable credential actually is, why this shift is happening now specifically, where the major course platforms (including ours) actually stand on this, and what creators should look for when their certifications are meant to mean something.
What a verifiable credential actually is
The term verifiable credential refers to a specific technical standard maintained by the W3C — the same standards body responsible for HTML, CSS, and the protocols that make the web work 1. The W3C Verifiable Credentials Data Model defines a credential as a digitally-signed data structure with three roles: an issuer (the institution making the claim), a subject (the learner the claim is about), and a holder (whoever is currently presenting the credential to a verifier).
What separates a verifiable credential from a PDF certificate is the cryptographic layer. A verifiable credential is signed by the issuer's private key, contains a tamper-evident hash of its contents, and can be verified by any third party — an employer, a regulator, a peer institution — using only the issuer's published public key. Verification doesn't require contacting the issuer's database, doesn't require the issuer to still be in business, and doesn't depend on a centralized verification service that might disappear. The credential proves itself, mathematically, on inspection.
A complementary standard, Open Badges 3.0, profiles the W3C Verifiable Credentials specification specifically for educational and skill credentials 2. It adds the structure for things like what assessment was passed, what evidence supports the claim, and what skills are being credentialed — turning the abstract VC standard into something a recruiter or admissions officer can actually parse.
Mature implementations of this stack already exist. Accredible has issued verifiable credentials at scale for major universities and certifying bodies for several years. Credly, now part of Pearson, manages one of the largest credentialing networks globally. Affinidi has been a notable infrastructure player for businesses building verifiable-credential issuance into their products. The European Union's EUDI Wallet initiative is rolling out verifiable credentials as continental infrastructure for everything from identity to academic qualifications, with mandatory adoption across member states underway through 2026 3. India's DigiLocker, while not strictly W3C VC-compliant, operates on adjacent principles for government credentials.
The standards exist. The infrastructure exists. The question for course creators in 2026 is whether their platforms have caught up.
Why this shift is happening now specifically
Three forces, converging:
Recruiter trust collapse on completion certificates. Hiring managers in 2024-2025 began openly stating, in surveys and on LinkedIn, that course-completion PDFs no longer factor into evaluation. The reason isn't that recruiters became cynical — it's that they were burned enough times by candidates whose certificates didn't reflect actual capability. The trust collapse isn't ideological; it's empirical 4.
AI-assisted cheating made weak credentials weaker. A certificate that confirms "the candidate completed the course" means little when the course's assessments could be passed with Claude, ChatGPT, or Gemini one keystroke away. Credentials that don't include integrity-of-assessment evidence — proctoring records, lockdown-browser sessions, AI-resistance design — are being discounted accordingly. The cornerstone of this series, The 2026 Course Creator Playbook, addresses the assessment-integrity shift in detail.
Regulatory pressure is now real. The EU's EUDI Wallet rollout creates a mandatory verifiable-credentials infrastructure for European citizens, which means cross-border recognition of educational credentials increasingly requires standards compliance. India's DPDP Act 2023 doesn't mandate W3C VC specifically, but it does mandate auditable, learner-controlled credential issuance — which is structurally what the verifiable-credentials standard provides. Non-compliant credentials will become administratively harder to integrate into formal recognition systems through 2026-2028.
The combined effect is that the credential trust model is shifting from "trust the issuer's reputation" to "verify the credential's evidence" — and the platforms that issue credentials are being asked to support the second model, not just the first.
Where course platforms actually stand in 2026
Honest survey across the major platforms:
Most independent course platforms — including the largest ones — are still issuing PDF certificates. Teachable, Thinkific, Kajabi, Graphy, LearnyST, and Tag Mango all primarily issue static PDF certificates, sometimes with verification URLs that point back to the platform's own database. These are not verifiable credentials in the W3C sense — they are centralized assertions, dependent on the platform's continued operation and trustworthiness for their verification value. If the platform goes offline, the certificate's verifiability goes with it.
A handful of education-specific platforms have moved further. Coursera and edX issue what they call "verified certificates" but the verification is mostly through their own infrastructure rather than W3C VC standards. LinkedIn Learning issues Open Badges 2.0 (the older standard) but not yet broadly to 3.0. Some university-affiliated programs issue full W3C VC credentials through partnerships with Accredible or Credly — but this is still the exception in the broader course-creator economy.
The honest summary: as of 2026, the course-creator economy as a whole is still on the wrong side of the credential transition. Most of what gets issued is a PDF, sometimes signed at the metadata level, occasionally pointing to a centralized verification URL. Genuine W3C Verifiable Credentials are rare in this category — common in formal education and enterprise certifying bodies, but uncommon for the independent-creator and academy market.
This isn't a moral failing of the platforms; it's a reflection of where customer demand has been. Verifiable credentials require engineering investment, and most course platforms have prioritized other features because their customers haven't been asking for VC support specifically. That's now starting to change as the credential trust model shifts.
Where Skolarli stand
Skolarli has built W3C Verifiable Credentials issuance into the platform through a partnership with one of the pioneers in the verifiable-credentials space. Learners completing assessment-gated courses on Skolarli — credentials are issued only on assessment completion, never on participation alone — can receive their credential via a verifiable-credentials wallet, issued to the W3C VC standard using the OID4VCI credential-offer flow.
The integration sits alongside Skolarli's own certificate-issuance path. Customers whose use case requires standards-compliant verifiable issuance can opt into the W3C VC path; customers whose certificate needs are simpler use Skolarli's native certificate flow, which produces both PDFs and web-based credential pages on skolarli.me/[learner] with QR-coded linking and assessment-evidence visibility.
The verifiable-credentials path is available on customer request, not yet a default-on feature for all programs. The honest reason: as a bootstrapped, early-stage company, Skolarli has prioritized active engineering investment where customer demand pulls it, and the W3C VC path is being held in a customer-on-request mode until that demand justifies broader rollout. The capability is built. The infrastructure works. The standards compliance is real. The customer-facing UX simply hasn't been productized as a default flow yet — and we'd rather be honest about this than overclaim a marketing-ready feature when what we have is a production-ready capability.
This positioning is, we think, the right one for a 2026 course platform: build the standards compliance ahead of mainstream demand, surface it for customers who need it now, productize it broadly when the market pulls it forward. The pull is starting; the productization will follow.
What creators should evaluate when credentials matter
A practical checklist for any creator whose programs issue certificates that are meant to mean something to a third party:
- Are the credentials issued to the W3C Verifiable Credentials standard, or to a proprietary verification mechanism? If the platform's verification depends on its own continued operation, the credential's long-term value is tied to the platform's longevity.
- Are credentials issued to a named learner with verifiable identity, or to a generic completion event? Verifiable credentials are about a specific subject; generic certificates are about a course event. The first is portable; the second is not.
- Are credentials assessment-gated or participation-gated? Recruiters in 2026 increasingly distinguish between "completed the course" and "passed an assessment for the course". The credential's signal value follows the gating.
- Does the credential link to evidence? A modern verifiable credential isn't just a claim — it links to the artifacts that justify the claim (the assessment record, the proctored session, the assignment).
- Can a third party verify without going through the issuing platform? This is the cryptographic-verification question. If verification requires visiting the platform's URL, the credential is centralized; if verification requires only the issuer's public key, the credential is portable.
- What's the platform's roadmap on standards compliance? Even if a platform isn't fully W3C VC-compliant today, a credible roadmap toward it matters for credentials that are intended to last.
These six questions cut through most marketing language about "secure" or "verified" certificates. A platform's answers will tell you whether its credentials are built for the 2015 trust model or the 2026 one.In 2015, a certificate of completion from an online course carried meaningful weight on a LinkedIn profile. By 2026, most certificates carry roughly the weight of a well-designed PDF — which is to say, almost none. This isn't a complaint about course quality. It's a coordination problem: the signal value of a completion certificate collapsed when anyone could buy any course, click through to the certificate, and claim the achievement on a CV. Recruiters learned faster than the credential infrastructure could adapt.
What's emerging in response is a different category of credential entirely — one designed to be verifiable rather than issued. The distinction matters more than it sounds. This piece walks through what a verifiable credential actually is, why this shift is happening now specifically, where the major course platforms (including ours) actually stand on this, and what creators should look for when their certifications are meant to mean something.
What a verifiable credential actually is
The term verifiable credential refers to a specific technical standard maintained by the W3C — the same standards body responsible for HTML, CSS, and the protocols that make the web work 1. The W3C Verifiable Credentials Data Model defines a credential as a digitally-signed data structure with three roles: an issuer (the institution making the claim), a subject (the learner the claim is about), and a holder (whoever is currently presenting the credential to a verifier).
What separates a verifiable credential from a PDF certificate is the cryptographic layer. A verifiable credential is signed by the issuer's private key, contains a tamper-evident hash of its contents, and can be verified by any third party — an employer, a regulator, a peer institution — using only the issuer's published public key. Verification doesn't require contacting the issuer's database, doesn't require the issuer to still be in business, and doesn't depend on a centralized verification service that might disappear. The credential proves itself, mathematically, on inspection.
A complementary standard, Open Badges 3.0, profiles the W3C Verifiable Credentials specification specifically for educational and skill credentials 2. It adds the structure for things like what assessment was passed, what evidence supports the claim, and what skills are being credentialed — turning the abstract VC standard into something a recruiter or admissions officer can actually parse.
Mature implementations of this stack already exist. Accredible has issued verifiable credentials at scale for major universities and certifying bodies for several years. Credly, now part of Pearson, manages one of the largest credentialing networks globally. Affinidi has been a notable infrastructure player for businesses building verifiable-credential issuance into their products. The European Union's EUDI Wallet initiative is rolling out verifiable credentials as continental infrastructure for everything from identity to academic qualifications, with mandatory adoption across member states underway through 2026 3. India's DigiLocker, while not strictly W3C VC-compliant, operates on adjacent principles for government credentials.
The standards exist. The infrastructure exists. The question for course creators in 2026 is whether their platforms have caught up.
Why this shift is happening now specifically
Three forces, converging:
Recruiter trust collapse on completion certificates. Hiring managers in 2024-2025 began openly stating, in surveys and on LinkedIn, that course-completion PDFs no longer factor into evaluation. The reason isn't that recruiters became cynical — it's that they were burned enough times by candidates whose certificates didn't reflect actual capability. The trust collapse isn't ideological; it's empirical 4.
AI-assisted cheating made weak credentials weaker. A certificate that confirms "the candidate completed the course" means little when the course's assessments could be passed with Claude, ChatGPT, or Gemini one keystroke away. Credentials that don't include integrity-of-assessment evidence — proctoring records, lockdown-browser sessions, AI-resistance design — are being discounted accordingly. The cornerstone of this series, The 2026 Course Creator Playbook, addresses the assessment-integrity shift in detail.
Regulatory pressure is now real. The EU's EUDI Wallet rollout creates a mandatory verifiable-credentials infrastructure for European citizens, which means cross-border recognition of educational credentials increasingly requires standards compliance. India's DPDP Act 2023 doesn't mandate W3C VC specifically, but it does mandate auditable, learner-controlled credential issuance — which is structurally what the verifiable-credentials standard provides. Non-compliant credentials will become administratively harder to integrate into formal recognition systems through 2026-2028.
The combined effect is that the credential trust model is shifting from "trust the issuer's reputation" to "verify the credential's evidence" — and the platforms that issue credentials are being asked to support the second model, not just the first.
Where course platforms actually stand in 2026
Honest survey across the major platforms:
Most independent course platforms — including the largest ones — are still issuing PDF certificates. Teachable, Thinkific, Kajabi, Graphy, LearnyST, and Tag Mango all primarily issue static PDF certificates, sometimes with verification URLs that point back to the platform's own database. These are not verifiable credentials in the W3C sense — they are centralized assertions, dependent on the platform's continued operation and trustworthiness for their verification value. If the platform goes offline, the certificate's verifiability goes with it.
A handful of education-specific platforms have moved further. Coursera and edX issue what they call "verified certificates" but the verification is mostly through their own infrastructure rather than W3C VC standards. LinkedIn Learning issues Open Badges 2.0 (the older standard) but not yet broadly to 3.0. Some university-affiliated programs issue full W3C VC credentials through partnerships with Accredible or Credly — but this is still the exception in the broader course-creator economy.
The honest summary: as of 2026, the course-creator economy as a whole is still on the wrong side of the credential transition. Most of what gets issued is a PDF, sometimes signed at the metadata level, occasionally pointing to a centralized verification URL. Genuine W3C Verifiable Credentials are rare in this category — common in formal education and enterprise certifying bodies, but uncommon for the independent-creator and academy market.
This isn't a moral failing of the platforms; it's a reflection of where customer demand has been. Verifiable credentials require engineering investment, and most course platforms have prioritized other features because their customers haven't been asking for VC support specifically. That's now starting to change as the credential trust model shifts.
Where Skolarli stands, accurately
Skolarli has built W3C Verifiable Credentials issuance into the platform through a partnership with one of the pioneers in the verifiable-credentials space. Learners completing assessment-gated courses on Skolarli — credentials are issued only on assessment completion, never on participation alone — can receive their credential via a verifiable-credentials wallet, issued to the W3C VC standard using the OID4VCI credential-offer flow.
The integration sits alongside Skolarli's own certificate-issuance path. Customers whose use case requires standards-compliant verifiable issuance can opt into the W3C VC path; customers whose certificate needs are simpler use Skolarli's native certificate flow, which produces both PDFs and web-based credential pages on skolarli.me/[learner] with QR-coded linking and assessment-evidence visibility.
The verifiable-credentials path is available on customer request, not yet a default-on feature for all programs. The honest reason: as a bootstrapped, early-stage company, Skolarli has prioritized active engineering investment where customer demand pulls it, and the W3C VC path is being held in a customer-on-request mode until that demand justifies broader rollout. The capability is built. The infrastructure works. The standards compliance is real. The customer-facing UX simply hasn't been productized as a default flow yet — and we'd rather be honest about this than overclaim a marketing-ready feature when what we have is a production-ready capability.
This positioning is, we think, the right one for a 2026 course platform: build the standards compliance ahead of mainstream demand, surface it for customers who need it now, productize it broadly when the market pulls it forward. The pull is starting; the productization will follow.
What creators should evaluate when credentials matter
A practical checklist for any creator whose programs issue certificates that are meant to mean something to a third party:
Are the credentials issued to the W3C Verifiable Credentials standard, or to a proprietary verification mechanism? If the platform's verification depends on its own continued operation, the credential's long-term value is tied to the platform's longevity.
Are credentials issued to a named learner with verifiable identity, or to a generic completion event? Verifiable credentials are about a specific subject; generic certificates are about a course event. The first is portable; the second is not.
Are credentials assessment-gated or participation-gated? Recruiters in 2026 increasingly distinguish between "completed the course" and "passed an assessment for the course". The credential's signal value follows the gating.
Does the credential link to evidence? A modern verifiable credential isn't just a claim — it links to the artifacts that justify the claim (the assessment record, the proctored session, the assignment).
Can a third party verify without going through the issuing platform? This is the cryptographic-verification question. If verification requires visiting the platform's URL, the credential is centralized; if verification requires only the issuer's public key, the credential is portable.
What's the platform's roadmap on standards compliance? Even if a platform isn't fully W3C VC-compliant today, a credible roadmap toward it matters for credentials that are intended to last.
These six questions cut through most marketing language about "secure" or "verified" certificates. A platform's answers will tell you whether its credentials are built for the 2015 trust model or the 2026 one.
Sources:
https://www.w3.org/TR/vc-data-model-2.0/
https://www.imsglobal.org/spec/ob/v3p0
https://economicgraph.linkedin.com/blog/linkedin-workforce-confidence-index