Skip to content
QRMakery

AI QR Code Generator

AI makes the picture. Something still has to make it scan, and that is the part that goes wrong. Upload the artwork your model produced, and this draws a real QR code into it, then rasterises the result and reads it back with a decoder before it will let you download anything.

Straight answer first: QRMakery does not run a diffusion model. That needs a GPU and a server, and everything here happens in your browser with nothing uploaded. Bring the image, keep the model you already like, and use this for the half it gets wrong.

Start from a style

A shorter link means fewer modules, which leaves more room for the styling to survive.

Both images are read in this tab and embedded in the file you download. Neither is uploaded. PNG, JPEG, WebP or GIF up to 2 MB.

Reading the artwork back...

The PNG comes out of the same rasteriser that just verified the artwork, so what was tested is what gets saved.

Artistic AI background combined with a precise QR code and verified by a phone scan
AI QR code failure modes including scrambled modules, damaged corners, blur, weak contrast, and covered margins
Artwork faded behind a crisp QR code before scan verification and print export

What Actually Breaks in an AI QR Code

Five mechanisms, ordered by how often they are the real cause rather than by how obvious they look. The first two stop a code scanning at all. The third is the one that ruins print runs, because the image looks perfect right up until nobody can read it.

  1. 1The three corner squaresA model treats the finder patterns as texture and restyles them. A decoder looks for their 1:1:3:1:1 run of dark and light before it reads a single byte, so once they are painterly there is nothing to lock onto and the code does not scan at any size.What to do: Keep the corners solid and squared or gently rounded. The generator here draws them last, in a flat colour, so nothing can paint over them.
  2. 2The quiet zoneThe blank margin is the first thing an artist fills, because on a poster it looks like wasted space. The spec asks for four modules of it, and without it a scanner cannot tell where the symbol ends and the artwork begins.What to do: Leave the margin. Crop the artwork instead of the code, and never trim to the edge of the modules.
  3. 3Modules the model inventedControlNet steers a picture towards a pattern, it does not encode data. Cells drift dark or light to suit the image, error correction absorbs the first few, and somewhere past that the payload is gone. The code often still looks perfect.What to do: Decode it. This is the failure that no amount of staring at the image will reveal, and it is why the tool on this page reads the artwork back rather than trusting it.
  4. 4Contrast, locallyA bright patch of artwork under a dark module, or a gradient that lightens one corner, flips the local contrast so a camera reads a dark cell as light. Average contrast across the image can look fine while one region is unreadable.What to do: Fade the artwork under the code, raise the module opacity, and judge the lightest region rather than the overall look.
  5. 5Edges, once it is printedDiffusion output is soft. Anti-aliased module edges give a scanner grey where it needs a decision, and ink spread on paper thickens the dark and closes the gaps. A code that reads on a monitor can fail on the same design at 300dpi.What to do: Export vector where you can, print a test at the size shown under the preview, and scan it in the lighting the code will live in.

The Workflow That Survives a Printer

Generate the art wherever you like. Midjourney, Stable Diffusion with ControlNet, whichever tool you already pay for. Then bring the image here and let a renderer put the code in, because a renderer knows where every module belongs and a model is only guessing at the shape of one.

Upload, set the fade until the artwork reads without swallowing the modules, and watch the verdict under the preview. It goes green when a decoder has read your exact artwork back and matched it to your link. If it stays amber, the message says which control to move. Then print a test at the size the tool shows and scan it in the lighting the code will live in, because a monitor is a much easier surface than a menu under warm bulbs.

If you already have an AI code from somewhere else and just want to know whether it works, scan a QR code from an image decodes a file you paste in and tells you what came out.

Styled Is Not the Same as Generated

Worth separating, because they fail differently. A styled code is drawn by a renderer that knows the position of every module: shapes and colours change, data never moves. An AI code is an image nudged towards the shape of a code, so any cell can end up wrong and error correction quietly absorbs the damage until it cannot.

If what you actually want is the look rather than the model, the QR code art generator gets you shaped modules, styled corners and gradients with none of the risk, because nothing is inventing modules in the first place.

What This Page Cannot Do

  • No image generation, no prompts, no model. Bring your own artwork.
  • No repair of a finished AI code. If a model has already scrambled the modules, the data is gone and no tool can reconstruct it from the picture. Generate the code again, here, into the same artwork.
  • No hosting. Your image is read in the tab, embedded into the SVG you download, and never sent anywhere.
  • No frames or captions around the code. Export it and place it in your own layout.
  • Static codes only, so the destination cannot be changed after printing.

AI QR Code Questions

Does this site generate AI QR code art?

No. Generating the artwork needs a diffusion model on a GPU, which needs a server, and everything here runs in your browser with nothing uploaded. What this page does is the other half: bring the image your AI tool produced, and the generator draws a real, decode-tested QR code into it. If you want the model itself, use one of the AI art tools and come back with the image.

Why will my AI generated QR code not scan?

Almost always one of five things, and they are listed on this page with the mechanism for each. The two that account for most total failures are restyled corner squares, which stop a decoder locking on at all, and a missing quiet zone. The sneakiest is a model inventing modules: the picture looks perfect and the data underneath is gone. The only way to tell those apart is to decode the image, which is what the tool above does.

Can raising the error correction rescue an AI QR code?

Sometimes, and it is worth trying before you regenerate. High error correction rebuilds roughly a third of a damaged symbol, so it can absorb a model taking liberties with the data modules. It cannot rescue broken finder patterns or a cropped quiet zone, because those are how a decoder finds the code in the first place rather than data it can reconstruct.

How do I test an AI QR code before printing it?

Decode it with software rather than with your own phone, then also with your own phone. A phone camera is generous and forgiving in good light, so passing on your desk tells you less than you think. Paste your artwork into the reader on the scan page here and it tells you whether a decoder can read the image at all, and what it decoded to.

Is a styled code the same thing as an AI code?

No, and the difference matters when something breaks. A styled code is drawn by a renderer that knows where every module goes: it can change shapes and colours but it never moves data. An AI code is a picture guided towards the shape of a code, so any module can end up wrong. That is why a styled code either scans or has an obvious contrast problem, while an AI code can fail for reasons you cannot see.

Colour, a logo in the middle, artwork behind it, each one measured against what still scans.

All tools

Guides worth reading

All guides
  • Comparisons

    Static vs Dynamic QR Codes

    What the redirect actually buys you, measured on real encoded codes, and which payloads are worse off for it.

    16 min read