Your certificates.
Separate, named PDFs.

1. Prepare your certificate document

Use an existing Data Merge template. The exporter reads finished certificates; it does not design them or perform the merge.

1. Use one certificate per page, one page per spread, facing pages off, no artboards, and normal page numbering beginning at 1. Keep the batch between 1 and 100 certificates.
2. In the template, put the recipient name and certificate ID in two separate, unlinked Frame Text objects. Insert the genuine Data Merge field into each. Label those layers kakulu_name and kakulu_id.
3. Each frame should contain only its value, without a “Name:” or “ID:” prefix. Use a different ID for every certificate: 1–40 letters A–Z, digits, underscores or hyphens. Names may repeat.
4. Save the template and Generate the merge. Make the generated document active. Check the visible names, IDs, dates and layout.

For a fictional example, use Batch_A_Recipients.csv. The first two recipients share the name Alex Rivera and have different IDs. The optional SVG background is artwork, not a ready-made Affinity template. Read the full template instructions.

2. Save the script once

1. Open Affinity → Settings → Scripting and enable scripting.
2. Allow filesystem access only to this package’s Return_Output folder.
3. Open exporter/Kakulu_Certificate_Exporter.js in a plain-text editor and copy the complete source unchanged.
4. Open Window → Scripting → Scripts Library. Create a new script and replace its starter content with the copied source. Name it Kakulu Certificate Exporter.
5. In that script’s settings, enable filesystem access. Keep network access, Canva AI and dynamic code generation off. Save the script for later use.

The exporter uses Affinity’s scripting tools. You do not need Node, a terminal, an AI account or any separate paid service.

3. Preview the names

1. With the generated certificate document active, run the saved script. Choose Preview only — no PDFs.
2. Select an installed PDF preset and a new folder name for this batch.
3. In the file chooser, select Return_Output/SELECT_THIS_FILE.txt. This marker identifies your output workspace.
4. Review the page, name, ID and filename together. Use Rows to show for the next group. Click OK to save the reports.
5. Open the new .manifest.html file in Return_Output. Check every full value against the actual document before exporting.

For the sample, compare the expected filenames. The two Alex Riveras must remain separate as C001 and C002. A correct preview alone does not verify a PDF’s contents.

4. Export and inspect

1. Run the script again. Choose Export named PDFs, the same PDF preset and a fresh output subfolder.
2. Select the same output marker, review the mapping and tick its confirmation.
3. Open the resulting PDFs. Check each recipient and ID against the filename, plus fonts, accents, cropping and artwork.

For the next batch, update the original template’s source, generate again and reuse the saved script. Choose a fresh output folder each time. Do not run simultaneous exports into the same location. If an export stops, keep the partial output and diagnostic.

Tell us whether it worked → Optional; no email or certificate upload.

If you get stuck

Start with the error-message guide or the online troubleshooting table. If the template or platform falls outside this preview, the free external workflow is another route.

Full manifests can contain names, certificate IDs and local paths. Keep them private. Nothing is uploaded by the exporter.