Skip to content

Glossary

What Is Bulk Certificate Generation?

Bulk certificate generation produces one personalised certificate per person from a single design and a list of recipients, instead of editing a file once per name.

Also called: mass certificate generation, batch certificates, mail merge certificates

What it's for

The manual version of this job is the same three steps repeated once per person: open the design, replace the name, export. At forty people it's a dull evening. At five thousand — a fest with sixty events — it's not a task anyone completes, which is why certificates so often arrive weeks late or not at all.

Bulk generation does it once. One design, one list, one operation.

How it works

Three pieces:

  • A template with placeholders. The design carries markers where per-person values go — a name, a university, a team, an event — instead of literal text.
  • A recipient list. A spreadsheet or CSV where each row is one person and each column maps to one placeholder.
  • A render step. Every row is merged into the template and rendered.

The details that decide whether it actually works:

  • Long names. "Dr. Lakshmi Venkataraman Subramanian" is not the same width as "Amy Wu". A design that can't shrink or wrap will clip one of them, and you won't notice until someone tells you.
  • Column mapping. Map spreadsheet columns to placeholders once, not per row.
  • A per-recipient QR code. The code has to encode each certificate's own URL, or it's decoration.
  • Fixing mistakes. With a batch this size, some names will be wrong. What matters is whether one correction means regenerating and resending everything.

Where you'll see it

College fests, hackathons, MOOCs and cohort courses, webinars, conferences, and corporate training. The traditional tooling is a mail-merge script over a Word template, or Google Sheets with an add-on like autoCrat — both of which produce files, and stop there.

In Verifycate

Place {{name}}, {{university}} or any attribute you like in the design, then drop in a CSV or Excel file — or paste the list. You map columns to Name and Email once, and any extra columns become attributes you can use in the design. Import doesn't spend credits; sending does, one per certificate.

Each recipient gets their own page, their own QR code, and their own Open Badge 3.0 credential. When a name is wrong, the recipient submits a correction from their own certificate page and you approve it from one inbox — the page updates at the same URL, no reissue, and corrections don't spend credits. On a five-thousand-certificate batch, that last part is the difference between an evening's work and a fortnight of email.

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

Common questions

How do I generate certificates for a list of names?
Put placeholders in the design where the per-person values go, then import a CSV or Excel file and map its columns to those placeholders once. Every row renders its own certificate.
Can I generate certificates in bulk from Google Sheets?
Export the sheet as a CSV and import it. Add-ons like autoCrat can merge into a Word or Slides template directly, but they produce files — no verification page, no QR code, and no way to fix a name afterwards without redoing the row.
What happens when a name is spelled wrong in a bulk batch?
In Verifycate the recipient submits a correction from their certificate page and you approve it. The public page updates at the same URL, nothing is reissued, and no credit is spent.
Is there a limit on how many certificates I can send at once?
No batch limit — issuers have sent several thousand at a time. What you need is credits, one per certificate on first issue.

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