Testing Before You Publish

A QR asset is not done when the PNG renders—it is done when target users can scan it in context.

Minimum checklist

1. Scan with two devices — iOS and Android if your audience is mixed
2. Scan at final size — print a proof or view the slide at 100% zoom
3. Scan under realistic light — dim rooms and glare matter
4. Confirm the payload — URL opens the correct environment; Wi-Fi joins the right SSID
5. Re-scan after edits — any change to text, colors, or size requires a new test

When scans fail

Work through this order:

1. Is the payload string correct (typo, wrong URL, broken Wi-Fi schema)?
2. Is contrast sufficient and margin preserved?
3. Is the print too small or blurry?
4. Is the string too long for the chosen error correction level?

Ops and support habits

• Version QR assets in docs like any other link ("QR v3 — 2026-05")
• Prefer stable URLs with redirects you control over reprinting
• For internal tools, note the encoded string in the runbook—not only the image file

Key takeaway

Treat QR publishing like shipping a link: preview locally, verify on device, then distribute. The generator is the first step, not the last.