Round QR codes — what actually makes them work
Round QR codes look great on packaging and posters but only scan reliably when the underlying code is built right. Here's what changes and what doesn't.
A round QR code looks softer, friendlier, more brand-aware. It's also the QR code most likely to silently fail at the till, on the bus stop, on the back of someone's coffee cup. The shape isn't the problem. What's underneath is.
This is the post we wished existed when we first started shipping round QR codes on Linked.Codes. We rebuilt the renderer three times before the round dots stopped breaking on uneven lighting. Here's everything we learned about why round QR codes work, when they don't, and the small set of decisions that separate a code that always scans from one that mostly does.
A QR code is a grid first, a graphic second
Every QR code, round or square, encodes data in a 2D grid of black and white modules. The decoder doesn't see "round dots" or "square pixels" — it samples the centre of each grid cell and asks "darker than the threshold or lighter than the threshold?" That's it. The shape of the cell is purely cosmetic.
Which means a round QR code is a square QR code with rounded modules. The data, the error correction, the finder patterns in the corners — all identical. The only thing that changes is how each module is drawn.
That sounds reassuring until you start replacing 21×21 = 441 squares with 441 circles. A circle inscribed in a 1×1 square covers 78% of the area, not 100%. The decoder still finds the centre, but the boundary between adjacent dark cells gets weaker. Two black squares share a full edge; two black circles touch at a single point. Cameras with low contrast threshold start mis-reading the gap.
That's the whole problem in one diagram. Square covers 100%, round covers 78%. Take a picture of the round version in dim light and the boundaries blur where you need them sharpest.
Why round still works in practice
Despite the smaller dark area, well-built round QR codes scan as reliably as square ones in most settings. Three things make it work:
Error correction. QR codes carry built-in redundancy at four levels — L (7%), M (15%), Q (25%), H (30%). At Q or H, the decoder can lose up to a third of the modules and still recover the data. That's enough to absorb the contrast loss from rounded modules with margin to spare. Round QR code generators that ship at level L for "smaller code, better reads" are the ones that fail in the wild.
Sub-pixel sampling. Modern phone cameras don't decide "module is dark" from a single pixel. They average a small region and apply a contrast threshold. Round modules give the sampler a clean centre — the middle 60% of every cell is solid black or solid white, no anti-aliased pixel weirdness from a beveled square. In good light, that helps.
Finder patterns. The three big squares in the corners aren't decorative — they're how the decoder finds the code in the camera frame and corrects for rotation and skew. Most "round QR" generators leave the finder patterns square, or use a circle for the inner solid block while keeping the outer ring rectangular. As long as those patterns stay close to the original geometry, the decoder locks on instantly.
So the round QR works because the decoder is forgiving and the design choices that matter most happen at the corners, not in the data area.
The four ways round QR codes fail
We've tested somewhere north of 200 round QR codes from various generators and clients. The failures cluster into four categories.
1. Error correction set too low
The most common cause. A generator defaults to level L because "the code is smaller and prettier", and the smaller dark area combined with 7% redundancy can't survive a slightly worn print. Always render round QR codes at level Q (25%) or H (30%). The code is bigger but it scans every time.
2. Modules that nearly touch
A round dot inside a 10×10 module is a 9.5px circle in a 10px square. Adjacent dark cells get a 1px gap and a 1px gap reads as white in low-resolution cameras. The fix is to oversize the dot slightly — render circles at 105% of cell size and let them slightly overlap. Most decoders read it as one continuous dark region. Get this wrong by 5% and your code stops scanning at six feet.
3. Finder patterns rounded into uselessness
The three corner squares are why the decoder finds the code. They're three concentric squares — outer dark, middle white, inner dark. Replacing the outer ring with a fat circle, or rounding the inner square into a dot, can make the decoder miss them entirely. Keep the finder patterns square (best), or round the corners gently with a small radius (acceptable). Don't replace them with concentric circles.
4. Logo overlay too large
A round QR code with a centred logo looks like the future. It also might be too damaged to scan. The QR error correction handles a missing region up to its capacity — at level H, you can blank out 30% of the modules and still recover. Most generators give you a "logo size" slider. At 20%, you're safe. At 30%, you're at the edge. Past 30%, the code stops working in less-than-perfect conditions.
The interactive: how big can your logo go?
The headroom number is the part most posts skip. It's not "logo at 30% works at level H" — it's "logo at 30% with level H leaves zero spare error correction for print damage, low light, or a smudge." Stay under the cap by 5% if you want the code to age well.
Round QR codes vs custom shapes
Once you've got round modules working, the next temptation is custom shapes — diamonds, hearts, the brand mascot. We've shipped a few. The honest take: anything more complex than circles or rounded squares starts losing on contrast. The decoder needs a clear difference between dark and light cells; ornate shapes erode that difference faster than error correction can compensate.
If you want a code with personality, do this instead:
- Round modules at 105% size with finder patterns kept square.
- Brand-coloured dark modules — any colour as long as the contrast ratio against the background is at least 3:1. Dark navy, deep red, forest green all work. Mid-tone purples and oranges struggle.
- Subtle background tint — the "white" modules don't have to be white. Cream, very light grey, faded brand wash all scan fine and help the code feel less digital.
- Logo at 18-22% with level Q error correction. Sharp logo, clear cap of dark space behind it.
That's the recipe behind 90% of the QR codes you've seen on packaging that you didn't realise were branded. The constraint is real but the design space inside it is wide.
When square is still the right answer
Three cases where you should ship square modules:
- Tiny codes. Under 1cm printed. Round modules at small sizes start to merge unpredictably; square modules degrade more gracefully.
- Aged or damaged surfaces. Stamps on cardboard, weathered outdoor signage. Square gives you back the 22% module area you lose to round, which matters when the print itself is rough.
- Industrial scanners. Some legacy scanners (warehouse barcode readers, some POS systems) have stricter contrast thresholds than phone cameras. If you control the scanning environment and it's not a phone, square is safer.
For everything else — packaging, business cards, posters, beer mats, kombucha labels, the side of a startup van — round QR codes work. They just have to be built right.
Want a designer that bakes these defaults in? Round modules at 105%, level Q, logo cap at 25% with a warning past 20% — every QR you generate on Linked.Codes ships scannable.
Try it free →What we ship in the QR designer
The Linked.Codes QR designer renders round modules at 105% by default, keeps finder patterns square, and caps the logo overlay at 25% with a warning if you push beyond it. Error correction defaults to Q. None of those numbers are by accident — they're the boundaries we found through testing where the code stays reliable in the conditions QR codes actually meet (uneven light, slight skew, mid-range phone cameras, occasionally a damaged print).
If you're rolling your own round-QR generator, copy those defaults. They'll get you 95% of the way to a code that scans every time without needing to know any of this.
Do round QR codes scan worse than square ones?
Marginally, in poor conditions. In normal use — daylight, average phone, intact print — both scan instantly. The 22% module-area loss is well within what error correction handles at level Q or H.
What error correction level should I use?
Level Q (25%) for almost every round QR code. Bump to H (30%) if you're adding a logo overlay or printing on a surface that might wear (cardboard, fabric). Avoid L — it doesn't leave enough room for round-module contrast loss plus real-world wear.
How big can my centre logo be?
Stay under 25% of the code's total area at level Q, or under 30% at level H. Use the calculator above to see headroom. Past those numbers the code may scan in lab conditions but fail on real packaging.
Can I use my brand colour for the dark modules?
Yes, as long as the contrast ratio against the background is at least 3:1 — measure with any free contrast checker. Navy, deep red, forest green all clear that bar. Mid-tone purples and oranges usually don't.
Should I round the finder patterns too?
No. The three corner patterns are how the decoder locks onto the code. Rounding their corners gently is fine; replacing them with concentric circles is a common cause of "the code looks great but won't scan".
Are round QR codes worse for outdoor printing?
Slightly. UV fade and surface wear hit round modules a touch harder because there's less ink-to-cell margin. For long-lived outdoor print (signage, vehicle wraps), square at level H stays readable longer. For short-run posters, round is fine.
Do dynamic QR codes change the answer?
No — the visual rendering is independent of whether the code is static or dynamic. A dynamic round QR code uses the same module layout as a static round one. The difference is what's encoded (a short link you can repoint vs a fixed URL). See the post on static vs dynamic QR codes for that distinction.
Try it on your own domain
Branded short links and dynamic QR codes, on your subdomain or your own domain. One-time purchase, no per-click fees.
