Printing is the point of no return. Once 500 flyers or 2,000 labels are out of the press, a bad code means a reprint. A few minutes of testing first costs almost nothing. This guide shows what to check and in what order.

Why a screen test is not enough

A code on your monitor is bright, flat, and sharp. A code on paper is none of those things. Ink spreads. Paper absorbs. Light bounces. Phones tilt.

So a code can pass on screen and still fail in someone's hand. The fix is to test the thing the customer will actually hold.

Step 1: Check the destination first

Open the link the code points to on your phone. Do this before anything else.

  • Does the page load?
  • Does it load quickly on mobile data, not only Wi-Fi?
  • Is it the page you meant, with no typos in the address?

If the URL is wrong, the best print job in the world will send people to the wrong place. Static codes cannot be changed after printing, so this check matters most.

Step 2: Scan with two phones

Phone cameras differ. Scan your test print with at least two devices:

  • One iPhone and one Android phone
  • If you can, one older model

Use the built-in camera app, not a special scanner app. Most customers will do the same.

If one phone reads it instantly and the other hesitates, treat that as a warning. A code that works only on your own phone is not ready.

Step 3: Run a distance test

Scan distance depends on code size. A common rule of thumb is that the distance is about 10 times the code width. A code 1 inch wide should scan from around 10 inches. A code 3 inches wide should scan from around 30 inches.

Test at three distances:

  1. Close, about 6 inches
  2. The expected distance, such as arm's length for a flyer or across a table for a tent card
  3. A little farther than expected

If the code only works up close, make it bigger. For close-range print, about 0.8 inch (2 cm) is the usual minimum. Do not treat that as a goal. Bigger is safer.

Step 4: Test the lighting

Real places have bad light. Test the print where it will live, or as close as you can get.

  • Bright light: Glare off paper can wash out the pattern.
  • Dim light: Restaurants, bars, and event halls are often dark.
  • Direct overhead light: Hold the print under a ceiling light and tilt it.
  • Outdoor light: Sun can overpower a glossy sign.

Try different angles too. People rarely hold a phone square to the code.

Step 5: Watch out for glossy paper and lamination

Gloss reflects. A mirror-like finish can bounce a light source straight into the camera and hide part of the code.

If your piece will be glossy or laminated:

  • Print a sample on that exact finish
  • Tilt it under light and scan
  • Compare with a matte version if you can

Matte finishes are usually easier to scan. If you like the look of gloss, test it hard.

Also test after any coating, folding, or laminating step. Scanning the plain proof does not tell you how the finished piece behaves.

Step 6: Check contrast and the quiet zone

Look at the printed sample, not just the file.

  • Is the code dark on a light background?
  • Is there a clear blank border on all four sides? The standard calls for 4 modules.
  • Has ink spread filled in small gaps?
  • Do any folds, edges, or trim lines cross the code?

Low contrast is a common failure. Made to Scan warns you when the contrast ratio is under 4.5:1 or when the colors are inverted. Read those warnings before you download.

Step 7: Check the finished size

Measure the printed code with a ruler. Confirm it matches what you planned. Printers sometimes scale artwork to fit a template, and a code meant for 2 inches can come back at 1.4.

If you print at a small size, check that the export is large enough. Made to Scan warns when an export is under 512 px or when a module is under 4 px.

What decode-checked means

Made to Scan decodes every exported file before you can download it. It reads the actual PNG or SVG back and compares the result with the exact URL you typed. If the two do not match, the download is blocked.

That catches file problems, such as a logo that covers too much or a color pairing a decoder cannot read. If you use a transparent background, we also decode it as if it were drawn on white paper.

It is still not a substitute for a print test. A decoder reads a clean digital file. It does not know your paper stock, your ink, your lamination, or the lighting in your room. A file can be decode-checked before download and still scan poorly after a rough print run. The two checks do different jobs.

A short pre-print checklist

  • Destination loads fast and is correct
  • Two phones scan the printed proof
  • Works at close, expected, and slightly longer distances
  • Works in bright and dim light
  • Tested on the real finish, after lamination
  • Quiet zone and contrast confirmed on paper
  • Printed size measured with a ruler

If everything passes, approve the run. If one phone struggles, fix it now. A second proof is cheap. A second print run is not.

Make your code

Ready to test one? Create a free QR code in your browser, download it, and print a proof first.