WiFi QR payload validator
Before print, the thing worth checking is not the design — it is whether the payload is right and how big it actually is. Enter the SSID and password to see the exact string, its byte length, escaping warnings, the real version and module count, and the resulting minimum print size.
Escaping follows the WIFI: spec — a backslash is inserted before \, ;, ,, : and ". Version and module count come from a real encode in the browser, not an estimate.
1. What each output means
| Output | Basis | Why it matters |
|---|---|---|
| Payload string | WIFI: format — T security, S SSID, P password, H hidden flag | Diff it against a code generated elsewhere to prove the fields match |
| Payload bytes | UTF-8 length | Payload size sets the QR version, and the version sets module density |
| SSID bytes | 32-byte protocol limit | Overflow gets truncated by the router while the code keeps the full name — a silent never-connects |
| Version / modules | Measured encode; version = (modules − 17) / 4 | Module count decides print size. Version 2 is 33×33, version 10 is 57×57 |
| Recommended edge | distance ÷ 10, and modules × 0.4 mm, whichever is larger | The second is the printer floor: smaller modules smear on paper |
2. Why module count equals print size
Total edge = module count × module edge. You cannot compress the module count — it is fixed by payload length. The only free variable is how large each module prints:
- Short payload (
S:SHOP01;P:abc12345): low version, few modules, 2 cm still scans. - Long payload (CJK SSID plus a 20-character password): higher version, more modules, so at 2 cm each module is 0.3 mm and a normal printer renders grey mush.
- So "the code is too small" is usually "the payload is too long", not a designer's mistake.
Two rules of thumb: no module below 0.4 mm (about 5 px at 300 dpi), and the scanning range is roughly 10× the code edge. The intersection of those two is your usable size window.
Three things this page does not do
- It does not judge password strength — that is the password generator.
- It does not check your router settings (guest isolation, rate limits). Those live in the admin page.
- It stores nothing. Reload and the inputs are gone; nothing is written to local storage.
3. Three steps after you get the numbers
- Read the warnings first: SSID over 32 bytes, password over 63 bytes (the WPA2 limit), and characters that need escaping are all flagged.
- Note the recommended edge, then set that size in the studio and export SVG or 300 dpi PNG.
- Test-scan the print yourself before ordering the batch — that single step prevents a full reprint.
Payload verified — export the artwork
Same payload, now with layout, logo and paper size, exported as a print-ready PDF.
Open the WiFi QR code studioRelated reading
Frequently asked questions
Does the validator compute the real QR version?
Why are there two recommended sizes?
What happens if the SSID contains CJK characters?
Is anything sent to a server?
Templates that fit this setup
Three layouts picked for this scenario — swap the venue name and password, then export.