Course completion certificate template
A landscape certificate with course, grade, and verification QR — designed for training institutes and online academies.
Try this template
1 · Edit the data
2 · Download the PDF
Generated locally in your browser. Nothing you type here is uploaded, stored, or sent to a server.
Edit the values and download the PDF — generated locally in your browser, no account needed.
What this document is
A completion certificate recognizes that a learner finished a course or training program. This landscape design includes the course name, completion date, grade, a unique certificate number, and a QR code that links to your verification page.
Who uses it
Training institutes, online academies, corporate learning teams, bootcamps, and workshop organizers.
When to send it
Generate the full batch when a cohort finishes. The certificate number and QR verification URL come from your spreadsheet, so each certificate is individually verifiable.
How batch generation works
- 1Open the template in the studio and adjust the layout, colors, or wording in the visual editor.
- 2Import your data — upload a CSV or XLSX, paste from a spreadsheet, or type a single record.
- 3Map your columns to the template's fields; exact matches connect automatically and fuzzy matches wait for your confirmation.
- 4Review validation: every row is checked for missing required values, bad dates or numbers, and duplicate filenames.
- 5Generate: up to 25 documents locally in your browser for free, or hundreds through a secure cloud batch with per-row results.
Common mistakes to avoid
- Reusing certificate numbers across cohorts — keep them unique in your data; duplicate output filenames are flagged before generation.
- Printing names with inconsistent casing from a registration form export; clean the data first (Reconova helps) since the certificate renders the name exactly as supplied.
- Pointing QR codes at pages that do not exist yet. Publish your verification page before distributing certificates.
Privacy
The preview above and all local batches run entirely in your browser — names, amounts, and other values are never uploaded. Cloud batches are explicit, isolated per workspace, protected by short-lived signed links, and deleted at the end of a visible retention window (or earlier, on your request).