Skip to main content
Processed in your browser · no upload

QR Code Scannability Tester — upload an image, see if it really scans

Added a logo, dark colors or fancy dots, or shrunk the code down small, and not sure it'll still scan from a distance or on a small print? Drop the image in and QR Cat tries to decode it under several conditions: original, grayscale, boosted contrast, scaled to 1/3, and extreme small size. You get a 'scannable / borderline / not scannable' verdict plus a contrast and quiet-zone read, so you know exactly what to fix. Everything is tested locally; the image is never uploaded.

QR Code Scannability Tester is a free online tool from QR Cat. Enter your content and get a scannable QR code (or decode one) instantly — everything runs locally in your browser, nothing uploaded or tracked. The codes are static: free forever, never expire, no watermark, no sign-up.

Tested locally in your browser — never uploaded

100% in-browser · nothing uploadedISO/IEC 18004 · scans with phone camerasZXing-verified · no sign-up · no watermark

2D migration

GS1 Sunrise 2027 rows near this tool

Source-backed migration rows connect static QR and barcode workflows to retail 2D readiness. The cluster is staged noindex until owner review.

How to use the qr code scannability tester?

  1. 1Drop the QR image in or click to upload (you can also paste a screenshot).
  2. 2QR Cat runs several local preprocessing passes and tries to decode each.
  3. 3Read the verdict — scannable / borderline / not scannable — and see which conditions passed or failed.
  4. 4Follow the advice: usually boost contrast, leave enough quiet zone, or print the code larger.

Why use QR Cat's QR Code Scannability Tester?

  • Catch broken codes early: many codes look fine but won't scan — find out before it's printed and on a wall.
  • Multi-condition matrix: not just the original — it simulates distance, small size and low contrast, closer to real scanning.
  • Actionable advice: it doesn't just say 'failed' — it points to low contrast, missing quiet zone or shrink-breakage and tells you how to fix it.
  • Image never uploaded: every test runs locally in your browser; your code never leaves your device.

Frequently asked questions

How is 'scannability' actually measured?

We use the ZXing decoder (the same family phone cameras rely on) and try several image conditions in turn: the original, grayscale, boosted contrast, scaled to 1/3 (distance / small print), and 80px (extreme small size). The more conditions it decodes under, the more robust the code and the more likely all phones will read it.

It says 'borderline' — should I worry?

Optimize it. 'Borderline' means the original decodes but it fails when shrunk or at low contrast — so at a distance or small print, some users won't scan it. Follow the advice to boost contrast and print it larger to push it to 'scannable'.

How are contrast and quiet zone judged?

Contrast looks at the difference between the brightest and darkest pixels (is there enough separation between modules and background?); quiet zone checks whether the four corners are plain and light (a standard QR needs a clear margin all around). Failing either tanks scan rate, and we flag each separately.

Why do some codes scan at full size but fail when shrunk?

Longer content means denser modules; once shrunk, adjacent modules blur together and the camera can't tell them apart. Fix it by shortening the encoded content (e.g. a short link) so modules are sparser, or simply print the code larger and closer to the scanner.

Is the image uploaded?

No. The uploaded QR image is processed only in your browser's local memory; all preprocessing and decoding happen on your device and are discarded when done — nothing uploaded or stored.

Updated · QR Cat team

Sources, review and limits

Last verified

2026-06-17

Author

GetQRCat editorial desk

Reviewer

QR standards review

Primary sources

  • QR-code encoding rules based on ISO/IEC 18004 concepts
  • Browser Canvas and SVG export APIs
  • User-entered URL, text, Wi-Fi or contact payloads

QR codes should be tested on target devices before print or distribution. We do not validate the safety, ownership or legality of the destination you encode.