Generate QR Codes That Scan Reliably

This guide maps to the tool directly so you can apply each step while reading.

Design your payload for reliable scanning #

The payload is the data encoded in the QR code — a URL, a text string, contact information, or Wi-Fi credentials. The longer the payload, the denser the QR code pattern becomes, and dense patterns are harder to scan in less-than-ideal lighting or at small print sizes. Keep payloads as short as reasonably possible.

For URLs, use the final destination link rather than a redirect chain. If your URL contains tracking parameters and UTM codes, every character adds density to the code. Consider using a URL shortener for QR codes in print materials — a link shortened to 20 characters produces a much less dense code than a 150-character URL with full UTM parameters, and it scans reliably at smaller sizes.

Avoid special characters, spaces, and punctuation beyond what is strictly necessary in text payloads. These characters require more bits to encode than standard alphanumeric characters, which increases code density. If encoding plain text for an informational sign or label, use concise, uppercase-only text where possible — uppercase alphanumeric characters use QR code space more efficiently than mixed case.

For Wi-Fi sharing QR codes, generate the code using the standard Wi-Fi QR format so phones can parse and apply credentials directly. The format is: WIFI:T:WPA;S:NetworkName;P:Password;; — correctly formatted, this creates a code that shows an 'Add to Wi-Fi Networks' prompt when scanned on both iOS and Android.

Size and contrast are the most common failure points #

Contrast is the single most important factor in scan reliability. Dark modules on a light background is the universal standard for a reason — maximum contrast lets cameras decode the pattern quickly across a range of lighting conditions. Avoid coloring the dark modules anything other than near-black, and avoid making the light modules anything other than near-white or transparent. Artistic color choices look appealing in design mockups and fail in real scanning environments.

Do not place logos, images, or decorative elements inside the QR code itself. QR codes have error correction built in, but the exact percentage of safe coverage depends on the error correction level you chose, and logos centered in QR codes regularly exceed safe limits. If you need a branded QR code, place the logo near the code, not inside it.

Print size determines scan distance. A QR code at 2 cm x 2 cm can only be reliably scanned from about 10 to 15 cm. A code at 5 cm x 5 cm can be scanned from 25 cm or more. For event posters, restaurant menus, and retail signage where the code will be scanned from arm's length, print at a minimum of 4 cm x 4 cm. For large format posters, scale proportionally larger.

For digital display — on screens, in presentations, in email signatures — export the QR code at high resolution (at least 500x500 pixels) and let the display system scale it down. Scaling down from a larger source preserves module sharpness. Scaling up from a smaller source produces blurry edges that hurt scan reliability. Always generate larger than you think you need.

Test on real devices before publishing or printing #

Always test your QR code before committing to a print run or published layout. Test with at least two different phones — ideally an iPhone and an Android device with a different default camera app. QR code readers are not identical across devices; a code that scans instantly on one may require multiple attempts on another if contrast or density is near the limit.

Test in the conditions where the code will actually be used. A code that scans under bright office lighting may fail under yellow artificial lighting in a restaurant, or in outdoor daylight with glare on a glossy surface. If your code will be used in a specific environment, test it there. If you cannot test on-site, test in poor indoor lighting as a rough proxy.

If you have placed the QR code inside a larger design — on a flyer or a poster — export the final design file and test that exported version, not the QR code in isolation. Resizing, resampling, and design tool export settings can all subtly reduce contrast or introduce compression artifacts that affect scan reliability.

For QR codes that link to dynamic content — like a restaurant menu that gets updated — verify that the underlying URL resolves correctly after any content updates. A QR code pointing to a page that has been moved or renamed gives the same bad experience as a code that cannot be scanned.

Operational use cases and context labels #

For menus, product sheets, and informational displays, pair every QR code with a short text label that tells users what they will see after scanning. A label that says 'Scan for today's menu' or 'Scan to book a table' removes the uncertainty that makes some users skip the code entirely. The label does not need to reveal the full URL — it just needs to set clear expectations.

For Wi-Fi sharing in homes, offices, and hospitality venues, QR codes eliminate the frustration of verbally communicating long passwords. Generate the code once, print it at a reasonable size, laminate it, and place it where guests can easily scan. Update the printed code if the password changes, and test the new code before replacing the laminated version.

For payment links and checkout flows, QR codes are valuable at events, markets, and physical retail where a direct link is more reliable than a typed URL. Keep payment links permanent — use a stable URL rather than one that changes per transaction — and test the full payment flow via QR scan before using it in a live context.

For internal operational use — linking a machine to its maintenance manual, a desk phone to its dialing guide, or a product to its configuration steps — QR codes make information instantly accessible without requiring any lookup. These internal codes can use slightly longer payloads since they will typically be scanned in good lighting at close range, but they still benefit from testing across the device types your team uses.