Check every code in the artwork, before it goes to press

Add the PDF you are sending to the printer. We find every QR code inside it, decode each one, and measure it at the size it will actually be printed. You get a page number, a position, and a plain answer for each.

  • Finds every code, not just the first
  • Real millimetres, from the page itself
  • Nothing is uploaded
  • Free, no account

This sets the distance every size judgement is made against.

mm wide

Ignored for PDFs. A PDF states its own physical size, so those measurements are exact.

Drop the artwork here

PDF, PNG, JPEG or WebP. Multi-page PDFs are checked page by page.

Nothing is uploaded. The file is opened and measured inside this browser tab.

The two failures that survive to press

A code is approved on a screen at 400 percent zoom, where every code looks perfect. It is then placed into a layout, scaled to fit a column, and nobody decodes it again. By the time anyone tries, the run is boxed.

It ended up too small
A code needs roughly a tenth of its reading distance in width, adjusted for how much content it carries. A menu code at 12 mm is fine in the hand and hopeless on a wall. This measures the printed width and says which one you have.
Something crept into the margin
Four modules of clear space on every side is part of the specification, not a design preference: decoders use that band to find the symbol's edges. A rule, a caption or a background shape inside it is the most common printed failure there is.

Every finding is scored the same way, and the working is shown. Read how the ScanScore is calculated.

Common questions

Does my artwork get uploaded?
No. The file is opened and measured inside your browser tab and never sent anywhere. That matters for packaging and campaign work under embargo, and it is also why there is no size limit beyond what your own machine can hold.
How can it know the printed size from a file?
A PDF describes its pages in points, and a point is exactly one seventy-second of an inch. So a code measured in a rendered PDF page converts to millimetres exactly, with nothing assumed. Images carry no physical size at all, so for a PNG or JPEG you say how wide it prints and the same measurement follows from that.
What does it actually check?
That every code decodes, where each one points, the printed width of each in millimetres against the distance it will be read from, the width of one module, the blank margin on the tightest side, and the contrast between dark and light. Each code gets a ScanScore with the full working shown.
Why does it flag a code that looks fine?
Almost always size or margin. A code that is perfectly legible on a monitor at 400 percent zoom can be 11 mm on the printed page, which fails from across a room. The other common one is a layout element that has crept inside the four modules of clear space the code needs on every side.
Can it handle a multi-page document?
Yes. Every page is checked and every finding is reported with its page number and its position on the page, so a catalogue with one bad code on page 27 is a thirty second job rather than an afternoon.
Does it check whether the destinations still work?
The checks on this page are about the printed code itself, and they run without a network connection. Watching a destination over time is a different job: tracked codes on a paid plan are checked daily, and you are emailed the day a destination breaks.