Static QR code

The generator turns the content into modules once. When someone scans the code, the phone decodes that content and acts on it directly: it opens the web address, offers to join the network or offers to save the contact. No server is involved in reading the code. If the content is a link, the only server contacted is the destination’s, and it sees an ordinary visit rather than a scan.

Because the content is the pattern, changing a single character produces a different code. There is no way to edit a static code after printing; the only fix is a new code. The one workaround applies to links: if a static code points to an address on a website you control, you can redirect that address on your own server.

Static codes have real strengths:

• No expiry. The code decodes the same way for as long as the print is readable. A static link stops working only if the page or domain it points to goes away.
• No dependency. No account, subscription or third-party service is needed.
• Offline content. WiFi logins, contact cards, plain text and calendar events work with no internet connection, and phones act on them natively.

The costs are the reverse: no editing, no scan counts and, for long content, a dense code. You can still measure visits from a static link by adding UTM parameters and reading your own web analytics, but the tags are then fixed forever and make the code denser. Use a static code for content that will not change, and a dynamic code for anything printed that you may need to update or measure.

A café’s WiFi code holds WIFI:T:WPA;S:Cafe Guest;P:espresso-2026;;, 41 characters that fit a version 3 code (29 × 29 modules) at error correction level M. If the password changes, the café prints a new code.