12 common WiFi QR code mistakes

Not "it won't scan, what now" — but "what to check before it goes out". Ordered by how often they occur, each with a symptom, a cause and a fix. Two minutes before printing beats a reprint after the sign is up.

1. Four payload mistakes

#SymptomCause and fix
1"Incorrect password" and the password is right; , " \ inside the password weren't escaped. Let the generator escape them; don't hand-build the string.
2The SSID shows but joining failsA trailing space in the SSID was swallowed, or full-width characters crept in. Check the tail of the name.
3A hidden network never connectsMissing H:true. Hidden SSIDs must be declared explicitly in the payload.
4Old signs still in use after a password changeThe password lives inside the code; changing it invalidates every print. Replace them, don't hope a rescan helps.

2. Four design mistakes

#SymptomCause and fix
5Built as an inverted code (light on dark)Some models and older cameras refuse it. Keep dark modules on a light background — skip the "premium" inversion.
6With a logo, scanning becomes intermittentLogo covers more than ~20% and EC is still M. Use Q or H with a logo, and add a white outline around it.
7Code sits against a border or over artworkThe quiet zone is gone. Keep at least four modules of white on every side.
8Rounded corners, drop shadow or gradient on the codeModule edges get destroyed. Decorate the card, never the code.

3. Four print mistakes

#SymptomCause and fix
9Sharp on screen, muddy on paperA screenshot or a low-resolution image scaled up. Export 300 dpi PNG or SVG, sized in millimetres.
10Printed code slightly smaller than designed"Fit to page" scaling. Print at 100% / actual size and measure the diagonal.
11It's only 2 cm once it's on the wallThe size was chosen for looks, not for distance. Within 1 m you need at least 3 cm; at 2 m, 8 cm or more.
12Unreadable behind glass, acrylic or filmReflection and refraction. Don't put the code behind glass; use matte stock or tilt the sign.

4. The last three minutes

In this order

  1. Scan the finished piece on iOS and Android, from the real distance.
  2. Scan again with WiFi switched off — with a live connection, the OS quietly ignores the payload and you'll misread it as fine.
  3. Measure the code's diagonal; within 1 mm of the design value.
  4. Photograph it in place and look for glare or anything blocking it.

Design most of this away

Escaping handled, EC level Q by default, adjustable quiet zone, 300 dpi PNG / SVG / PDF export.

Open the WiFi QR studio

Related guides

Frequently asked questions

The code scans on my desktop monitor but not on a phone.
Usually size or contrast: the screen zoom flatters it, while the printed version is only 2 cm. Size the code from the real scanning distance and keep dark modules on a light background.
Why are the printed edges muddy?
The printer scaled to fit the page, or the export is below 300 dpi. Print at 100% / actual size and use SVG or a 300 dpi PNG.
Same code: Android scans it, iPhone doesn't.
Often an inverted code (light modules on a dark background) or film glare. iOS cameras handle inverted codes poorly — switch to standard dark-on-light.

Templates that fit this setup

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