How to verify a QR code before printing
Five hundred flyers are cheap to print and expensive to reprint. This routine takes five minutes and catches every failure mode we document across this site — before the press runs.
Check 1 — Read what it really encodes
Scan the code and look at the URL your phone displays before opening it. Two things must be true: it is the correct destination (typos in URLs survive printing forever), and it is a direct address, not an intermediary. If you see a domain that is not yours — a shortener, a QR platform's short URL — the code depends on that server staying alive and paid for. That is the expiry mechanism in the flesh, and the moment to catch it is now: permanence is verifiable, not a label.
Check 2 — Open the destination like a stranger
Paste the decoded URL into a private browsing window. Your normal browser hides problems behind your logins and cache; a customer's phone has neither. The page must load over HTTPS without warnings, fast, and on mobile. Redirect chains and certificate issues show up here — while they are still free to fix.
Check 3 — Scan with more than one phone
A recent iPhone, a recent Android, and if possible an older device. Vary the light and the angle. If any of them hesitates on screen, the print will be worse — work through the three failure layers before continuing. Codes with logos deserve extra attention here: confirm the error-correction level is at maximum.
Check 4 — Confirm the size for the real distance
Measure where the code will actually live and apply the rule: printed width ≈ scanning distance ÷ 10 — the full per-support table is here. While you are at it, verify the layout kept the quiet zone (the white margin is part of the code) and that the contrast survived the design pass.
Check 5 — The one-copy proof
Print one copy at final size, on the final material, with the final finish. Scan it at the real distance, in the real light, at an angle. This single sheet is the only test that exercises ink, paper, glare and size together — the screen-to-print gap hides everywhere else. It passes? Print the run. It hesitates? The printing guide has the fix for whichever check failed.
The checklist, portable version
- Decoded URL = correct + direct (no third-party domain)
- Destination loads clean in private browsing, HTTPS, mobile
- Three phones, varied light, no hesitation
- Size ≥ distance ÷ 10, quiet zone intact, real contrast
- One printed proof at final size and material, scanned like a customer
Five minutes. It is the cheapest insurance in printing — and if a code fails a check, every fix is linked above.
Frequently asked questions
What is the most important check before printing a QR code?
Reading what it actually encodes: scan it and look at the URL before opening. It tells you the true destination and whether the code depends on a third-party server — the two failure modes that no print setting can fix.
How many phones should I test with?
At least two, ideally three including an older Android. A code that only scans on the newest iPhone in perfect light is a code that fails in the field.
Do I really need to print one copy first?
Yes. Screen validation cannot catch ink bleed, glare, contrast shifts on real paper, or size problems at real distance. One proof copy costs cents; five hundred bad flyers cost the reprint plus every lost scan.
Can I verify someone else's QR code, like one from an agency?
Absolutely — every check on this page works on any code from any source. If the decoded URL is not the client's own domain, raise the question before printing, not after.
Create a QR code that answers to no server.
Static, permanent, yours. €5 once — no subscription, no expiry, print-ready files.
Create my permanent QR