Build a WiFi QR payload string for WPA, WEP, or open networks

This tool builds that standard payload from an SSID, password, and encryption choice. It handles WPA, WEP, and open networks, escapes characters that have special meaning in the format, and returns plain text ready for any QR encoder. The result is deterministic, easy to inspect, and available through the API for $0.002 per request.

Supply the network details that devices need

Start with the exact SSID shown by the wireless access point. Network names are case-sensitive, so capitalization, spaces, and punctuation must match what users see on their devices. Then provide the password and select WPA, WEP, or none as the encryption type. WPA is the appropriate choice for the common WPA, WPA2, and WPA3 personal network configurations represented by this broadly supported QR text convention. WEP is retained for older equipment, while none represents a network that does not request a password. The builder accepts encryption labels without regard to letter case, but it rejects any label outside those three choices so that a typo cannot silently create a misleading QR payload. For WPA and WEP, a non-empty password is required. For an open network, the password is ignored and no password field is emitted. This keeps the output focused on the credentials a scanner actually needs and prevents an unused password from being embedded accidentally.

Understand the payload and its escaping rules

The returned value begins with WIFI: and contains labeled fields separated by semicolons. The T field identifies authentication, the S field holds the SSID, and encrypted networks also receive a P field containing the password. A final pair of semicolons closes the payload. Open networks use the conventional authentication value nopass and omit P. Several ordinary characters have structural meaning in this text format: a backslash introduces an escape, a semicolon ends a field, and commas or colons may be interpreted as delimiters by compatible parsers. The builder prefixes each of those characters with a backslash when it appears inside an SSID or password. Escaping is especially important for names such as Office:Guest or passwords containing punctuation, because concatenating raw values by hand can produce a string that looks plausible while being split into the wrong fields by a scanner. The tool returns the payload as JSON text data; it does not render pixels or alter the credentials themselves.

Encode, test, and share the result safely

Pass the returned payload unchanged to a QR code library, printing service, label workflow, or design application that accepts arbitrary text. Choose an error-correction level and physical size appropriate for the setting, then test the finished symbol with more than one target device before distributing it. A valid payload does not guarantee that a phone can reach the access point, that the password is current, or that a particular operating system supports every legacy encryption mode. Treat the generated string as sensitive whenever it includes a password: avoid placing it in public logs, analytics events, source repositories, or support tickets, and retire printed codes when credentials change. This capability performs no network lookup and cannot verify the wireless network. Its job is narrower and predictable: validate the requested encryption family, escape format-sensitive text, and assemble a reusable payload. That separation is useful in automated systems because QR rendering can change independently while the credential serialization remains stable and straightforward to test.