Event QR Code Generator
Generate a calendar QR code that stores an event title, location, description and date/time information.
This generator keeps the GS1 Digital Link URI directly inside the QR code. Premium QR dynamic redirects are not used for GS1 Digital Link codes.
Advanced Customization
Colors & Gradients
Logo & Social Icon
QR Code Size
Event QR Code Generator
Quick answer: A calendar event QR code encodes an iCalendar VEVENT block per RFC 5545. Scanning it prompts the device to add the event to the installed calendar app. The payload includes event title, start time, end time, location and description. Payload size grows with each additional field, which increases module density — a relevant constraint for small print sizes.
How to create a calendar event QR code
- Enter the event title (the SUMMARY field in the VEVENT block).
- Set the start date and time and the end date and time.
- Choose UTC time (append Z to the time) or a named timezone using TZID — for example TZID=America/New_York — to avoid daylight-saving ambiguity.
- Add an optional location string and an optional description. Keep both concise to control payload size.
- Customise the pattern style, finder-eye style, colours and logo if needed, then download as PNG, SVG, WEBP or JPG at up to 4096 px.
The code is generated in your browser. Nothing you enter is uploaded to a server.
What a calendar event QR code is
A calendar event QR code is a standard QR code whose payload is an iCalendar VEVENT block. iCalendar is defined in RFC 5545 (2009), which superseded RFC 2445. The QR symbol itself follows ISO/IEC 18004, the international standard for QR Code symbology.
When a user scans the code, the operating system passes the .ics data to the default calendar application — Apple Calendar on iOS and macOS, Google Calendar on Android, and compatible third-party apps on other platforms. The app then presents an "Add to Calendar" prompt. The user must still confirm; scanning does not add the event silently.
Because the event data is encoded directly in the QR pattern, the code is static. It works offline, requires no server, and does not depend on any third-party calendar service. However, it cannot be edited after printing. If the event details change, the code must be regenerated and reprinted.
iCalendar VEVENT payload format
Full structure
A minimal but complete VEVENT payload for QR encoding looks like this:
BEGIN:VCALENDAR VERSION:2.0 PRODID:-//PremiumQRCodes//EN BEGIN:VEVENT UID:[email protected] DTSTAMP:20261015T120000Z DTSTART:20261015T140000Z DTEND:20261015T160000Z SUMMARY:Annual Product Review LOCATION:Conference Room B, 10 Main Street, London DESCRIPTION:Q3 results presentation and Q4 planning session. END:VEVENT END:VCALENDARField-by-field reference
| Field | RFC 5545 property | Required in practice | Notes |
|---|---|---|---|
| Calendar container start | BEGIN:VCALENDAR | Yes | Wraps the VEVENT |
| Version | VERSION:2.0 | Yes | Always 2.0 for RFC 5545 |
| Product ID | PRODID | Yes | Identifies the generating app |
| Event container start | BEGIN:VEVENT | Yes | |
| Unique identifier | UID | Yes | Any unique string; domain-qualified |
| Timestamp | DTSTAMP | Yes | Apple Calendar requires it; Google Calendar Android refuses import without it |
| Start date/time | DTSTART | Yes | See time format section below |
| End date/time | DTEND | Required in practice | Google Calendar prompts if missing |
| Summary (title) | SUMMARY | Yes | Displayed as the event name |
| Location | LOCATION | Optional | Shown in calendar and maps apps |
| Description | DESCRIPTION | Optional | Additional text; increases payload size |
| Event container end | END:VEVENT | Yes | |
| Calendar container end | END:VCALENDAR | Yes |
Time formats and timezone handling
The date/time format in RFC 5545 is YYYYMMDDTHHMMSS. Two forms are relevant for QR encoding:
UTC form (recommended for fixed-time events): DTSTART:20261015T140000Z The trailing Z means the time is in UTC. All devices interpret the same absolute moment in time.
Local form with named timezone (recommended for events where local time is stated): DTSTART;TZID=Europe/London:20261015T140000 The TZID parameter names the IANA timezone. Calendar apps resolve daylight-saving rules locally.
All-day event (date-only form — no T or Z): DTSTART;VALUE=DATE:20261015 DTEND;VALUE=DATE:20261016 The end date for an all-day event is the day after the event, per RFC 5545 convention.
Using UTC (Z) is the simplest format and avoids daylight-saving edge cases, but it means the event appears at a different clock time for attendees in different time zones. Use TZID when the event has a stated local time that should display correctly everywhere.
Payload size and module density
This is the critical practical constraint for event QR codes.
Each character added to the VEVENT payload increases the number of data bits, which raises the QR code version (the number of modules), which reduces the size of each module at a fixed print size. A dense module grid at small print size becomes harder for a camera to resolve.
Rough character budgets at common error correction levels:
| Error correction | Byte capacity (Version 10) | Version 10 modules |
|---|---|---|
| L | ~271 bytes | 57×57 |
| M | ~213 bytes | 57×57 |
| Q | ~151 bytes | 57×57 |
| H | ~115 bytes | 57×57 |
A minimal VEVENT with title, UTC start and end times, and no location or description encodes in approximately 180–220 bytes. Adding a full street address for LOCATION and a two-sentence DESCRIPTION can push the payload to 350–500 bytes, requiring a higher version (more modules) and consequently a larger print size.
Practical guidance:
- Keep SUMMARY to 40 characters or fewer.
- Keep LOCATION to the shortest recognisable form (venue name and postcode).
- Keep DESCRIPTION to 80 characters or fewer, or omit it and put detail on the printed material.
- If the description must be long, print the code larger or link to a web page from within the description and shorten the DESCRIPTION field itself.
- Use error correction level M for general use. Use H only if adding a centre logo.
When to use a calendar event QR code
Printed conference programmes. A QR code beside each session adds it to an attendee's calendar with one scan, including room number and speaker name in the LOCATION and DESCRIPTION fields.
Wedding invitations. A code on the invite encodes the ceremony start and end time, the venue, and a short description. Guests scan it once and all devices remind them on the day.
Webinar and online class registration. A code in a confirmation email or on a course webpage encodes the exact start time in UTC — removing the timezone confusion that causes attendees to miss the start.
Trade-show stands and pop-ups. A code on the stand banner lets visitors scan the next session or demo time directly into their calendar rather than hoping they will remember to add it later.
Printed event tickets. A code on the ticket encodes the event details so the calendar reminder appears even if the recipient loses the ticket or forgets the venue.
Recurring class schedules. A code on a gym or studio timetable can encode an individual class so participants can add just that session rather than the whole schedule.
Design and print requirements
Maintain a quiet zone of at least four modules on all sides, as required by ISO/IEC 18004.
For a business card or folded programme insert, print at 2 cm by 2 cm minimum. For a table tent or window poster, use 3 cm or more. For a large banner, use 8 cm or more.
Because event QR codes can carry substantial payloads (250–500+ bytes depending on description length), print larger than the 2 cm minimum whenever possible. A 3 cm code with a 400-byte payload is more reliably scanned than a 2 cm code with the same payload.
If embedding a logo, use error correction level H, which recovers approximately 30% of codewords. This ensures the modules covered by the logo can be reconstructed during scanning.
Test the printed code with both an iPhone and an Android device before mass distribution. The calendar import behaviour differs between platforms and it is better to discover a format issue before 500 invitations are posted.
Troubleshooting: why your calendar QR code is not adding the event
DTSTAMP is missing. Apple Calendar silently ignores VEVENT blocks without a DTSTAMP property. Add a DTSTAMP in UTC format. Google Calendar on Android also refuses import without it.
DTEND is missing. Google Calendar may prompt the user to complete the event. Always include DTEND even if it equals DTSTART.
The time shows in the wrong timezone. If you used UTC (Z), attendees in a different time zone will see the correct absolute time but a different clock reading. Switch to a TZID named timezone so the local time is explicit.
The payload is too long. A code printed at 2 cm that encodes a 500-byte payload will be too dense for a camera at arm's length to resolve. Shorten the DESCRIPTION and LOCATION fields and reprint, or print larger.
The QR code is static — event details changed after printing. Event QR codes cannot be edited. Regenerate with the updated details and reprint. Consider using a URL QR code pointing to a hosted calendar invite page for events whose details may change.
The calendar app shows an import failure. Confirm the VCALENDAR wrapper (BEGIN:VCALENDAR / END:VCALENDAR) is present. The VEVENT alone is not a valid .ics file without the wrapping component.
Static event QR codes versus URL-based calendar invites
A static VEVENT QR code encodes the full event data in the pattern itself. It works offline, needs no server, and cannot be updated after printing.
| Static VEVENT QR code | URL QR code (calendar page) | |
|---|---|---|
| Payload | Full VEVENT block | A URL pointing to a calendar invite |
| Works offline | Yes | No — URL must resolve |
| Editable after printing | No | Yes — update the page |
| Depends on a service | No | Yes |
| Calendar app import | Direct — native import prompt | Varies by how the page is built |
| Best for | Print invitations, single-date events | Events where details may change |
Use a static VEVENT code for any event where the details are confirmed before printing and the audience may scan in a location without reliable data (a venue entrance, a paper invitation). Use a URL-based approach for events with evolving details — encode the URL of a hosted invitation page and update that page when details change.
What this Event QR Code Generator gives you
This browser-based tool creates an iCalendar VEVENT payload that offers to add a dated event to the user’s calendar. It is designed for conferences, appointments, launches, training sessions, weddings and community events. The live preview updates while you edit, which makes it easier to catch a missing field or an unexpectedly dense symbol before download.
You can adjust matrix patterns, finder-eye styles, foreground and background colours, gradients, frames, size and an optional logo. Exports are available as SVG, PNG, WEBP and JPG at 512, 1024, 2048 or 4096 pixels. SVG is the practical choice for professional print. A high-resolution PNG suits office documents and digital artwork.
The static payload is constructed in your browser. The information entered into the generator does not need to be uploaded to create the QR image. Calendar applications interpret time zones and reminders differently, so test the payload on iOS, Android and desktop calendar software.
Using this QR code in Bahrain and abroad
Set Bahrain events to Asia/Bahrain time and state whether the time is local, particularly when invitations may be scanned by overseas guests.
Use British English spelling in customer-facing copy when that matches your organisation’s house style, and provide Arabic wording where the audience expects it. Keep the action after scanning obvious. A short line beside the symbol such as “Scan to save the contact” or “Scan to open the location” gives people confidence before they point their camera.
Test the final design on current iPhone and Android devices. Test it again after printing on the actual paper, sticker, card, sign or packaging material. Bahrain’s bright outdoor light can expose glare and low-contrast problems that are less obvious on a computer screen. For international use, confirm country codes, currencies, time zones, regional app availability and payment-network compatibility.
Before you publish
- Correct QR payload type
- Complete and verified data
- Four-module quiet zone
- Strong foreground contrast
- Proportional square scaling
- Logo kept within safe limits
- SVG or high-resolution PNG
- Final-size device scan test
Frequently asked questions
Open a question to read a concise technical answer.
01What is the iCalendar VEVENT format for a QR code?+
The iCalendar VEVENT format is defined in RFC 5545. A QR-encoded event wraps a VEVENT block inside a VCALENDAR container. Required fields are DTSTAMP (a creation timestamp), DTSTART (event start) and SUMMARY (event title). DTEND, LOCATION and DESCRIPTION are optional but strongly recommended for calendar app compatibility.
02Does a calendar event QR code work on iPhone and Android?+
Yes, on both platforms, but with differences. iOS opens the VEVENT data in Apple Calendar. Android opens Google Calendar or the default calendar app. DTSTAMP is required for Apple Calendar and Google Calendar on Android. Always include it and always include DTEND to avoid import errors on either platform.
03How do I include a timezone in a calendar event QR code?+
Use the TZID parameter in the DTSTART property: DTSTART;TZID=America/New_York:20261015T140000. This uses IANA timezone names and lets each calendar app apply local daylight-saving rules. Alternatively, use UTC by appending Z to the time (DTSTART:20261015T190000Z), which specifies the same absolute moment for all attendees regardless of location.
04Can I update a calendar QR code event after I have printed it?+
No. A static VEVENT QR code encodes the event data directly in the pattern. Once printed it cannot be changed. If the event details may change after printing, encode the URL of a hosted event or registration page and update that page instead.
05Why is DTSTAMP required in a calendar QR code?+
DTSTAMP represents the date and time the iCalendar object was created, per RFC 5545. Apple Calendar silently ignores VEVENT blocks that lack DTSTAMP, meaning the event will not be imported even if DTSTART is correct. Google Calendar on Android also refuses import without DTSTAMP. Always include it.
06How do I create an all-day event in a calendar QR code?+
Use the date-only form of DTSTART and DTEND without a time component: DTSTART;VALUE=DATE:20261015 and DTEND;VALUE=DATE:20261016. Per RFC 5545 convention, the DTEND for an all-day event is the day after the event date, not the same day.
07Why is my event QR code too dense to scan?+
A long DESCRIPTION or LOCATION field increases the payload size, which raises the QR code version and packs more modules into the same print area. Shorten the DESCRIPTION to 80 characters or fewer, reduce the LOCATION to a venue name and postcode, and either print the code larger or remove the DESCRIPTION entirely.
08What happens when someone scans a calendar event QR code?+
The scanning device recognises the iCalendar VEVENT data and passes it to the default calendar application. The calendar app displays an "Add to Calendar" prompt showing the event title, time and location. The user taps to confirm. The event is not added automatically; the user must approve the import.
09Does a calendar event QR code expire?+
No. The VEVENT data is encoded directly in the QR pattern with no expiry date and no server dependency. The code will continue to prompt a calendar import indefinitely. Once the event date has passed the code still works but will add a past event to the calendar.
10Can one QR code add an event to multiple calendar apps?+
Yes. The iCalendar VEVENT format (RFC 5545) is a cross-platform standard. The same QR code can be scanned by iOS (Apple Calendar), Android (Google Calendar), Outlook, and most other modern calendar applications. Each app interprets the DTSTART, DTEND and SUMMARY fields natively.