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
| # | Symptom | Cause 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. |
| 2 | The SSID shows but joining fails | A trailing space in the SSID was swallowed, or full-width characters crept in. Check the tail of the name. |
| 3 | A hidden network never connects | Missing H:true. Hidden SSIDs must be declared explicitly in the payload. |
| 4 | Old signs still in use after a password change | The password lives inside the code; changing it invalidates every print. Replace them, don't hope a rescan helps. |
2. Four design mistakes
| # | Symptom | Cause and fix |
|---|---|---|
| 5 | Built 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. |
| 6 | With a logo, scanning becomes intermittent | Logo covers more than ~20% and EC is still M. Use Q or H with a logo, and add a white outline around it. |
| 7 | Code sits against a border or over artwork | The quiet zone is gone. Keep at least four modules of white on every side. |
| 8 | Rounded corners, drop shadow or gradient on the code | Module edges get destroyed. Decorate the card, never the code. |
3. Four print mistakes
| # | Symptom | Cause and fix |
|---|---|---|
| 9 | Sharp on screen, muddy on paper | A screenshot or a low-resolution image scaled up. Export 300 dpi PNG or SVG, sized in millimetres. |
| 10 | Printed code slightly smaller than designed | "Fit to page" scaling. Print at 100% / actual size and measure the diagonal. |
| 11 | It's only 2 cm once it's on the wall | The size was chosen for looks, not for distance. Within 1 m you need at least 3 cm; at 2 m, 8 cm or more. |
| 12 | Unreadable behind glass, acrylic or film | Reflection and refraction. Don't put the code behind glass; use matte stock or tilt the sign. |
4. The last three minutes
In this order
- Scan the finished piece on iOS and Android, from the real distance.
- Scan again with WiFi switched off — with a live connection, the OS quietly ignores the payload and you'll misread it as fine.
- Measure the code's diagonal; within 1 mm of the design value.
- 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 studioRelated 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.