Wi-Fi QR Code Generator — Scan to Join

Almost always the network name rather than the password. It is case-sensitive and it is encoded exactly as typed, so a trailing space you cannot see is enough to break it — this page warns when the name starts or ends with one. Check the hidden-network tick too: setting it on a network that does broadcast makes some Android builds refuse the join outright. Then check the passphrase length. WPA takes 8 to 63 characters or exactly 64 hex digits, and anything else is flagged here, because no access point will accept it however cleanly the code scans.

No, and nothing about a QR code ever is. It is a picture of a string, and the string here contains your passphrase in plain text — any scanner app will read it back out and show it to you. Anyone who photographs the square, screenshots this page, or picks the printed card up off the table has your Wi-Fi password. That is inherent to the format rather than something this page does badly. Nothing is uploaded to build it, so the only copies that exist are the ones you make; point it at a guest network wherever you can.

That is the bug this format invites. A semicolon ends a field and a colon ends a key, so a name like Cafe; Bar written straight into the payload hands the reader a network called Cafe and a stray field called Bar — and the code still scans, which is why it is so hard to debug. Backslash, semicolon, comma, colon and double quote are each escaped here before the payload is assembled, in one pass so an escape character does not get escaped a second time. The payload is printed on screen exactly as encoded, backslashes and all.

Because it is entirely hex digits. A reader is entitled to treat a bare run of hex in those fields as the byte-wise spelling of the value rather than as its text, so a network genuinely called ABCD would be looked for as the two bytes AB CD and matched against nothing on air. The quotes say these are characters. The same rule is applied to an all-numeric passphrase, where the failure is worse because nothing looks wrong — the join simply never authenticates. A handful of very old scanners do not understand the quotes and show them as part of the name.

For enterprise, no. An 802.1X network needs an identity, an EAP method and a phase-2 method, and this page writes only the T, S, P and H fields — it does not emit the E, I, A or PH2 fields some readers understand, and it never asks you for a certificate. For WPA3-Personal, pick WPA/WPA2: SAE uses the same passphrase, and phones join transition-mode networks from a T:WPA payload perfectly well. A WPA3-only network paired with a device that insists on the newer T:SAE spelling may still refuse, and neither that nor the DPP format is generated here.

No. Transmute processes everything locally in your browser using JavaScript and WebAssembly. Your files never leave your device — there is no server, no upload, no cloud processing.