QR Codes for Campaign Links vs Guest Wi‑Fi

A poster QR that should open a landing page is not the same as a QR that joins Wi‑Fi. Wrong payload, dead scan.

Campaign links

Build UTMs on /tool/utm-builder, create the code on /tool/qr-code-generator, download PNG, and test on two phone brands before you print. Strip tracking later with /tool/utm-stripper when you need a clean share URL.

Guest Wi‑Fi

Use /tool/wifi-qr-generator with SSID, password, and encryption. Print it near the router. Don’t bury a Wi‑Fi password inside a normal URL QR.

Privacy

Both generators run in the browser — useful for event and shop teams without a design SaaS seat.

Test the code before you print a stack

Scan with two phones, not the phone that created the image. iOS and Android cameras both need a quiet margin around the modules — a code cropped to the edge of a poster fails more often than a slightly smaller one with white space. Dark ink on a glossy menu can glare; matte paper is more forgiving. For a campaign link, open the URL and confirm the UTM parameters survived. A code that points at the homepage with no campaign tags will not tell you which poster worked. For Wi-Fi, join and forget the network, then scan again as a guest would. The password in the code must match the router exactly, including capitals. Do not put the Wi-Fi password in a normal link code, and do not put a tracking URL in a Wi-Fi code. They are different payloads. Regenerate when the SSID or the landing page changes instead of editing the PNG.