Exports.

Exports pull your event's data out as files: QR code archives for a printer, guest sheets for a spreadsheet. They are generated in the background, so a large event does not tie up your browser.

Opening it

From the event sidebar, under Tools, choose Exports. The guest list's Tools menu also links straight here.

The three export types

QR Codes (PNG) produces a zip of QR images, one per guest. This is the format for dropping codes into a badge template in a design tool, or for anything that expects raster images.

QR Codes (SVG) produces the same set as vectors. Use this for print: an SVG scales to any badge size without going soft, which is what a commercial printer will ask for.

Guest Sheet (ZIP) produces a CSV per ticket tier, zipped together. Each sheet includes:

• first_name, last_name, email
• ticket, the tier name
• qr_code_url, the address of that guest's code
• source, how they registered
• registration_date
• amount_paid and payment_status
• archived
• one column per registration question on that tier
• one checked_in: column per schedule, holding the time they were checked in

That last group is what makes the guest sheet the file to reach for after an event: attendance per session, per guest, in one row.

Requesting an export

Choose New Export, pick the type, and confirm. The job is queued and the page shows it with a status:

• Pending, waiting to start
• Processing, being built
• Completed, ready to download
• Failed, something went wrong

Refresh the page to see it move. Large events take longer, and there is no need to sit and watch.

Downloading

A completed export has a download link. The file is a zip in all three cases.

Deleting exports

Exports do not tidy themselves up. Delete the ones you no longer need, particularly guest sheets, because an export is a file containing your attendees' personal details sitting outside the application.

Attendance for one schedule

For a single session's attendance rather than the whole event, the door desk has a direct CSV download with first_name, last_name, email, ticket and checked_in_at.

That is usually the faster answer when a timing provider or a sponsor wants one session's list.