Event tool

Calendar Event QR Code

Scan and the event is ready to add — title, start and end time, venue and notes already filled in. No link to open, no details to retype, no time zone to guess.

Event details

iCalendar (VEVENT)

Times are read in your device's time zone and stored as UTC, so they display correctly for every guest.

What is inside an event code

The payload is a small iCalendar file — the same .ics format that Outlook and Google Calendar use to send invitations. It contains a single VEVENT with a start time, an optional end time, a title, a location and a description.

Times are stored in UTC with a trailing Z, which is why the same code works for a guest in Tokyo and a guest in Toronto: each calendar app converts the stored instant into the viewer's local time. If you enter 19:00 in London, a guest in Berlin sees 20:00.

Where event codes are worth printing

  • Invitations and tickets. The guest adds the date to their calendar at the moment they open the envelope, rather than forgetting by the following week.
  • Conference signage. A session board where each talk has its own code, so attendees can build a personal schedule in seconds.
  • Recurring meetups. A poster that adds the next occurrence, printed once per cycle.
  • Retail and workshops. In-store demo sessions and classes, added straight from a shelf card.

Practical limits

Each field you fill lengthens the payload. A title, start time and location scan comfortably at 3 cm. Add a long description and the pattern becomes dense enough that you should step up to 4–5 cm. If the description runs beyond a sentence or two, put the details behind a URL instead — the calendar entry only needs to be a reminder.

This generator creates single, non-repeating events. Recurrence rules (weekly meetings, monthly sessions) are part of the iCalendar standard but are handled inconsistently by mobile calendar apps, so they are deliberately left out.

Always set an end time. A calendar entry with no end defaults to one hour in some apps and "all day" in others, which can hide the real start time in a busy week view.

Frequently asked questions

Which calendar apps understand this?

Apple Calendar, Google Calendar, Outlook, Samsung Calendar and most Android defaults all parse a VEVENT payload. The phone shows an "Add to calendar" prompt and opens the event preview rather than saving silently.

What happens with daylight saving time?

Because the moment is stored in UTC, the event lands on the correct instant everywhere. The local display adjusts automatically, so a 19:00 London event in winter shows as 20:00 in Berlin and 21:00 in Helsinki, in both summer and winter.

Can I make a recurring event?

Not with this tool. Recurrence needs RRULE support, and mobile handling of it is uneven — some apps add only the first occurrence, others add a broken series. Print a new code per date instead.

Why is the code so dense with a long note?

Calendar payloads include structural lines and escaped line breaks, so a 200-character note can produce a 400-character payload. Trim the note to what a guest needs at a glance and move the rest to a web page.

Can attendees RSVP through the code?

No. RSVP requires a server that tracks responses and sends the invitation by email, which is outside what a static code can do. Put an RSVP link in the notes field if you need one.