WiFi QR codes at events and trade shows
A café sign is about looking good and sitting in the right place. An event is a different problem: hundreds of devices arriving at once, a ten-minute scan spike at the door, and a network that may have to change mid-day.
1. Size the network first
The code only hands over the password; it cannot make a weak network strong. The usual failure at an event is not a code that won't scan — it's a code that scans and then nothing connects, or drops ten minutes later.
| Scale | Concurrent devices (est.) | Approach |
|---|---|---|
| Up to 50 people, small meetup | 30–60 | One commercial router with a guest SSID |
| 100–300 people, conference | 150–400 | 3–5 access points, one SSID, roaming on |
| Trade-show booth (your own corner) | 10–30 | Bring your own router with a separate SSID |
| Outdoor / market | Varies | 4G/5G CPE, and tell guests honestly that speed is limited |
Count devices, not people: one attendee with a phone and a laptop is two, and exhibitors bring tablets and hotspots.
2. Placement: spread the scanning
- Entrance — A3 portrait, scannable from 1.5 m, with a line like "join the WiFi before you queue."
- Check-in desk — two A5 table tents, one on each side, so nobody queues for a single code.
- Main hall door — A4, stating what the network is for (materials, not streaming).
- Lounge / coffee area — A5; this is where people actually sit down and connect.
- Inside booths — a business-card-sized card on a table stand, not a poster; guests connect after sitting.
Every sign should spell out the SSID. Events usually have the organiser's network, exhibitor networks and venue WiFi all at once; "scan to join WiFi" alone gets people on the wrong one.
3. Security and throttling, decided beforehand
Four baselines for an event network
- Use a dedicated guest VLAN, never the same segment as office or payment systems.
- Turn on client isolation so devices cannot see each other.
- Cap each device (1–3 Mbps is plenty for messaging and pages) and limit connections per device.
- Disable UPnP and port forwarding on the guest network so one compromised device cannot expose the LAN.
Fix the password before printing. Rotating it means the whole room reconnects, and old signs must come down immediately or half the room ends up on a password that no longer works.
4. Fallbacks: prepare three items
| Backup | When it's used |
|---|---|
| A second code for a backup SSID | Primary network saturates or hardware fails; swap the sign |
| A plain text card: SSID + password | Broken camera, or a locked-down corporate phone that blocks scanning |
| An electronic copy on your phone | Temporary extra point, or printing that never arrived |
Name the backup something unmistakable — "BrandGuest2", not "WiFi2" — and label the sign "use this if the main network is slow."
5. Closing down afterwards
- Disable the guest network or change the password, so a sign that walks out of the venue is useless.
- Collect or destroy the printed signs, especially any version naming internal systems.
- Save the SSID, password policy and placement map as a template for the next event — only the code needs regenerating.
Make the code first
Enter the SSID and password, export PNG, SVG or PDF; A4 and table-tent sizes switch in one click.
Open the WiFi QR studioRelated guides
Frequently asked questions
Is one router enough for an event venue?
Is one sign at the check-in desk enough?
Can I show the code on a phone screen if printing is late?
Will changing the password mid-event disconnect people?
Should event WiFi be throttled?
Templates that fit this setup
Three layouts picked for this scenario — swap the venue name and password, then export.