Guides
QR code won't scan: troubleshooting checklist

A qr code not working usually fails because the square is hard for a camera to read, not because every phone is broken. Blur, glare, a tiny print, a missing white margin, weak contrast, a logo that covers finders, or a torn sticker will stop most cameras. Work the list in order: prove the code on a second phone, fix lighting and distance, then inspect the file. Run a sharp photo or export through QR diagnose for contrast, quiet zone, and decode hints. If the payload is fine but the artwork is weak, rebuild a clean mark with the QR code generator and reprint. For logo-only failures, see QR codes with logo: contrast and scan reliability.
Why a QR code not working is usually the print
Cameras need three clear corner finders, a readable module grid, and enough contrast between dark and light. When any of those fail, the phone hunts and gives up. People call that “the QR is dead.” The file often still encodes a valid URL.
Print multiplies small design mistakes. Soft blacks from cheap toner, stretched non-square exports, and busy backgrounds all shrink the margin that worked on a bright monitor. A desk test on one phone is a draft check only.
Screens add their own traps. A QR shown on another phone under bright sun, or a projector image with moiré, can fail even when the PNG is clean. Treat the export and the real-world surface as two separate tests.
If every phone fails in every light, blame the artwork first. If one phone fails and another succeeds, still enlarge and darken the mark before you invent phone settings theories.
Quick field checks before you rewrite the file
Start with habits that cost nothing. Clean the camera lens. Hold steady at arm’s length, then move closer and farther until the square fills a comfortable fraction of the frame. Wait for focus. Try a second phone with a different camera app.
Turn the phone slightly if the sticker sits under a light. A small angle often kills specular glare without changing the ink. Shade the code with your hand when window light washes the surface.
Confirm you are scanning the right square when several codes share a poster. Guests often aim at the Wi‑Fi mark when they need the menu link. Label each code in plain text beside it.
If a second phone opens the link in normal room light, the payload is alive. Fix print size, contrast, or placement for the phones that still struggle. If both phones fail, stop tweaking brightness and open the source file.
Second phone and clean lens
Fingerprint smudge and cheap screen protectors blur fine modules. Wipe the lens and retry before you redesign. Borrow another device so you do not debug one camera forever.
Android and iPhone both read plain URL codes in the system camera on recent OS versions. Older devices may need a gallery or settings path. That is an OS quirk, not proof the code is invalid.
Distance, focus, and which square you aim at
Stand where your audience will stand. A 2 cm code on a table card can work. The same size on a wall across a lobby will not. Move until the finders look sharp, then hold still for a beat.
When two codes sit close, the camera may lock on the wrong one or see overlapping quiet zones. Separate the marks and add short captions so people aim correctly.
Blur and glare that stop a scan
Blur softens module edges so the decoder cannot sample the grid. Causes include out-of-focus photos used as the “master,” low-resolution PNG upscaled for a poster, motion during capture, and soft print from a worn printer drum.
Glare turns dark modules into gray highlights. Glossy laminate, window vinyl, and phone screens under overhead light are common. Matte stock and a slight tilt help more than cranking phone brightness.
Do not photograph a printed code through another glossy sheet and call that your archive master. Shoot square-on in even light, or better, keep the original PNG or SVG. If you must send a proof photo to a designer, strip location metadata first; see Remove EXIF GPS before sharing photos.
A blurry export will fail QR diagnose decode or look soft under the size tips. Fix the file at the source. Lighting tricks will not rescue a soft master across a print run.
Size, quiet zone, and contrast failures
Three geometric problems show up on almost every failed batch: the square is too small for the scan distance, the white margin is cropped, or dark and light modules sit too close in lightness. Fix these before you change the URL.
Print size scales with distance. Rough rule: keep the code at least about 2-3 cm across for arm’s-length scans, and larger for wall or window reading. Dense long URLs need more physical size because modules shrink.
The quiet zone is the light empty border around the symbol. Pack design loves to crop it. Without that margin, finders merge into nearby art and cameras lose the lock.
Contrast means dark modules on a light field. Black on white remains the safest pair. Pale gray on cream, brand orange on brand red, or white modules on a photo background fail often once print dulls the ink.
Print size and viewing distance
Measure where people stand, then size the code for that distance. A menu tent card and a parking-lot poster are different jobs. Stretching a small PNG to poster width creates blurry modules; regenerate larger from a vector or a high-resolution export.
Test a one-page proof at the real distance with two phones. If you need perfect framing and max zoom, enlarge the square.
Quiet zone and white border
Leave a clear light margin of at least four modules on every side. Do not place logos, rules, or colored panels against the edge of the symbol. Bleed and automatic crop in print shops often steal that margin; add extra pad in the layout file.
If a photo of the sticker shows ink or wood grain touching the modules, redesign. No camera setting restores a cropped quiet zone.
Contrast and colored modules
Pick module colors for the camera. Keep modules near black and the ground near white. Put brand color in captions or nearby art, not in the module field, unless you have already passed two-phone print tests.
Low contrast is a top hit in QR diagnose. Darken modules, lighten the background, and reprint. Screen “okay” contrast often fails after toner and laminate.
Damaged stickers, logos, and covered finders
Physical damage and branding both punch holes in the grid. Phones recover some damage through error correction. They do not forgive torn finders, sun-bleached black that turns gray, or a logo that eats half the symbol.
Stickers on bottles and tubes wrap around curves. The camera sees a warped grid. Flat labels on flat packaging scan more reliably. Replace wrinkled, scratched, or half-peeled marks instead of asking staff to “hold it just right.”
Logos belong in a small center island with intact corner finders and high contrast. Oversized badges, translucent marks, and covered finders are a separate failure class. Walk that path in QR codes with logo: scan reliability.
Faded outdoor posters lose contrast month by month. Schedule reprints when blacks look soft. Tape wrinkles and folded flyers create local blur that looks like random damage to the decoder.
Torn, faded, and wrinkled stickers
Replace any sticker with a missing corner finder or a crease through the center. Temporary tape over a torn code rarely restores a clean sample. Print a fresh label from the master file.
Sun and dishwasher steam fade ink. If the modules look gray on white, contrast is already gone for many cameras. Do not wait until every guest fails.
Logo overlays that block the grid
A small opaque center mark can survive. A large badge, a low-contrast watermark, or art that covers a finder will not. Generate a clean base first with the QR code generator, place a modest logo in design software, then retest.
If the unbranded code scans and the branded one fails, the logo is the bug. Shrink it, restore the quiet zone, and keep finders clear. Full logo rules live in the logo reliability guide.
Check the file with QR diagnose
When field checks fail, move to the file. Open QR diagnose in the browser. Use a sharp export or a well-lit, square-on photo of the printed mark. The check runs on your device for decode, contrast, quiet zone, and size tips.
Read the warnings in order. Failed decode means the pattern is too damaged or too soft. Contrast and quiet-zone warnings point to redesign before another print order. Size tips matter when the physical square is tiny relative to how you photographed it.
Diagnose is a lab pass, not a substitute for a live camera on paper. After you change the file, print a proof and scan again with two phones under the light your guests will use.
Toolsy’s diagnose tool is free and frontend. The image stays on your device for the check. That differs from upload-heavy converters; for general upload habits see Is it safe to upload documents online?.
Rebuild a clean code when the payload is fine
If diagnose opens the correct URL but print still fails, the payload is not the enemy. Export a fresh black-on-white PNG or SVG from the QR code generator, keep the quiet zone, and print larger with matte stock when you can.
Shorten long tracking URLs when density makes modules too fine at your print size. Static codes bake the destination into the pattern; change the link and you must regenerate. Editable destinations with scan counts belong on Pro Dynamic QR, which is a different product from a free static mark.
Guest Wi‑Fi sheets use a different payload. Build those on Wi‑Fi QR and still apply the same size, contrast, and glare rules from this checklist. For no-signup generator habits on plain URL codes, see Free QR generator without an account.
Do not “fix” a bad print in an image editor by cranking contrast on a blurry photo. Regenerate from vector or a clean generator export, then place that file in the layout.
Limits: phone settings vs bad artwork
Some failures are phone-side. Camera permission off, a third-party scanner that needs an update, or an older device that cannot read Wi‑Fi QR payloads will look like a dead code. Try the system camera on a second modern phone before you reprint a hundred signs.
A valid code that opens a dead website is a content problem. The scan worked; the destination did not. Fix hosting or the URL, then regenerate if the link string changed.
Curved surfaces, heavy frost on freezer doors, and extreme motion (moving vehicles) sit outside what a static flat mark can promise. Redesign placement rather than blaming the generator.
Dynamic marketing codes with redirects still need readable print. If the redirect works in a browser but the square will not scan, return to blur, glare, size, and quiet zone. Product differences between static and dynamic live in Dynamic QR vs static QR for marketing.
When you need a free on-device read of why the pattern fails, start at QR diagnose. When you need a new clean square, use the QR code generator. Logo-specific failures: QR codes with logo.
Frequently asked questions
Why is my qr code not working on every phone?
Shared failure across phones usually means the artwork is hard to read. Check blur, glare, print size, quiet zone, contrast, logos, and physical damage in that order. Run a sharp export through QR diagnose, then reprint from a clean generator file if warnings appear.
What does it mean when a qr code won't scan on one phone only?
Try a second device and clean both lenses. One weak camera, a dirty lens, or an outdated scanner app can fail while others succeed. Still enlarge and darken the mark if the successful phone needs perfect framing; that margin will help the weaker cameras too.
How do I fix blur and glare on a printed QR?
Use a sharp master file, matte stock when you can, and avoid photographing a glossy print as your archive. Tilt the phone slightly or shade the sticker to cut specular highlights. Soft or washed masters need a regenerate and reprint. Brighter room lights will not fix a soft master.
How large should a QR code be to scan reliably?
Size the square for the real viewing distance. Arm’s-length cards often need about 2-3 cm across or more; walls and windows need larger marks. Dense long URLs need more physical size at the same distance. Proof at the real stand-off with two phones before you order a batch.
What is a QR quiet zone and why does it matter?
The quiet zone is the light empty margin around the symbol. Cameras use it to find the edges of the grid. Cropping that border into colored art or photo backgrounds is a common reason a qr code won't scan after a “tight” layout pass.
Can a damaged sticker still scan?
Mild scuffs sometimes survive because of error correction. Torn finders, deep creases, and faded gray modules usually will not. Replace the sticker from the master file instead of patching with tape. Curved bottle wraps also warp the grid; prefer flat labels when scans matter.
Will a logo stop my QR from scanning?
A small centered logo can work when contrast stays high and finders stay clear. A large or translucent mark often kills the scan. Follow the size and contrast rules in QR codes with logo: contrast and scan reliability, then retest with QR diagnose.
Why won't my qr code scan on iPhone or Android?
Recent iPhones and many Android phones read URL codes in the system camera when the square is clear. Failures on one OS usually still trace to size, glare, or contrast. Update the OS, try the built-in camera, and retest a larger high-contrast print before you chase obscure settings.
Is QR diagnose free, and does it upload my image?
Yes, QR diagnose is free for this check. Processing runs in the browser on your device for the diagnose flow described on the tool page. Use a sharp export or photo, read the warnings, then confirm again with a live phone on paper.
Should I rebuild the code or only change lighting?
Change lighting and distance first when one phone almost works. Rebuild when diagnose fails decode, contrast, or quiet zone, or when every phone fails in good light. Generate a fresh black-on-white file with the QR code generator, keep the margin, print larger, and retire damaged stickers.
For logo branding limits, read QR codes with logo: contrast and scan reliability. For guest Wi‑Fi prints that still fail in the room, pair this checklist with Wi‑Fi QR code for guests.
Check why a QR fails
Upload or open a sharp photo of the code. Get on-device tips for contrast, quiet zone, size, and decode before you print another batch.


