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.

Payload—
Payload bytes—
SSID bytes / limit 32—
QR version / modules—
Recommended edge (distance / modules)—
At 300 dpi—
—

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

OutputBasisWhy it matters
Payload stringWIFI: format — T security, S SSID, P password, H hidden flagDiff it against a code generated elsewhere to prove the fields match
Payload bytesUTF-8 lengthPayload size sets the QR version, and the version sets module density
SSID bytes32-byte protocol limitOverflow gets truncated by the router while the code keeps the full name — a silent never-connects
Version / modulesMeasured encode; version = (modules − 17) / 4Module count decides print size. Version 2 is 33×33, version 10 is 57×57
Recommended edgedistance ÷ 10, and modules × 0.4 mm, whichever is largerThe 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:

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

  1. Read the warnings first: SSID over 32 bytes, password over 63 bytes (the WPA2 limit), and characters that need escaping are all flagged.
  2. Note the recommended edge, then set that size in the studio and export SVG or 300 dpi PNG.
  3. 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 studio

Related reading

Frequently asked questions

Does the validator compute the real QR version?
Yes. It runs the same QR engine the site's studio uses, encodes the payload in your browser and reads back the module count. Version = (modules − 17) / 4, so the number is measured rather than estimated.
Why are there two recommended sizes?
One from scanning distance (distance ÷ 10) and one from module count (each module at least 0.4 mm so a normal printer can resolve it). The usable size is the larger of the two, which is exactly why longer names and passwords force bigger codes.
What happens if the SSID contains CJK characters?
The payload is UTF-8, so each CJK character costs 3 bytes and the SSID limit is 32 bytes — a pure Chinese name over about ten characters gets truncated by the router. The page shows the byte count and warns you when it overflows.
Is anything sent to a server?
No. Validation, encoding and the arithmetic all happen in the browser. The page makes no requests and writes nothing to local storage.

Templates that fit this setup

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