Free Event QR Code Generator

The code encodes a calendar entry in the iCalendar format that phones and desktop calendar apps already understand — the same structure behind every .ics invitation you have ever been emailed. It carries a summary, a start, an optional end, a location and a description, and nothing else.

Scanning does not silently write to anyone’s calendar. The phone shows the event and asks, and the person taps to save it. That confirmation step is the reason these codes work well on public signage: people can see exactly what they are about to add before they add it.

Support is less uniform than for a website or contact code, and this is worth knowing before a print run. Many scanners hand a calendar code straight to the calendar app; some show the raw text instead, particularly on iPhones, where calendar codes have never had the consistent handling that contact cards and WiFi codes do.

A trackable event code removes that variance. The pattern encodes a short link, scanning opens a page showing the event with a single Add to Calendar button, and that behaves the same on every phone because it is an ordinary web page serving a standard calendar file.

Times are saved as local wall-clock time with no time zone attached. An event set for 7pm reads as 7pm in the calendar of whoever scans it, which is what you want for a physical event: the doors open at seven for everyone standing outside them, regardless of where the attendee’s phone thinks it is.

This is the opposite of what a purely online event wants. If you are promoting a webinar to an international audience, a floating 7pm will show as 7pm in every time zone and half your audience will arrive at the wrong moment. For those, it is usually better to put the time zone in the description explicitly, or point a URL code at a registration page that handles the conversion.

An end time is optional. Leaving it out produces an entry that most calendars treat as a point in time rather than a block, which suits a deadline or a save-the-date but reads poorly for anything with a duration. If people need to know how long to set aside, set the end.

Dates move, and this is where a trackable code earns its place. A postponed event on a static code means reprinting everything, because the date is baked into the pattern. On a trackable code you change the date in your dashboard and every poster already on a wall now points at the new one.

Keep the event name to something recognisable in a calendar list weeks later. "Summer Product Launch" survives that test; "Launch" does not, sitting among a dozen other entries in a busy week.

The location field is free text and is shown in the calendar entry, so write it as a person would need to read it — venue name and enough address for a maps app to find it. If the venue is hard to find, a location QR code alongside the event code is often more useful than a longer address string.

Use the description for the things people ask: doors versus start time, what to bring, parking, whether there is a bar. Every field you add makes the pattern denser on a static code, so on a poster read from a distance it is worth being brief; a trackable code has no such constraint, because the details live on a page rather than in the pattern.