GetQRMaker

Calendar Event QR Code Generator

  • Free
  • No sign-up
  • Never expires

Add your event to people's calendars with one scan, including time, place and details.

  1. Pick a type(done)
  2. 2Add content(current step)
  3. 3Save

Type

Event

Adds the event to the calendar.

Preview

Waiting

Fill in the form above and your QR code appears here.

Size
Margin

Output 512 × 512px · 4-module margin

Add some content to turn on the save buttons.

Style

Optional · Frame, color, background, error correction, logo

Frame shape

Adds a colored border and a one-line caption around the code. Included in the saved PNG, SVG and the print sheet.

Center logo

More optionsCode color · Background · Error correction

Code color

#111111

Background

Error correction

Maximum keeps the code readable when part of it is covered or damaged, but makes it denser.

How a calendar event QR code works

The code contains an iCalendar event, the same format calendar invitations use: BEGIN:VEVENT, SUMMARY:Product launch, DTSTART:20261015T170000Z, DTEND:20261015T183000Z, LOCATION:Room 3, END:VEVENT. Times are converted from your device's time zone to UTC, marked by the Z, so each phone shows the event in its own local time.

For an all-day event, dates are written without a time, as DTSTART;VALUE=DATE:20261015. The end date in this format is exclusive, so a one-day event on October 15 ends on October 16 in the code; that is how calendars expect it, and it displays as a single day.

On iPhone, the Camera app recognizes the event and offers to add it to Calendar. On Android, support depends on the scanner: Google Lens and many camera apps show an add-to-calendar option, while some older ones only display the raw text.

Where it helps

  • A concert poster carries a code that saves the date and venue, so people who walk past do not have to remember it.
  • A school newsletter adds codes for parent evenings, putting the time and room straight into busy calendars.
  • A conference badge lists codes for each workshop, each with its room in the location field.
  • A clinic prints the next appointment as a code on the reminder card.

Tips before you print

  1. Check your device's time zone before creating the code. The time you enter is read as local time where you are, then stored in UTC.
  2. Put the room or full address in Location; many calendars turn it into a map link.
  3. Keep the description short. Practical notes such as “Bring a laptop” fit well; a full agenda makes the code dense.
  4. Add the event from your own code and confirm the date, time and duration before printing.

Questions

Will the time be right for people in other time zones?
Yes. The time is stored in UTC, so each calendar shows it in the viewer's local time. A 5 pm event in London appears at noon in New York.
Can I change the event after printing?
No. The details live inside the code. If the time or place changes, make and print a new code.
Can I make a recurring event?
Not with this generator. Each code describes a single event.
Does it add the event automatically?
No. The phone shows the event and the person chooses to add it to their calendar.

Guide: Calendar event QR codes

Anatomy of the VEVENT block

iCalendar is defined in RFC 5545, and a VEVENT is the smallest useful unit of it: a handful of property lines between BEGIN:VEVENT and END:VEVENT. SUMMARY is the title that shows in the calendar list, DTSTART and DTEND give the bounds, LOCATION is a free-text place, and DESCRIPTION holds notes. Scanner apps accept the event without the surrounding VCALENDAR wrapper, which keeps the code compact. Every character adds density, so those five properties are the practical limit for a code that still scans from a poster across a room.

Time zones without surprises

A timestamp ending in Z is Coordinated Universal Time. 20261015T170000Z means 17:00 UTC, which a phone in Seoul displays as 02:00 the next morning and a phone in Los Angeles as 10:00. That is exactly right for a webinar with scattered attendees, but it can mislead for a local concert if the organiser made the code while travelling in another zone. Daylight-saving time adds a second trap: a code made in summer for a winter date gets the winter offset automatically, yet if the venue's country changes its clock rules before the event, the stored UTC instant no longer matches the intended local time.

All-day events sidestep the issue. DTSTART;VALUE=DATE:20261015 has no clock time and no zone, so it stays on October 15 everywhere. The end value is the morning after the last day, so a three-day festival from the 15th to the 17th is written with an end of the 18th.

What happens on the phone

iOS Camera reads the block natively and shows an event card with an Add button; Apple Calendar then creates a normal, editable entry. Google Lens and most recent Android camera apps do the same, but a bare camera app on some budget devices may only show raw text, and the person then needs a calendar app that can import from a scan. Nothing is added silently in either case.

Beyond the basics, reliability drops quickly. Recurrence rules, alarm reminders, attendee lists and attachments are legal iCalendar, yet scanner apps strip or ignore most of them, and a long block becomes a dense code. Keep the event single and let people set their own reminder.

Printing and planning around it

Invitations, conference agendas with one code per session, class timetables and appointment reminder cards all work well because the date is fixed before printing. Where a date might slip, print the code on a separate insert or sticker rather than the main card. Give the end time deliberately too: a missing DTEND makes some calendars default to a zero-length or one-hour slot, which hides the event in a day view.

A venue that is hard to find pairs naturally with a location code, an RSVP can go through a WhatsApp code, and the print size guide explains how big the event code needs to be on a poster compared with a card.