How to test a QR code before printing

Two ways a code fails, two kinds of test

Every QR failure is one of two things: the data is wrong (it scans fine and goes to the wrong place) or the rendering is wrong (the right data, unscannable). Testing means attacking both, in that order, a beautifully scannable typo is the more expensive failure.

Layer 1: prove the data

1. Decode the actual file you will print, not the preview, the exported file. Drop it on the validator, which renders and decodes it with a real decoder; the reasoning behind decode-verification is in why verify that your code decodes. (Every styled code downloaded from UseQR has already passed this loop, but re-check after any edit in another tool.)
2. Read the decoded payload character by character. http vs https, a trailing space, a smart quote pasted from a document, .co vs .com, decoders faithfully preserve your typo. The classic wrong-destination cases are in QR code opens the wrong link.
3. Follow the link on a phone, on mobile data, not office WiFi. You want the redirect chain, cookie walls and mobile rendering a real scanner will meet.

Layer 2: prove the physics

4. Print at final size on an office printer. Paper stock is wrong, but geometry is right, and geometry (module size, quiet zone) is what kills most printed codes. If it fails on a laser printer at final size, the print shop cannot save it; the causes live in scans on screen but not in print.
5. Scan from the real distance. A poster read at 2 m needs a 20 cm code (the 10:1 rule; check yours in the size calculator). Test at the distance, not at your desk.
6. Use the worst phone you can find. A three-generation-old Android mid-ranger is the honest canary; if it scans there, modern iPhones are a formality.
7. Worst light. Dim room, and angled under a bright light for glare. Codes destined for laminate or gloss stock especially.
8. Greyscale test. Print it on a mono laser: colour codes that rely on hue can vanish in black-and-white, and someone will photocopy your flyer eventually.

Layer 3: probe the margin

A code that barely scans clean has zero margin for the scuffs, folds and fading of real life. Cheap probe: cover a small patch of modules (never a corner finder square) with a fingertip or paper scrap and scan. At error correction Q or H it should still read; if a clean code is already temperamental, enlarge it, shorten the payload, or raise the EC level before printing.

The checklist

#	Check	Pass
1	File decodes in the validator	☐
2	Payload read character by character	☐
3	Destination opened on mobile data	☐
4	Printed at final size, office printer	☐
5	Scanned at real distance	☐
6	Scanned with an old phone	☐
7	Dim light + glare angle	☐
8	Mono/greyscale print	☐
9	Partial-cover margin probe	☐

This page is about proving the code; the production-side checks (bleed, colour space, resolution handoff) are the separate print checklist, and the conversation with your printer is proofing with a print shop.

FAQ

How do I test a QR code without printing it?

Decode the exported file with a validator and read the payload exactly, then print at final size on any office printer for the geometry test. Screen-only testing misses the two most common print failures: size and quiet zone.

Which phone should I test a QR code with?

The oldest, cheapest one you can borrow. Modern flagships decode marginal codes that mid-range and older phones reject, so a flagship-only test hides real-world failures.

What does covering part of the QR code prove?

It spends the error-correction budget deliberately. If a clean code cannot survive a fingertip over a few modules at level Q or H, it has no margin for the wear, folds and fading it will meet after printing.

Why does my code scan on screen but not when printed?

Usually module size below the printable floor, a cropped quiet zone, or an upscaled PNG with soft edges. Print at final size from vector artwork and re-test: the geometry, not the printer, is normally at fault.