QR Code Not Working? How to Fix Common Issues

The number one design-time failure. Scanners need a clear difference between dark modules and the light background to detect the QR pattern. Pure black on white delivers 21:1 contrast — the maximum possible. Any deviation reduces reliability.

The 4.5:1 WCAG threshold. Color combinations below 4.5:1 contrast fail intermittently. Pastels (pale blue on cream, soft pink on white), trendy grays (charcoal on off-white when both are mid-gray), and color-on-color combinations all live in this risk zone. The QR may look fine in the design file at 100% zoom but fail under real-world print and lighting conditions.

The lighting multiplier. Restaurant lighting is dimmer than office lighting; outdoor lighting at dusk is dimmer than midday sun; older phones have less forgiving QR scanners than current flagships. A QR that scans cleanly in a brightly lit design studio fails 20–30% of the time in a dim restaurant on an older Android. Test under the actual deployment lighting before printing.

Background interference. A QR placed on a busy patterned background (textured stock, watermarked paper, photo backgrounds) fails because the scanner cannot separate the QR pattern from the surrounding noise. The QR needs a solid quiet-zone background to scan reliably.

The safe palette. Black on white. Dark navy, deep teal, forest green, burgundy, charcoal on white or cream. These pass 4.5:1 and read as branded without sacrificing reliability. See the QR color guide for the full tested palette and the no-watermark generators guide for vendors that allow free brand-color QRs.

If the printed code is too small for the scanning distance, the camera cannot resolve the individual modules and scanning fails.

The 10:1 rule. Code width should be roughly 1/10th the typical scanning distance. A 2 cm code works at 20 cm (business card distance). A 4 cm code works at 40 cm (menu reading distance). An 8 cm code works at 80 cm (poster distance). A 30 cm code works across a small room. Apply a 1.5–2× safety margin for older phones, dim lighting, and angled scans.

Practical minimums by use case:

• Business cards: 2 cm minimum. Below this, older iPhones in dim restaurant lighting fail.
• Menus and table tents: 2.5–4 cm. Restaurants tend to undersize the QR because the menu design is crowded.
• Yard signs and real-estate brochures: 5–8 cm. Sidewalk scan distance is 3–8 feet.
• Posters and signage: 8–15 cm depending on viewing distance.
• Window vinyl for retail storefronts: 8–15 cm. Passersby scan from 3–10 feet on the sidewalk.
• Trade-show booth signage: 15–30 cm for far visibility.
• Billboards and large-format display: 30+ cm; consult the print vendor for vehicle-distance specifications.

If the QR fails only at distance but works up close, size is the cause. See the QR code size guide for the full scaling table by deployment type.

Every QR code needs a quiet zone — a clear margin of solid light space around the entire code, at least 4 module widths wide on all sides. The quiet zone is part of the QR spec, not optional design padding. Without it, the scanner cannot detect where the code begins and ends.

Common quiet-zone failures:

• Designer crops the QR flush to the surrounding layout because it looks cleaner. The crop removes part or all of the quiet zone, and scan rates drop or fail entirely.
• Background graphic bleeds into the quiet zone. Brand patterns, decorative borders, or photo backgrounds extending into the quiet zone create visual noise that the scanner cannot separate from the QR pattern.
• Logo placement around the quiet zone. A company logo placed right at the edge of the QR encroaches on the quiet zone. Move it at least one full quiet-zone width away.
• Text or icons within the quiet zone. A "Scan me" label or arrow icon placed inside the quiet zone breaks the scan. The label belongs outside the quiet zone.

The fix: ensure the QR has at least 1 cm of solid background on all sides on a 4 cm code (proportional for other sizes). Test the printed proof on a phone — if you cannot scan it cleanly from 30 cm, the quiet zone is probably the issue.

If the QR scans cleanly but the phone opens a 404 page, an error page, or a completely wrong destination, the URL itself is the problem.

Common URL failure modes:

• CMS migration changed the URL. You moved your menu page from restaurant.com/menu to restaurant.com/dine/menu, and the static QR still encodes the old URL. The old URL 404s.
• The page was deleted. Marketing rotated the campaign landing page out without redirecting the old URL.
• The destination domain expired or was sold. Common with old marketing-campaign domains that the team didn't renew.
• The page exists but the content changed unexpectedly. A repurposed URL now serves something the QR users weren't expecting.
• SSL certificate expired on the destination. Modern phones block insecure pages by default; an expired cert means the destination won't load.

Static QR fix: generate a new QR with the corrected URL, then reprint any printed materials carrying the old QR. There's no way to edit a static QR after generation.

Dynamic QR fix: open the dashboard, edit the destination URL to point at the new page, save. Every printed QR redirects to the new URL on the next scan. No reprinting required. This is the killer feature of dynamic QRs.

Prevention: for any URL that might change in the next 12 months, use a dynamic QR. For static QRs, encode a URL on a domain you control with a stable redirect — your server can map yourdomain.com/r/abc to wherever the content lives, and you update the server-side mapping when needed. See the dynamic vs static guide for the architectural decision.

If a dynamic QR worked yesterday and stopped working today — and you haven't changed anything physically — the most likely cause is a vendor-side deactivation tied to the subscription status.

Vendors that deactivate dynamic codes after cancellation:

• Flowcode deactivates dynamic codes 30 days after subscription cancellation per their published ToS. Every printed Flowcode dynamic QR redirects to a Flowcode error page after the deactivation date.
• QR Code Generator (qr-code-generator.com) deactivates dynamic codes on cancellation per their published ToS.
• Some Bitly QR retention rules apply different policies to free, paid, and cancelled accounts.

Vendors that keep codes active after cancellation:

• EZQR keeps dynamic codes redirecting indefinitely after cancellation on every tier including free.
• QR Tiger keeps dynamic codes active per their published ToS.
• Uniqode keeps codes active per current ToS — verify in writing for high-value commitments.

Diagnosis steps:

1. Open the QR vendor dashboard. If the code is marked deactivated or expired, the vendor cancelled it.
2. Check the dashboard subscription status. If the subscription lapsed (failed payment, manual cancellation), that's the trigger.
3. Check the cancellation policy of the vendor. If the policy includes deactivation, the codes will stay dead until you resubscribe (where supported) or recreate.

Fix:

• Within the vendor's reactivation window: resubscribe immediately. Some vendors (including Flowcode within the 30-day window) reactivate codes on resubscription.
• After the window: the codes are dead. Recreate them on a vendor with cancellation survival (EZQR, QR Tiger), update future print artwork to use the new codes, and reprint any critical customer-facing materials. See the verify codes survive cancellation guide and the Flowcode migration guide.
• Prevention going forward: use vendors with published cancellation-survival policies, or use static QRs that have no vendor dependency at all.

Long URLs and large payloads create denser QR patterns with more modules. The denser the code, the larger it has to be printed for reliable scanning.

The version system. QR codes come in versions 1 through 40, with module counts from 21×21 (version 1) to 177×177 (version 40). Higher versions encode more data but require larger physical print sizes. A 22-character URL fits in version 1; a 100-character URL with tracking parameters needs version 6 or higher; a vCard with photo and full social URLs can push to version 20+.

Common density problems:

• Marketing URLs with full UTM parameters can be 200+ characters. Strip the QR-side URL down to a short identifier; let your server-side analytics handle the attribution.
• vCard QRs with too many fields. Adding bio text, photo data, and a full list of social URLs bloats the vCard and pushes the QR to a denser version. Stick to name, phone, email, company — and one additional field max.
• WiFi QRs with very long passwords (32+ characters) create denser patterns. Most don't hit this problem; complex enterprise passwords sometimes do.

The fix: shorten the encoded payload. For URLs, use a short URL service or a dynamic QR that encodes a short redirect URL on the vendor's server. For vCards, strip to essentials. For long passwords, consider a dynamic WiFi QR with a hosted landing page that displays the credentials.

Printed QRs degrade physically over time. Even a perfectly designed QR can stop working after months or years of real-world wear.

Lamination failure on table tents and shelf tags. Standard interior lamination delaminates at the edges first, exposing the print to spills, cleaning chemicals, and oils. Once the QR pattern is exposed, scan rates drop within weeks. Replace table tents every 12–18 months under normal restaurant wear; shelf tags every 6–12 months in high-traffic retail.

UV fading on outdoor signage. Standard interior-grade printing fades in direct sun within 4–6 months. Yellow and red inks fade first; black inks are more stable but still degrade. For window vinyl, yard signs, and any outdoor deployment, spec UV-resistant inks with exterior-grade lamination — the print lasts 2–5 years instead of months.

Glossy lamination glare. Glossy lamination creates specular reflection under overhead lighting at certain angles, intermittently breaking scans even on undamaged QRs. Matte lamination scans reliably under variable lighting.

Print resolution problems. QRs exported at 72 DPI (screen resolution) print with fuzzy module edges that scanners cannot parse cleanly. Always export at 300 DPI minimum for print, or use SVG (vector) format that scales to any size without quality loss. PNG at 300 DPI is sufficient for most print; SVG is the better choice when the print broker handles variable sizing.

Substrate problems. Uncoated paper absorbs ink and softens module edges. Glossy stock creates glare. The right default is coated 14-point cover stock with matte lamination for printed QRs that face wear.

Folds and creases on direct mail and packaging. A QR placed on a fold line breaks when the material is folded. Position QRs in flat areas with no anticipated fold or crease.

See the QR code best practices guide and the packaging labels guide for the print substrate and material decision in detail.

Sometimes the problem is on the scanning side rather than the QR.

Dirty camera lens. Pocket lint, fingerprints, and oil residue on the camera lens reduce scan accuracy. Clean the lens with a soft cloth.

Outdated OS. Native QR scanning shipped in iOS 11 (2017) and Android 8 (2017). Older devices need a third-party QR reader app. If your QR fails on an old phone but works on a current one, the OS may be the cause.

Camera setting disabled. Some Android skins ship with QR scanning disabled in the camera app settings by default. Open the camera app settings and verify QR scanning is enabled.

Low-light scanning. In very dim environments, the camera cannot resolve the QR pattern. Improve the lighting or move the QR to a better-lit position. Some phones include a flashlight toggle within the camera app for low-light QR scanning.

Camera too close or too far. Phones autofocus on the QR within a certain distance range. Too close and the focus blurs; too far and the modules can't resolve. The sweet spot is 10–40 cm for most phones on most QR sizes.

Aggressive QR readers. Third-party scanner apps sometimes redirect the user through their own redirect page (for monetization), which introduces a delay or a popup. Stick to the native camera app on iOS and Android for the cleanest scan experience.