How to Generate Hundreds of Certificates From a Spreadsheet

Producing a hundred certificates by hand — duplicating a design, retyping each name, exporting one PDF at a time — is slow and easy to get wrong. The moment you have more than a handful, the work belongs to a spreadsheet and a template, not a person. This guide covers the standard pattern for bulk certificate generation from Excel or CSV, and how our own tool implements it end to end.

The pattern, in four steps

1. 01Design one certificate template with placeholders for the values that change.
2. 02Put your data in a spreadsheet — one row per certificate, one column per field.
3. 03Map each column to a placeholder: name to recipient name, course to title, date to completion date.
4. 04Generate a personalised PDF for every row in a single batch.

Everything else — fonts, layout, logo, signature — is fixed once in the template and reused for every record. That separation of design from data is what lets the job scale from ten certificates to ten thousand without any extra effort per certificate.

Designing the template once

Start with the fixed design: background, borders, logo, signature block, and any body text that stays the same on every certificate. Then drop in placeholders wherever a value changes — typically the recipient's name, the course or achievement, and the date. A visual drag-and-drop designer like the one in CertifyAI lets you position each placeholder exactly where the text should land and set its font, size, and alignment. Spend the time here once. Every certificate in the batch inherits this layout, so a well-placed name field is the difference between a clean run and re-exporting the whole set.

Mapping spreadsheet columns to fields

Your spreadsheet is the data source. Use one row per certificate and a header row that names each column. Keep the values clean: no stray spaces, consistent date formatting, and one column per field you intend to place on the certificate.

The import step reads your Excel or CSV file and asks you to connect each column to a placeholder. Once the mapping is set it applies to every row, so adding fifty more recipients means adding fifty more rows — nothing else changes.

Generating and verifying at scale

With the template fixed and the columns mapped, generation is a single pass: each row's values are substituted into the layout and rendered to its own PDF. Doing this at scale is a rendering problem, not a design one — CertifyAI is built on Konva for the canvas designer and pdf-lib for export, running on Next.js and Supabase, so producing hundreds of files is a batch job rather than hundreds of manual saves. If your certificates need to be checked later, add a QR code per record that links to a verification page; CertifyAI generates these as part of the same batch, so every certificate carries a scannable proof of authenticity without a separate step. It runs live at certificateco.vineetbuilds.workers.dev.