HOW IT WORKS / FROM BADGE TO EVIDENCE
Look past the badge.
See what checks out.
A convincing image is a starting point, not a proof. Bring the original credential. We’ll help you read the evidence behind it.
Open Badges 3.0. Free to use. No account needed.
01 / THREE SIMPLE STEPS
A closer look.
Without the complicated part.
No account to create. No software to install. Just your credential, a set of technical checks and a little more context.
Start with the original.
Download the original credential from its issuer, or copy its public badge URL. A screenshot can look right without carrying anything we can verify.
Original PNG, SVG, JSON, JSON-LD, VC or JWTLet the checks do the work.
The validator reads the credential and examines its structure, proof and status. When needed, it contacts linked resources such as issuer keys and status lists.
The credential and its linked evidenceRead the whole story.
See which checks passed, failed or were skipped. Use the warnings and error codes to understand the result, not just the color at the top.
A readable, check-by-check report02 / FOLLOW THE EVIDENCE
Not a black box.
A clear set of checks.
A green result is only useful when you know what it means. See what was checked — and what couldn’t be.
Credential structure
Check that the credential can be read and contains the required Open Badges fields.
- Credential parsed
- Required fields present
- Achievement identified
- Issuer identified
03 / READ BEYOND THE HEADLINE
Three check outcomes.
One informed decision.
Not every check can run on every credential. These labels explain the individual checks — not the credibility of the issuer.
This check succeeded.
The named check completed successfully. Keep reading the other checks and any warnings before relying on the credential.
Something needs attention.
A check found a problem. Read the error code and message. An altered, expired or revoked credential, or an unsupported method, can produce a failed check.
Not the same as passed.
The check did not apply or could not run. For example, some credentials have no recipient check available. Read the context rather than treating a skipped check as a success.
A valid badge is not an endorsement.
Technical validation does not prove that a recipient completed the activity, or that an issuer is trustworthy. You still decide what the achievement means.
04 / THE RIGHT STARTING POINT
Bring the original.
Not a picture of it.
Open Badges 3.0 credentials can travel as images, structured data or signed tokens. The important part is the credential inside, not the file’s appearance.
Designed for Open Badges 3.0, with compatibility settings for some VC 1.1 credentials. Not a general Open Badges 2.0 checker.
Choose your badgeUpload a file.
Original baked PNG or SVG, JSON, JSON-LD, VC or JWT. Files are selected before you explicitly start validation.
PNG / SVGJSON / JSON-LDVC / JWTUP TO 5 MB PER FILEOr share its URL.
Paste a public link to the credential or badge resource itself — not a profile, PDF, screenshot or ordinary webpage.
UP TO 10 MB REMOTE INPUT · 5 REDIRECTS · 10-SECOND INPUT FETCHAn ordinary PNG or SVG may contain only artwork. If you see missing_baked_payload, download the issuer’s original export.
05 / A REQUEST, NOT AN ARCHIVE
Your badge takes a short trip.
It doesn’t move in.
The application processes the credential to return a report. It does not keep an application database of your badges, URLs or results.
The original credential
A selected file or public credential URL.
The available evidence
Required fields, proof and relevant status checks.
Linked issuer resources
Contexts, keys, status lists or other referenced evidence.
A report with context
Individual checks, errors and warnings.
Issuer hosts may see verification requests. Hosting infrastructure can retain ordinary access and security logs. Read the privacy policy
06 / BEFORE YOU BEGIN
A few useful answers.
Still unsure about a format or a result? The blog goes a little deeper.
Read the blogWhat does a valid result tell me?
The validator could read the credential and its required checks passed at the time of the request. Review the individual checks and any warnings. A valid result does not endorse the issuer or prove that the recipient actually completed the activity described in the badge.
Which files and URLs can I check?
Upload a baked PNG or SVG badge, a JSON or JSON-LD verifiable credential, a .vc file or a compact JWT. Individual uploads must be 5 MB or smaller. URLs may point to a credential or badge resource; remote input is limited to 10 MB, five redirects and a ten-second fetch timeout. A PDF or screenshot of a badge is not a verifiable credential.
What do failed, passed and skipped checks mean?
Passed means the named check succeeded. Failed means the check found an error, which is reported with a code and message. Skipped means the check could not run or did not apply to that credential; it is not the same as passed. Read warnings as well before relying on a result.
Are my uploaded badges stored?
No application database or file store keeps your submitted credential. The service processes it for the validation request and returns a report. Hosting providers can retain ordinary security and access logs; linked issuer hosts can see validation requests. If you choose to contact us, your message is delivered to our team by email so we can respond.
A LITTLE CERTAINTY GOES A LONG WAY.
A little clarity.
Starts with your badge.
Free for everyone. Open to every issuer.