// Pre-Print QA

Will your QR code actually scan?

Paste a link (or upload a code), and get a Print-ready / Needs attention / High risk verdict — a simulated check against blur, low light, glare, low contrast, small sizing, compression, corner damage, and 7 other real-world conditions. Then download a one-page PDF report for your print shop.

14Conditions
PDFReport
100%In Your Browser
0Account Needed
Drop a QR code image, or click to browse
PNG, JPG, WebP or SVG ·

The image is read in your browser and never uploaded.

0 codes

Up to 100 codes per run. All rendering and checking happens in your browser.

Starting…
// How It Works

Enter → Check → Hand off the report

01

Enter the content or upload the code

A link, some text, or an image of an existing QR code. Pick the error-correction level you plan to print at.

02

Run the simulated check

The code is decoded, then put through 14 degradations — blur, glare, low light, low contrast, downscaling, JPEG compression, corner damage and more.

03

Read the verdict, download the PDF

A clear verdict with specific fixes, plus a one-page PDF report you can attach to a print order.

QuickQRC
Technical Brief · No. 0005
articles/qr-validator.html
// FAQ

Frequently Asked Questions

No. The check renders your code, decodes it, and simulates 14 common real-world conditions with a client-side decoder, all in your browser. It is a strong early-warning QA step, not a certification, and it cannot predict every phone, printer, or lighting situation.

No. Rendering the code, decoding it, running the simulation, and building the PDF report all happen locally in your browser. No link, image, or result is ever sent to a server.

This validator is built for a fast yes/no answer and a shareable PDF report, and it can check a batch of up to 100 links at once. The Scannability Tester is an interactive playground for a single code, where you tune each condition's severity and see the stressed image side by side.

Test at the level you will actually print at. M (15%) is the common default. Choose Q or H if the code will carry a center logo, be printed small, or land on a rough or curved surface, because the extra redundancy is what lets a scanner rebuild damaged modules.

Both are really the same problem: not enough pixels per module. Shorten the encoded link with a redirect, raise the printed size, or lower the amount of data, then re-check. The PDF report lists the specific fix for every condition that failed.

Yes, that is what the one-page PDF is for. It shows the verdict, the per-condition results, the tested content and error-correction level, and the recommended fixes, so a printer can see exactly what was checked.

Screens are backlit, high-contrast, and pixel-perfect; print is not. Ink spread, low paper contrast, small sizing, and glare each cost you modules that were fine on a monitor. The validator's Print and Reproduction tests simulate these effects so you catch them before the run.

There is no single rule, but a common guideline is at least 2 x 2 cm (0.8 in) for codes scanned up close, and about 2.5 cm (1 in) of width for every 3 m (10 ft) of scanning distance on signage. The validator's Downscaling test is a faster proxy: a code that still decodes at 150 px has room to shrink.