WiFi QR codes for offices and studios

A café has one network for guests. An office does not: staff need the printer and the file server, visitors need internet and nothing else. That means at least two SSIDs, two sets of codes and different places to put them. Here it is as two codes, three placements and one rotation table.

1. Segment the network before designing the card

The QR code is just an entry point; the real structure is segmentation. Two SSIDs on one router is enough — no second box needed:

NetworkWhoSettings
Staff (e.g. OFFICE_STAFF)Laptops, phones, printer, NASCan reach internal devices, can cast, sees shared drives
Guest (e.g. OFFICE_GUEST)Clients, interviewees, hot desksClient isolation, no LAN access, its own bandwidth cap and device limit

If you also have meeting-room displays or IoT gear (cameras, smart lights), give them a third network of their own rather than mixing them into the guest SSID.

2. Three placements, and the two codes must not swap

PlacementWhich codeNotes
Reception / waiting areaGuest onlyAnything visitor-visible carries guest only; 2 in (5 cm) code with "Guest WiFi — scan to join"
Meeting-room tent cardMostly guestWhere "what's the WiFi?" gets asked; 1.2 in (3 cm) code, printed on both sides so it reads from either end of the table
Back of desk card / by the printerStaffFacing inward or downward so visitors do not photograph it; 1.2 in (3 cm) is plenty

The classic mistake is pinning the staff code in the meeting room or at reception. Within two weeks a visitor has photographed it and the password is effectively public. The test is simple: will this card ever be seen by someone not on payroll?

3. Size: offices need less than venues

Office scanning distances are short — 12–20 in (30–50 cm) from hand to desk card, maybe 24–32 in (60–80 cm) across a meeting table — so 1.2 in (3 cm) is enough. Only wall or glass-door codes need 2 in (5 cm). Same rule: edge ≈ distance ÷ 10, or use the size calculator.

Two office-specific traps: acrylic stands and glass decals at reception catch ceiling lights and kill the scan — go matte or move the card; and meeting-room cards get buried under laptops and cables, so a small stand beats a flat A4 sheet.

4. Password changes and departures: a table beats a clever password

TriggerGuestStaff
Someone leavesNo changeChange same day; revoke NAS, printer and shared-drive access
Leeching detectedChange now, check the client countAs needed — read router logs for the source first
Scheduled (quarterly)ChangeChange
New router or ISPKeep the same SSID and password and the cards still workSame — but new hardware usually ships with a different default SSID

When you do change it with many cards in the field, keep the stand and swap the insert: print only a business-card-sized patch each time and the cost drops to a tenth.

Three things the guest network should do anyway

  1. Rate limit: a bandwidth cap on the guest SSID stops one large upload from saturating the line.
  2. Time limit: some routers can expire guest access outside business hours.
  3. Device cap: 10–20 clients, which beats investigating "why is everything slow" later.

5. The payload itself: never hand-assemble it

A WiFi QR code is one line of text shaped like WIFI:T:WPA;S:SSID;P:password;;. Semicolons, quotes and backslashes in the password must be escaped, and a non-ASCII or space-containing SSID breaks the whole string if encoding is even slightly off. Generate it in the studio instead of typing it, then scan the result on both iOS and Android.

One reminder: the password is stored in plain text inside the code. Anyone who scans it — including with a generic scanner app that just shows the decoded string — has it. That makes it right for a network you are happy for anyone in the room to use, and wrong as an access-control mechanism.

6. Pre-launch checklist

Run through this before the cards go up

  • Reception and meeting rooms show guest codes only; staff codes face inward or downward.
  • Guest SSID has client isolation on, with no route to printer, NAS or cameras.
  • Both codes scanned on iOS and Android, doing it while disconnected from the network.
  • Code edges ≥ 1.2 in (3 cm) on desk cards, ≥ 2 in (5 cm) on reception wall cards, quiet zone intact.
  • The rotation table says who changes which code and when — not just in one person's head.

Generate the staff code and the guest code in one sitting

Change SSID and password, export straight to 300 dpi PDF or SVG at tent-card, business-card or A5 size.

Open the WiFi QR code studio

Related reading

Frequently asked questions

Do we need a QR code for the staff network at all?
Yes, but only in internal spots: the back of a desk card, a meeting-room tent card, next to the printer. It saves answering the same question for every new hire, replacement phone or borrowed laptop — just never put it where a visitor can photograph it.
Do two networks mean two routers?
No. Most routers run a primary network and a guest network on the same box; the guest SSID already isolates clients from your LAN and can be rate-limited and capped per device. Sharing one SSID and password with everyone is what actually forces extra hardware.
Should the password change when someone leaves?
The guest password rotates on a schedule, not per person leaving — quarterly is a sane default. The staff network is different: change it the same day and revoke that person's access to the NAS, printer and shared drives.
What guest settings actually matter?
Client isolation, so guest devices cannot see each other, and no route from the guest SSID to printers, NAS or cameras. Both are checkboxes in the router and matter far more than anything printed on the card.

Templates that fit this setup

Three layouts picked for this scenario — swap the venue name and password, then export.