Polotno SDK is the design layer for event platforms: organizers design tickets, badges, certificates, and promo graphics inside your product, and the render pipeline personalizes them per attendee, names, seat numbers, QR check-in codes, at registration time. One editor and one schema cover the whole visual surface of an event, from the announcement post to the badge on the lanyard. This is production infrastructure for registration flow, not optional UI.
The event-visuals sprawl
An event's visual assets are scattered by default: tickets from the registration vendor's fixed templates, badges from a desktop app someone runs the night before, social graphics from a designer's queue, certificates from a mail-merge macro. Every asset repeats the same data, event name, date, venue, attendee, through a different tool with a different idea of the brand.
Platforms consolidate this by owning the design layer. One governed template set per event; organizer edits in the embedded editor; attendee data flows through at render time. The QR code that gates entry is generated per ticket from your check-in payload. See the QR automation guide for the specs that make codes scan reliably at a door.
Key features
Organizer self-serve design
Organizers customize tickets, badges, and graphics from your template library, brand elements locked, event details open, without leaving your platform.
Per-attendee personalization
Names, ticket tiers, seat assignments, and QR payloads render per registration via dynamic variables. A 3,000-attendee event is 3,000 render calls, not a design task.
Check-in QR codes
Generate per-ticket QR codes from your check-in tokens at render time, sized and error-corrected to scan from phone screens at a busy door.
Badge printing
Badges export as print-ready PDFs at standard badge sizes, batched per event, ordered for the printer or the on-site printing station.
Event marketing kit
The same editor produces the social announcements, banners, and email headers. Organizers reuse the event's template set instead of a second tool.
Post-event certificates
Attendance certificates issue automatically from the attendee list. Same pipeline, see certificate generation.
Example use cases
- Registration platforms rendering personalized tickets with QR check-in on purchase.
- Conference tools batch-printing badge PDFs per attendee list.
- Event marketing suites where organizers design promo graphics from governed templates.
- Community and meetup platforms auto-generating event cover images from event data.
- Awards and ceremony platforms issuing programs, place cards, and certificates from one template set.
Developer benefits
- One JSON schema across tickets, badges, graphics, and certificates.
- Render at registration time via polotno-node or the Cloud Render API. No render infrastructure on your side if you don't want it.
- QR and barcode payloads per attendee via template variables.
- Editor governance keeps organizer designs on-brand and printable.
- Attendee data never leaves your pipeline when rendering self-hosted.
FAQs
Can tickets carry per-attendee QR codes?
Yes. Payloads generate per record at render time; size and error-correction settings that survive phone-screen scanning are covered in the QR guide.
How fast can we render for a large event?
Batch rendering handles thousands of assets; for spikes (on-sale moments), the Cloud Render API scales without your involvement.
Can organizers design badges themselves?
Yes. Templates lock the layout and check-in zone; organizers edit branding and text in the embedded editor.
What print formats do badge printers get?
PDF at standard badge dimensions with bleed where required, batched in attendee order.
Does attendee data go through Polotno's servers?
Only if you use the Cloud Render API. Self-hosted rendering keeps registration data entirely in your infrastructure.
