How QRacade verifies a code still scans

The most expensive QR mistake is printing thousands of codes that don't work. We try to make that impossible.

The promise

QRacade checks every export with a real QR-reading decoder. Static designs are checked with their colours and logo; animated PNG and GIF exports check the base pattern without the moving character. If the relevant image cannot be decoded, the download is blocked and you get a warning.

What the check does

  1. Render the relevant image: the static design with colours and logo, or the base QR pattern for an animated export.
  2. Decode it with a QR reader and compare the result to the content you entered.
  3. Act on the result: if it reads correctly, the export proceeds; if not, we block the download and tell you what to adjust — usually colours or logo size.

This is why QRacade can promise "verified scannable" rather than just "looks nice". The check is not a claim in the copy; it runs on your design, in your browser.

How it handles animated codes

An animated code is a special case. A moving character will pass over part of the code in some frames, and a strict software decoder is far less forgiving than a real camera — it can reject a frame that a phone reads easily.

So for animation, we verify the code itself: the base image, without the character, at export resolution. That proves the pattern underneath is sound. The character is then drawn only along the code's free corridors, spending none of the recovery budget, which is what keeps the frames readable in practice.

The limits — and why we're honest about them

Always test a printed proof at the real size before a large run. Verification makes the digital design trustworthy; the proof test covers the physical world.

Related guides


See it for yourself

Watch the "Verified scannable" badge respond as you design in the generator or the logo tool.