Ticket Design
Organizer Guide
4 min read
Help articles may not be fully accurate — they can lag behind the app due to frequent updates and automated translation. If in doubt, please contact support.
On this page
Ticket Design controls exactly what a ticket looks like — colours, layout, logos, and which fields are printed — for both the PDF an attendee downloads and the one attached to their confirmation email. There is a single ticket renderer behind both, so whatever the preview here shows is what gets delivered.
What you can do here
- Choose a style and layout — Modern, Minimal, Dark, or Gradient style; Standard, Compact, or Badge layout; Sans, Serif, or Mono font.
- Set colours — primary, accent, and background, each a hex value.
- Upload a logo, and separately an organizer logo or display name shown as issuer branding.
- Show or hide fields — event image, QR label, ticket type, category, price, attendee name, booking reference, ticket ID, date, and venue each have their own toggle.
- Add sponsor and partner logos to the ticket, with a position — header or footer, above or below, or sidebar for sponsors and partners.
- Set the ticket language — the label language printed on the ticket, independent of the visitor's browser language.
- Scope the whole design to one ticket type instead of the event default, for events that sell visually distinct tiers such as VIP versus General.
- Preview live and download a sample PDF before saving.
How to customise a ticket
- Pick "Design for" — the event default, or a specific ticket type if you want that tier to look different.
- Choose your style, layout, font, and three colours.
- Upload a logo and, if you want the organizer identified separately from the event, an organizer logo or a display name override.
- Turn each field toggle on or off to match what you want printed.
- Add any sponsor or partner logos you want on the ticket and choose where they sit.
- Use the live preview to check the result, then save, or download the sample PDF to see the exact delivered file.
Settings explained
- Design for (scope) — a ticket type with no design of its own inherits the event default automatically; only set a per-type design when that tier should genuinely look different.
- Display Name — overrides the organizer name shown on the ticket; leave blank to use your account name.
- Show Sponsors / Show Partners — when off, no sponsor or partner section renders at all, regardless of what logos are configured underneath.
- Logo files — JPG, PNG, or SVG, capped at 2 MB.
- Ticket language — fixed at generation time from your explicit choice here, or your own account language if you leave it unset; it does not follow the buyer's browser language, so every copy of a given ticket reads the same.
Good to know
- The saved design applies identically to the downloaded ticket and the one emailed on booking confirmation — there is a single renderer behind both, so there is no way for the two to drift apart.
- An organizer logo pulled from an external URL is fetched through a security filter: only public http/https addresses that resolve to a public IP are accepted, so a logo hosted on an internal or private address will silently fail to appear rather than load.
- Non-Latin scripts are covered by bundled fonts, so Chinese, Japanese, Korean, Thai, and Latin/Cyrillic/Greek text render correctly rather than as boxes. Arabic, Hebrew, and Indic scripts (Devanagari, Bengali, Gujarati, Tamil, Telugu) also render using their correct glyphs, but right-to-left joining and Indic conjunct/matra positioning may look slightly imperfect — legible, not pixel-perfect.
- The event's cover image only appears on the ticket when "Show event image" is on and the event isn't marked online-only.
Troubleshooting
- My uploaded logo doesn't show on the sample PDF — check the file is a JPG, PNG, or SVG under 2 MB; anything else, or anything larger, is silently skipped.
- A sponsor isn't appearing on tickets — the sponsorship must be Active or Approved and have "Show on tickets" turned on in Event Sponsors, and Show Sponsors must be on here too.
- Attendee names or venue text show as boxes or look garbled — this typically only affects Arabic, Hebrew, or Indic-script text where shaping, not the glyphs themselves, is imperfect; the underlying characters are still correct.
- My changes to one ticket type's design also changed another — check whether "Design for" was left set to the event default; a per-type override only applies once you scope the form to that specific type.