Print attendee badges
Updated October 5, 2026
Print one branded badge per registrant, with their ticket’s QR code, straight from the page.
What it’s for
For an in-person event, the badges are laid out for you: one card per registrant, in your brand, from the same list you work from at the door. Nothing to export and no file to build, the browser’s print dialog is the export, so a PDF comes free.
Each badge carries its holder’s ticket as a QR code, so at the door you scan the badge they are wearing.
On the “Registrants” tab of an in-person page, click “Print badges”. It always prints the whole list, whatever search or arrival filter the tab is showing.
The print view stacks one badge per registrant, alphabetically: your logo and accent color, their name, their job title and company when you collect them, their ticket’s QR code under the name, and the event with its venue.
Pick the size (A7 or A6) and the layout (several badges per A4 sheet with cut guides, or 1 per page for a badge printer) then drop what you don’t want with the Logo, Job title, Company, QR code and Event date toggles. They are all on each time you open the view.
Click “Print”. Print at 100% scale, margins set to None and background graphics on, then cut along the dashed guides.
Good to know
- Badges print one per person, not one per booking: someone attending several days gets a single badge, and the date line only appears for someone attending one day.
- Only what you collect can be printed: no job title in your form, no job title on the badge. With no name field, the badge falls back to the email.
- The QR code is the person’s ticket: the scanner on the Registrants tab, the team link and the public link read the badge exactly as they read the ticket, with the same answers. See “Scan tickets at the door”.
- The code holds the ticket alone, with no name, no email and no link, so a phone camera that is not your door scanner opens nothing. It prints black on white whatever your accent color: 24 mm on an A7, 34 mm on an A6.
- Someone attending several days wears the same badge every day: the first scan checks them in for the whole event, and later scans answer “Already checked in” without turning them away.
- A registrant anonymized by your data retention setting has no ticket, so their badge prints without a code, and the view says how many badges have none.
- Moving someone to other dates keeps their badge valid. Deleting or anonymizing them stops it working at the door, like their ticket.
- Someone you add at the desk (“Add a registrant”, or “On site” in the scanner) can be printed on their own right away: “Print badge” in the ⋯ menu at the end of their row. Their badge carries their code too.
- Past 1000 registrants the stack is capped, and the view says so rather than quietly printing a partial list.
Related articles
- Create a page from an eventStart from a Livestorm, Zoom or Microsoft Teams event: its details pre-fill the page.
- Create a Livestorm event from the builderThe event your page promotes does not exist yet? Describe it on the Event step and it is created in Livestorm for you.
- Publish your pageTake the page live at its public, crawlable and indexable address.
Still need help?
Ask AI for a docs-grounded answer, or talk to our team.
Was this article helpful?