Personalized certificates. One design, a CSV of names.

Reuse your course certificate for every participant. Keep the logo and layout in the template, then supply names, course titles and dates from your spreadsheet.

Prepare a certificate batch Download example CSV

Decide what stays in the design.

Create and save a single-page certificate in the visual editor. Keep your logo, course description and authorized signature artwork as fixed elements. Use separate text objects for the recipient’s name, the course and the completion date.

In Automate, expose the fields that should change. Those saved variables determine the mapping available in bulk rendering. The column names below are examples; map them to your actual variables.

Leave space for the longest name in the group and check accented characters in your chosen font. A certificate records the information you supply; Pikstrapi does not verify course completion or accreditation.

One participant per CSV row.

Export your spreadsheet as a comma-separated CSV. Include a unique header for each field. This small fictional dataset includes a long name and a course title containing commas so you can check both layout and parsing.

recipient_name,course,completion_date
Alex Morgan,Visual design,2026-10-09
José María Fernández de la Vega,"Automation, data and design",2026-10-09

Download the complete example CSV

Dates are text: choose the wording you want printed before exporting the CSV. For example, replace 2026-10-09 with 9 October 2026 if that is your design’s format. A field containing commas needs quotation marks; quotation marks inside a field are escaped as two quotation marks.

Use only recipient information needed for the certificate. The sample does not contain real student records.

Map the columns before submitting.

Open Bulk Renders, select your certificate template and wait for its variables to load. Choose the certificate slide if the template has several pages.
Upload the CSV. Map recipient_name to the name variable, course to the course variable and completion_date to the date variable.
Review the preview rows and any default values. An empty cell can use the configured default; do not leave a sample recipient as the default for a real batch.
Choose PNG for an image or PDF for a document. First run a small test with the longest name, then submit the full participant list.

Each row submits one deferred render for the selected slide. Keep the submission screen open until all rows have been queued. Rendering then continues on the server.

Check the certificate before sending it.

Review completed job status and the actual file. Queued or processing does not mean ready to deliver.
Inspect name spelling, line breaks, course title, date, image quality and signature placement. Test the PDF in the viewer or print size you will use.
Retry a failed row only after reading its error. A retry is a new render and uses the normal credit accounting.

PDF export contains a rasterized image of your visual canvas. It is suitable for a fixed design, but it does not turn the certificate into editable PDF text or a fillable form.

Learn how PDF rendering and combining completed PDFs work

Use the same design for the next course.

Keep the approved template, replace the participant CSV and review the variable mapping. If course completions already arrive through an automation, use the API or n8n HTTP guide to send that event’s values to the template.

Create your certificate batch