Encoding URLs, Wi-Fi, and Text

The QR symbol is generic; payload format determines what happens after a successful scan.

URLs

Best practices:

• Include the scheme: https:// (not example.com alone unless you intend a search)
• Avoid unnecessary query noise; encode special characters correctly first
• Test staging vs production URLs before printing thousands of labels

If a URL contains reserved characters, fix encoding with a URL tool before generating the QR payload—not after.

Plain text

Plain text QR codes copy or display a message. They do not magically open apps unless the scanner app chooses a action.

Good for:

• Short support codes
• Internal asset tags
• Offline instructions

Keep text short when you also need high error correction or small print.

Wi-Fi strings

Many platforms recognize the WIFI: schema:

WIFI:T:WPA;S:MyNetwork;P:secret-password;;

Fields:

• T — security type (WPA, WEP, nopass)
• S — SSID
• P — password

Special characters in SSID or password may need escaping per the spec. Always scan on a real phone on the target OS before publishing guest Wi-Fi posters.

Common mistakes

• Encoding a redirect URL that changes later
• Pasting HTML or markdown instead of the raw URL
• Wi-Fi password with unescaped ; or \ breaking the parser

Key takeaway

Encode the exact string you want the scanner to deliver. Validate URLs and Wi-Fi strings in a text editor, then generate the QR locally.