For event organisers and conference teams

Every attendee’s badge and ticket, from one registration export.

Name, company, tier and a check-in code on every badge, rendered from the CSV your ticketing platform already gives you. Send the ZIP to the printer, or have your booking system call the API per purchase.

100 free renders a month · Print-ready PDF and the API on every plan · No credit card

A conference name badge template with an attendee name, company and QR code
The job today

Badge day usually goes one of three ways.

One export per attendee

Type the name, adjust the company line so it fits, export, repeat for four hundred people. It is an all-hands afternoon before the event, and there are always a few typos at the registration desk.

Canva Bulk Create

Fine for a meetup. For a conference, rows are capped per batch, every attendee is a page of one long document, and a different check-in code per row is a requirement worth testing before you trust it.

Word label merge

Merging onto badge-insert sheets fills the names, but alignment drifts across the sheet, long names wrap or get cut, and a per-attendee QR code needs field codes most people have never used.

Already on Canva? Where Bulk Create stops, and when it is still the better answer →

How it works

From a list of attendees to finished badges, in three steps.

  1. Pick a badge and bind the fields

    Start from a badge or ticket template. Bind the big line to {{attendee_name}}, the smaller one to {{company}}, and the QR code to {{attendee_id}}. Tickets work the same way, with the code bound to a QR or a barcode.

  2. Export attendees from your ticketing platform

    One row per attendee. Rows are checked before anything renders, so a missing name or a code the QR cannot hold is flagged before the print run, not at the door.

  3. Send the PDFs to the printer

    A ZIP with one print-ready PDF per attendee, at the physical size of your badge holder. Reprint a single badge on the day from the editor.

The fields that change per badge

{{attendee_name}}
The large line — auto-fit matters, names vary a lot in length.
{{company}}
Organisation, shown smaller beneath the name.
{{ticket_tier}}
Speaker, VIP, staff, general — often drives a colour or lozenge.
{{attendee_id}}
Bound to the QR code for check-in scanning.

In practice: One CSV export from the ticketing platform, one batch, print-ready PDF to the printer. Booking systems generally call the API per purchase and attach the render to the confirmation email. Fixed-capacity events batch the whole allocation from a CSV up front.

Read the walkthrough: How to Number Event Tickets (And Why the Number Isn't Enough) →
Sample data

Start from a spreadsheet that already fits.

The column headers are the variable names above. Paste your own attendees under them, or use the sample rows to try a template first.

event-badges-sample.csv 8 sample rows
attendee_namecompanyticket_tierattendee_id
Alexandra Whitfield-MontgomeryNorthwind LabsSpeakerATT-000101
Tomás HerreraBrightline StudioGeneralATT-000102
Yuki TanakaKestrel SystemsVIPATT-000103
Ngozi OkaforHarbour & PineGeneralATT-000104
Lars JohanssonFjord AnalyticsStaffATT-000105
Download event-badges-sample.csv
Templates

Start from a design that is already done.

Every template opens in the editor with its fields ready to bind. Change anything; the layout is yours.

Built for output that has to be right

The details that make badges usable.

A check-in QR code per attendee

Bind the QR code to {{attendee_id}} and every badge carries the ID your check-in app scans. Codes are drawn sharp at any size, so they read from a lanyard as well as from a phone screen.

Learn more

Built at your badge size

Set the canvas in millimetres or inches to match the insert, for example 4 × 3 in or A6 (105 × 148 mm), and the 300 DPI PDF comes out at that physical size. Anything up to A5 prints on the Free plan.

Learn more

Tickets with the barcode your scanner reads

Bind {{ticket_code}} to a QR code or to a Code 128, EAN-13, UPC, Code 39 or ITF-14 barcode. Decide the numbering scheme before the first batch; the walkthrough below covers how.

Learn more
One template, three ways to fill it

Upload the list, call the API, or ask your assistant.

Upload a spreadsheet

Drop the CSV in the app, match columns to fields, download a ZIP. No code.

Batch from CSV

Call the API

Your registration system, for the whole list.

POST /api/v1/batch-jobs
X-Api-Key: YOUR_API_KEY
Idempotency-Key: summit-2026-badges

{
  "template": { "templateId": "{template_id}", "format": "pdf" },
  "rows": [
    { "attendee_name": "Yuki Tanaka", "company": "Kestrel Systems",
      "ticket_tier": "VIP", "attendee_id": "ATT-000103" },
    { "attendee_name": "Lars Johansson", "company": "Fjord Analytics",
      "ticket_tier": "Staff", "attendee_id": "ATT-000105" }
  ],
  "callbackUrl": "https://example.com/hooks/zandovi"
}
# → 202 · jobId · a signed callback when the ZIP is ready
API reference

Ask your AI assistant

Connect Claude or ChatGPT once. It designs, checks and renders real templates you can edit later.

Make a badge for everyone in attendees.csv. Put the attendee ID in a QR code and make the tier easy to spot.

Template checked and saved. Batch submitted, one badge per row. Here is the ZIP.

Connect your assistant
Pricing

What a list of 400 attendees costs on each plan.

Every batch job has a row cap set by your plan, from the app and the API alike. A longer list runs as several jobs, two at a time, and every row is one render against your monthly quota. Failed rows are refunded.

Plan Price / mo Rows per job Renders / mo 400 attendees
Free $0 25 100 More than a month’s renders
Personal $29 100 5,000 4 jobs
Studio $49 200 12,000 2 jobs
Team $79 300 25,000 2 jobs
Business $199 400 100,000 1 job

400 attendees is an example, not a limit. Prices exclude VAT; annual billing is two months free. Full pricing and what counts as a render →

Questions

Event badges and tickets, asked and answered.

What does the QR code on a badge contain?
Whatever is in the column you bind it to, usually the attendee or ticket ID from your registration export. Your check-in app decides what a scan does; Zandovi renders the code and does not run check-in.
Which barcode formats can tickets use?
QR, Code 128, EAN-13, UPC, Code 39 and ITF-14, each bound to a variable. Check which one your door scanners expect before the first batch.
Can I reprint one badge on the day?
Yes. Open the template in the editor, type the corrected name and export. On paid plans, exports from the editor do not count against your render quota.
Can our ticketing platform generate a ticket per purchase?
Yes. Call the generate endpoint when an order completes and attach the PNG or PDF to the confirmation email, or ask for a hosted link instead of the file.
How big can a badge be?
Up to A5 on Free, A4 and US Letter on Personal, and A3 on Studio and above, all as print-ready PDF at 300 DPI. Most badge inserts are well under A5.

Badge day, done before the coffee is.

Open a badge template, bind the name, company, tier and QR code, and render the attendee list. Free forever, no credit card.