Use QR from Event in Ali Hub Codes with clear validation, results, privacy information, and documented limitations.
Enter data to see a preview.
Turn a title, schedule, location, and description into a compact calendar payload. A compatible scanner can offer the event to a calendar application without asking people to retype every field. Use ISO timestamps with an explicit UTC offset, preferably Z, and review every calendar line before publishing the code. The result is static: changing the event later requires a new code.
The tool creates an iCalendar-style VCALENDAR block with VERSION, PRODID, VEVENT, SUMMARY, DTSTART, and DTEND lines. LOCATION and DESCRIPTION are included when supplied. Event fields are escaped for calendar text: backslashes, line breaks, semicolons, and commas are represented safely. The QR code contains readable data and does not encrypt or register the event.
1. Choose the exact event title, location, and description you want readers to see. 2. Enter Start ISO and End ISO as valid ISO timestamps with a timezone offset, such as 2026-06-28T10:00:00Z. 3. Generate the QR code, decode it, and compare SUMMARY, DTSTART, DTEND, LOCATION, and DESCRIPTION with the source values. 4. Open the decoded event in the intended calendar app and confirm its date, time zone, location, and description. 5. Print one sample at final size and scan it under normal lighting before distributing copies.
Team planning session How do I make a QR code for a team planning session? 1. Enter the event title and the start and end times as ISO timestamps ending in Z. 2. Add the location and a concise description, checking punctuation and line breaks. 3. Generate the code, decode the result, and compare each calendar line with the source fields. The code stores a static calendar handoff. A scanner or calendar application may interpret it differently, so test the decoded event on the devices your audience will use. Community workshop Can I share a workshop schedule as a calendar QR code? 1. Enter the event title and the start and end times as ISO timestamps ending in Z. 2. Add the location and a concise description, checking punctuation and line breaks. 3. Generate the code, decode the result, and compare each calendar line with the source fields. The code stores a static calendar handoff. A scanner or calendar application may interpret it differently, so test the decoded event on the devices your audience will use. Venue with punctuation How should I encode an event location containing commas and semicolons? 1. Enter the event title and the start and end times as ISO timestamps ending in Z. 2. Add the location and a concise description, checking punctuation and line breaks. 3. Generate the code, decode the result, and compare each calendar line with the source fields. The code stores a static calendar handoff. A scanner or calendar application may interpret it differently, so test the decoded event on the devices your audience will use. Online event Can an event QR code describe an online session? 1. Enter the event title and the start and end times as ISO timestamps ending in Z. 2. Add the location and a concise description, checking punctuation and line breaks. 3. Generate the code, decode the result, and compare each calendar line with the source fields. The code stores a static calendar handoff. A scanner or calendar application may interpret it differently, so test the decoded event on the devices your audience will use. Evening talk What should I include for an evening public talk? 1. Enter the event title and the start and end times as ISO timestamps ending in Z. 2. Add the location and a concise description, checking punctuation and line breaks. 3. Generate the code, decode the result, and compare each calendar line with the source fields. The code stores a static calendar handoff. A scanner or calendar application may interpret it differently, so test the decoded event on the devices your audience will use. Multiline description Can the description contain a line break? 1. Enter the event title and the start and end times as ISO timestamps ending in Z. 2. Add the location and a concise description, checking punctuation and line breaks. 3. Generate the code, decode the result, and compare each calendar line with the source fields. The code stores a static calendar handoff. A scanner or calendar application may interpret it differently, so test the decoded event on the devices your audience will use.
Decode the payload and check that it starts and ends with the expected VCALENDAR markers. Compare every event field, including converted UTC times and escaped punctuation. A successful scan only confirms that text was read. Review the proposed calendar entry before saving it, especially when the code came from a public poster.
Using a local time without an offset can shift the appointment when another device interprets it in a different time zone. Reversing the start and end times creates an invalid or confusing event. Check the order before generating. A comma, semicolon, backslash, or line break in a description must be escaped in the payload. Decode a sample and confirm the result. Printing an old code after the schedule changes leaves readers with stale details. Generate and replace the code when the event changes.
The tool prepares a static iCalendar-style payload. It does not send invitations, synchronise calendars, validate the venue, detect conflicts, or guarantee support in every calendar app. Anyone who can scan a public event code can read its title, schedule, location, and description. Do not include private attendee data, access tokens, or confidential instructions.
What format should Start ISO and End ISO use? Use valid ISO 8601 timestamps with a timezone offset, preferably a UTC value ending in Z, such as 2026-06-28T10:00:00Z. Does scanning add the event automatically? No. A compatible scanner may offer the decoded event to a calendar app, but the reader should review and approve it. Behavior varies by device and application. What does the QR payload contain? It contains a VCALENDAR block with a VEVENT, title, start and end times, and optional location and description fields. Can I include commas or semicolons? Yes. The generator escapes those characters for calendar text. Decode a sample and check that the displayed event still says what you intended. Can the description have multiple lines? Yes. Line breaks are escaped in the payload. Test the decoded event because calendar applications can display multiline descriptions differently. Will the code update when the event changes? No. The code is a static snapshot. Create and distribute a replacement when the title, time, location, or description changes. Can I use a private meeting location? You can, but anyone who scans the code may read it. Share the code only with the intended audience and remove sensitive details from public versions. Does the tool send invitations or reserve a venue? No. It only creates the QR payload locally. Invitations, calendar syncing, room reservations, and venue checks require separate services or manual steps.
Event fields Title, start, end, location, and description are collected as the event record. Calendar payload The generator builds a VCALENDAR and VEVENT block, converts valid dates to compact UTC timestamps, and escapes special text characters. QR handoff The calendar text is encoded into the QR image. A compatible scanner may offer it to a calendar application for review and import. Use a timezone-aware ISO value. A timestamp without an offset can be rejected by the form or interpreted inconsistently by different calendar apps. The payload is a snapshot. It does not send invitations, reserve a room, sync updates, or prove that the venue exists.
https://www.rfc-editor.org/rfc/rfc5545 https://www.qrcode.com/en/about/ https://www.qrcode.com/en/howto/code.html