Skip to content
motifuse

Event badge with QR code template

A print-and-cut attendee badge with name, role tag, and a check-in QR code. Two badges per A4 sheet.

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.

Live preview — Event badge with QR code
The preview appears here.

Edit the values and download the PDF — generated locally in your browser, no account needed.

What this document is

An attendee badge with the event name, attendee name, organization, a role tag (attendee, speaker, volunteer), and a check-in QR code, sized for standard badge holders.

Who uses it

Conference and meetup organizers, workshop hosts, and community events that need fast, error-free check-in.

When to send it

Generate the full batch after registration closes; late registrations can be generated individually in seconds.

How batch generation works

  1. 1Open the template in the studio and adjust the layout, colors, or wording in the visual editor.
  2. 2Import your data — upload a CSV or XLSX, paste from a spreadsheet, or type a single record.
  3. 3Map your columns to the template's fields; exact matches connect automatically and fuzzy matches wait for your confirmation.
  4. 4Review validation: every row is checked for missing required values, bad dates or numbers, and duplicate filenames.
  5. 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

  • Unreadably long names overflowing the badge — the name element auto-shrinks, and the preview shows exactly how each badge fits.
  • Encoding personal data in the QR code; encode only the check-in reference.
  • Forgetting role tags for speakers and volunteers — a one-column change in the spreadsheet updates the whole batch.

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).

Frequently asked questions