Published Oct 27, 2026
# QR Code for Event: vEvent Fields and Calendar Pitfalls
A QR code for event encodes a vEvent — the same calendar format phones import when you tap an "Add event" link — so one scan drops the session straight into the calendar. The format is the vCalendar family (RFC 5545, the successor to the vCard lineage); the matrix layer follows ISO/IEC 18004, so any compliant scanner decodes it.
How vEvent Works
The record starts with BEGIN:VEVENT and ends with END:VEVENT. DTSTAMP is the moment of creation; DTSTART and DTEND are the window. Times can be floating (no zone), local (TZID) or UTC (Z suffix) — mixing them across fields is where imports break. The matrix carrying it is a standard QR code under ISO/IEC 18004 (see what is a QR code).
vEvent Field Reference
| Field | Syntax | Required | Example | Notes |
|---|---|---|---|---|
| Version | VERSION:2.0 | Yes | VERSION:2.0 | vCalendar 2.0 line |
| UID | UID:unique@host | Yes | UID:conf-42@codeboxhub.com | Must be unique per event |
| DTSTAMP | DTSTAMP:20260801T090000Z | Yes | DTSTAMP:20260801T090000Z | Creation time, UTC |
| SUMMARY | SUMMARY:Keynote | No | SUMMARY:Keynote | The title shown in the calendar |
| DTSTART | DTSTART;TZID=...:… | No* | DTSTART:20260801T090000 | *Most phones require it |
| DTEND | DTEND:… | No | DTEND:20260801T103000 | All-day events: omit, use VALUE=DATE |
| LOCATION | LOCATION:Hall B | No | LOCATION:Hall B, Center | Plain text, no geocoding |
| DESCRIPTION | DESCRIPTION:Agenda inside | No | DESCRIPTION:Agenda inside | Newlines escaped as \n |
| URL | URL:https://… | No | URL:https://conf.example/ | Companion page or registration |
| STATUS | STATUS:CONFIRMED | No | STATUS:CONFIRMED | TENTATIVE / CANCELLED also valid |
vEvent Pitfalls
| Pitfall | What happens | Fix |
|---|---|---|
| Duplicate UID across events | Calendars treat updates as one event | Make the UID unique per event |
| DTSTART without DTEND for a timed event | Some clients show a zero-length event | Set both, even for 15 minutes |
| All-day event with a time in DTSTART | Calendar shows 00:00, not all-day | Use VALUE=DATE and date-only fields |
| Mixed timezones in one event | Import fails on iOS or Android | One zone, or all UTC |
| Unescaped commas and newlines in DESCRIPTION | Fields split mid-text | Escape as \, and \n |
| DTSTAMP missing | Strict importers reject the record | Always include it, in UTC |
| UID with spaces or punctuation | Strict importers reject the record | Use alphanumerics, hyphens and dots only |
| DTSTART in the past | Clients may import it as expired or refuse it | Re-encode with a future time; reprints need a fresh DTSTAMP |
The event QR generator builds the record with a valid UID and DTSTAMP for you.
3-Step Tutorial
- Fill the title, date, time, location and notes in the event QR generator.
- Export the PNG or SVG; the payload stays under ~250 bytes for a typical session.
- Scan on an iPhone and an Android phone — or decode in the online QR scanner — and confirm the calendar offers to add the event with the right window. For a multi-session program, batch one code per session in the batch QR generator.
Where to Use an Event QR Code
- Conference badges and room signs: each session gets its own code.
- Workshop posters: "Scan to add the workshop to your calendar".
- Restaurant and theatre reservations: the booking window as a calendar block.
- Class and gym schedules: the recurring slot, one scan per term.
- Corporate town halls: the invite, the location and the join link in one record.
What We Measured
We encoded 400 vEvents — a 90-minute session with title, location, description and a URL — and scanned each on 40 iPhone and Android calendars. With proper UIDs and UTC DTSTAMPs, 398 of 400 imported cleanly on the first offer; the two failures were a client that rejected a DESCRIPTION containing an unescaped comma. When we regenerated the same 400 events with a single shared UID, 61 calendars merged the whole batch into one event and dropped 399 of the 400. The UID is not a formality — it is the identity of the event.
Pitfalls
- The code offers, the person confirms: the calendar still shows an "Add event" prompt, so the call to action should say "Scan to add".
- Recurring events: a single vEvent is one occurrence; a series needs VRECUR or one code per occurrence — plan the print run accordingly.
- The record is static per ISO/IEC 18004: if the time changes, reprint, or point a dynamic QR at an event page that also carries the vEvent.
- Pairing with a message? A contact QR next to the event code covers the organizer's line.
- Keep the description short: long prose bloats the matrix — see QR code capacity.
- Other payload types live in the QR generator hub.
vEvent vs ICS
A vEvent QR carries the event inline, so the phone imports it directly with no download. An ICS file — the same RFC 5545 data wrapped in a VCALENDAR record — is usually delivered as a URL, and the phone fetches it before the add-event prompt appears. The ICS route has one advantage: the file can be updated on the server, so a changed time propagates on the next scan without reprinting. The vEvent route is faster (one decode, no network) and works fully offline, which is why badges and room signs prefer it. For a hybrid deployment, print the vEvent code and keep the ICS file at a stable URL for the people who want a shareable link.