Make a QR code that connects a phone to your Wi-Fi without anyone typing the password. The detail that matters: the payload format separates its fields with semicolons and colons, so a password containing either — and plenty do, because password policies encourage exactly those characters — breaks the code unless it is escaped. Most generators do not escape, and the failure is silent: the phone just says it could not connect. This escapes all five characters the specification requires, in the order that avoids double-escaping. Your password stays in the page; there is no reason for a credential to travel to a server to become a picture.
| Character | Why it matters |
|---|---|
| ; semicolon | Separates fields — truncates the payload |
| : colon | Separates key from value |
| , comma | Reserved by the format |
| " quote | Reserved by the format |
| \ backslash | The escape character itself |
Usually an unescaped character. The format uses semicolons and colons as separators, so a password containing one truncates the payload — the phone then tries to join a network named after the first half of your password. Nothing reports an error. This escapes all five characters the specification requires.
It contains your password in plain text — anyone who scans it, or photographs it, joins your network. That is fine for a guest network on a café wall and not fine for your main network in a public place. Use a guest network for anything printed.
Yes. iOS reads it from the Camera app since iOS 11 and Android since 10, both natively. Older Androids need a QR app that understands the Wi-Fi format.
Tick the hidden option, which adds the flag the phone needs. Without it the phone scans for a network it cannot see and gives up, even though the name and password are correct.
All three use the WPA setting here — the format does not distinguish them, and the phone negotiates whatever the router offers. Only pick WEP if your equipment genuinely has nothing else; it has been trivially crackable for twenty years.
Yes, and it is handled properly: the password field is omitted entirely rather than left empty, because an empty password field makes some Android versions prompt for one that does not exist.
No. The code is generated in the page, and you can confirm there are no network requests while it happens.
The payload is a short text format phone cameras recognise: `WIFI:T:WPA;S:network;P:password;;`, with the fields separated by semicolons and each key from its value by a colon. That separator choice is exactly why most generators produce codes that fail. A password containing a semicolon, a colon, a comma, a quote or a backslash — and plenty do, since those are precisely the characters a password policy encourages — terminates the field early, and the resulting code either joins nothing or tries to join a network whose name is the first half of your password. Nothing reports an error; the phone simply says it could not connect. The specification requires backslash-escaping of those five characters, and the order matters: the backslash must be replaced first, because escaping it afterwards would also escape the backslashes just added for the others and double them. Two further details are handled that generators commonly get wrong. An open network needs `T:nopass` with the password key omitted entirely rather than an empty `P:`, since some Android versions read the empty value as a password they should prompt for. And a hidden network needs `H:true`, without which a phone will scan for a network it cannot see and give up. The QR itself is rendered with the already-bundled `qrcode-generator` at error-correction level M, which tolerates about fifteen per cent damage — enough for a printed sign that gets scuffed, without the size penalty of level H for a payload nobody is printing on a curved surface. Everything happens in the page: a Wi-Fi password is a credential, and there is no reason for one to travel to a server to become a picture.