Batch Certificate Generation with n8n

Generating 100+ certificates manually is a nightmare. But automating it with n8n and RenderPix is surprisingly simple. This guide walks you through setting it up, plus real performance data from testing with 200 certificates.

The Problem

You have 200 course completions in a Google Sheet. You need to generate a certificate for each one. Manually creating PNG files? That'll take forever. Your options were:

• Puppeteer script (requires hosting, maintenance, debugging)
• HTML-to-image SaaS (expensive at scale, many require templates)
• Manual design tool (Figma batch exports, Canva, etc. — limited)

What if you could just define the certificate layout once in HTML, connect a Google Sheet, hit "execute," and get 200 PNGs in 2.5 minutes?

The Solution: n8n + RenderPix

n8n is a low-code automation platform. RenderPix is an HTML-to-image API that converts raw HTML to PNG/JPEG/WebP. Together, they handle batch certificate generation without code.

Why this approach?

• No cold starts: RenderPix pre-warms Chromium, so renders start immediately
• Control: You write the HTML. Use any CSS, fonts, layout you want
• Scalable: Tested with 200 certificates in 2.5 minutes; 1000+ possible with batching
• Cost-effective: ~$9–29/month for most use cases

Step-by-Step Setup

<div style="width:100%; height:100%; background: linear-gradient(135deg, #667eea 0%, #764ba2 100%); display: flex; align-items: center; justify-content: center; font-family: Arial;">
  <div style="text-align: center; color: white;">
    <h1>Certificate of Completion</h1>
    <p style="font-size: 24px; margin: 20px 0;">{{ $json.Name }}</p>
    <p style="font-size: 18px;">Course: {{ $json.Course }}</p>
    <p style="font-size: 16px;">Completed: {{ $json.Date }}</p>
  </div>
</div>

Real Performance Data (200 certificates)

We tested this exact workflow with 200 certificate records. Here's what happened:

Breakdown

• Fastest render: 304ms (simple HTML)
• Slowest render: 600ms (complex layouts)
• Average per render: 496ms (Chromium)
• API overhead: ~250ms per request (queue, network, request roundtrip)
• Usage quota consumed: 200 renders (from 10,000/month Pro limit)

Practical Tips

For 100–500 certificates

Just execute. 500 certificates = ~6 minutes, which fits comfortably in any timeout window.

For 1000+ certificates

Split into batches. Run 500 certificates, wait 1 minute, run the next 500. This avoids HTTP timeout (which typically caps at 5–10 minutes). The RenderPix API itself doesn't throttle, but your HTTP client does.

Optimize template rendering

Simpler HTML = faster renders. Avoid heavy images, complex CSS animations, or external fonts. Inline fonts and use data URIs for images if possible.

Save certificates efficiently

Don't download all 200 PNGs to your machine. Instead, pipe them to Google Drive, AWS S3, or email them directly from n8n. This keeps your workflow fast.

Cost Breakdown (200 certificates/month scenario)

• RenderPix Pro: $29/month (10,000 renders)
• n8n: Free tier supports this; or $20+/month for hosted
• Google Sheets: Free
• Total: ~$29/month (or $50 if using n8n cloud)

Compare that to Bannerbear ($29–99/month), htmlcsstoimage ($20–50/month), or hiring someone to design in Figma.

When to Use This vs. Alternatives

• Use this: You control the template, need bulk generation, want simple setup
• Use Figma batch exports: You need pixel-perfect design control per certificate
• Use Puppeteer: You need full flexibility and don't mind hosting/maintenance
• Use no-code template tools (Canva): You want a UI, not code

Conclusion

Batch certificate generation doesn't require custom code or expensive SaaS. With n8n and RenderPix, you can automate 200+ certificates in minutes. No rate limit issues, no timeouts, 100% reliable. Start with 10 certificates to test, scale to 1000+.

Have questions? Try RenderPix free tier (100 renders/month) or reach out on Twitter.