How to generate certificates in bulk from a spreadsheet
Course completions, event attendance, employee awards — every certificate is the same design with a different name. That is a render, not a design job.
·6 min read
Certificates are the purest bulk-image problem there is. The artwork is identical for every recipient; the only things that change are a name, a date, maybe a course title and a serial number. Yet most teams still produce them by hand — a designer duplicating a file, or an admin fighting a mail-merge template that mangles the typography.
With a templated render, the whole job collapses to: design once, upload the roster, collect the files.
Why mail merge keeps failing at this
Office mail merge was built for letters, not artwork. Fonts substitute silently, long names overflow the ornamental frame, and the output is a document that only looks right on the machine that made it. The failure mode is always typographic — and a certificate is nothing but typography.
A render fixes this at the root: the design is locked, the type auto-fits the field, and “Alexandra Konstantinopoulou” lands as cleanly as “Li Wei”. Every certificate is pixel-identical except the data.
PNG for the feed, PDF for the frame
The same template renders both destinations. Request PNG or WebP for the version recipients share on LinkedIn, and PDF for the version they print — one design, one roster, two format parameters. There is no second layout to keep in sync.
The details that make it production-grade
- Auto-fit type: names of any length stay inside the frame, no manual kerning pass.
- Stable URLs: every certificate has a permanent link you can put in the completion email.
- Determinism: re-running a row reproduces the identical file — reissues are exact.
- Caching: repeat requests serve from cache, so hosting the links costs nothing.
- Localisation: add a language column and the same roster renders per-market certificates.
Where teams run this
Online course platforms issue completion certificates the moment a learner finishes, by calling the render from the completion hook. Conference organisers batch the attendee list the morning after the event. HR teams keep one recognition template and render awards quarterly. In each case the certificate stopped being a design request in someone’s queue and became a row in a file.