Skip to content

Glossary

What Is QR Code Verification?

QR code verification puts a scannable code on the certificate itself, so anyone holding a copy — printed or digital — can reach the issuer's own record of it in one scan.

Also called: certificate QR code, scan to verify

What it's for

A verification link only helps the person holding the digital original. Print the certificate, photograph it, or paste it into a slide, and the link is gone — the document is back to being a picture that has to be taken on trust.

A QR code survives all of that. It's part of the artwork, so it travels wherever the certificate travels: printed on a wall, screenshotted into a group chat, or held up to a camera.

How it works

The code encodes the certificate's verification URL. Scanning it opens the issuer's own record for that specific certificate — not a generic "verify here" page where someone has to type a number in.

Three things separate a QR code that works from one that's decoration:

  • It points at one certificate. A code that opens a general lookup form is barely better than printing the domain name.
  • It survives printing. Enough size and enough quiet space around it. QR codes carry error correction, so they tolerate a scratch or a fold, but not being shrunk into a corner at 8mm.
  • It's on the downloaded file, not only the web page. This is the one most often missed. If the QR only exists on the hosted page, every downloaded copy is a dead end.

The Credential ID in the URL should be unguessable, since anyone who can read one code can otherwise try counting to the next one.

Where you'll see it

On event and course certificates, ID cards, professional licences, and increasingly on printed diplomas. In India it's become common on government-issued documents through DigiLocker, which has made scanning a document to check it a familiar action rather than a novel one.

In Verifycate

The certificate editor has a QR element, and its default value is the verification URL for whichever certificate is being issued — so one design produces a different, correct code for every recipient. It renders into the PNG and the print-ready PDF as well as the public page, which means a downloaded or printed certificate still resolves back to the issuer's record.

Scanning it opens the public page: issuer, recipient, issue date, and current or expired. No app, no account.

Everything on this page runs in Verifycate. The first 300 certificates are free, no card. Start for free

Common questions

How big should a QR code be on a certificate?
Around 20–25mm on an A4 print is comfortable, with clear space around it. Smaller can work, but stops scanning reliably from a phone at arm's length — which is the actual use case.
Does each certificate need its own QR code?
Yes, if the code is meant to verify. It should encode that certificate's own verification URL. One shared code across a batch verifies nothing about the individual document.
Does the QR code still work on a printed certificate?
It does on Verifycate — the code is rendered into the PNG and PDF, not only onto the web page, so a printed copy still points back to the verification page.
What stops someone copying the QR code onto a fake certificate?
Nothing stops the copy, and nothing needs to. Scanning it opens the issuer's real record, which will show a different name — so a copied code makes the forgery easier to catch, not harder.

Related terms

Issue certificates people can actually check.

Every certificate gets a QR code, a public page, and an Open Badge 3.0 credential. 300 free credits, no card.

We issued 2,000+ certificates for InCTF — winners, participants, the lot.” — Aravind BL, Amrita InCTF

Start for free

All glossary terms