QR rounded modules decides whether a QR code feels like part of your design or like an afterthought stuck onto it, and it also decides whether the code scans. This guide sets out the working rules for rounded modules, explains why each rule matters, and shows how to apply it on real materials. The rules are practical rather than theoretical: each one can be checked on a proof with your eyes and a phone, before you spend money on a print run. If you follow them, your code will look intentional and still read quickly in the place where it will actually be used.
The core rules for rounded modules
Rounded modules soften the square edges of a QR code so the symbol looks friendlier and more modern. The rounding is a style choice applied to the shape of each module, and it must be kept gentle enough that the scanner still sees each module as a distinct dark or light square.
Round the corners slightly, never so much that modules turn into isolated dots. The scanner reads the centre of each module, so a gentle radius keeps the centre solid while softening the outline. Heavy rounding shrinks the dark area and makes the code look speckled to the camera.
How rounded modules affects scanning
Keep the finder patterns strong and square-ish even when the data modules are rounded. The three corner squares are the landmarks the scanner searches for, and rounding them into circles makes them harder to recognise. Many safe designs round the data modules but leave the finder patterns crisp.
Test rounded designs at the smallest size you plan to use. Rounding that looks fine on a large poster can turn into blur at business-card size, because each module is tiny and the rounded corners eat a large share of it. Print the smallest version and scan it before approving the style.
Setting up rounded modules before you print
Keep the gap between modules clean. Rounding should not merge neighbouring modules or leave ragged bridges between them. If the design tool joins modules together or leaves uneven gaps, the pattern becomes noisy and decoding slows.
Start with the plainest version that meets the brief, then add branding step by step, testing after each addition. If a step makes scanning slower, that step is the one to simplify. This gradual approach keeps the design honest: you can see exactly which choice helped and which choice hurt. Keep a copy of the last version that scanned instantly, so you can always fall back to a known-good design if a later variation fails.
Putting this into practice
Pick one live design that uses rounded modules and run it through this guide today. Print a proof at the final size, check the rules against it, and fix the first problem you find. Then scan the corrected proof with two phones in the real light. Keep the passing proof as a reference, and use it as the starting point for the next design so you are not solving the same problems twice.
Common mistakes to avoid
Even when the main rules are followed, small slips still creep in. The most common ones are letting decoration drift into the quiet zone, choosing colors that look distinct but share a brightness, and approving a design from a screen preview instead of a printed proof. Another frequent slip is changing one part of a working design, such as the link or the paper, without retesting the whole thing. Treat every change as a reason to run a fresh proof, and treat any hesitation in a test scan as a signal to simplify rather than to hope the next phone will cope better.
Quick checklist
- Keep dark modules on a light, even background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Keep the finder patterns solid, undisturbed, and easy to find.
- Check the code at the real size, on the real material, in the real light.
- Confirm the call to action names the payoff and the typed alternative works.
- Recheck the code after any change to the link, design, size, or placement.
Related tools and guides
- Try the [QR SVG PNG PDF exporter](/qr-svg-png-pdf-exporter) to check your choices before you commit to a design.
- Use the [QR contrast checker](/qr-contrast-checker) to confirm the numbers and guardrails for this element.
- Check the [QR size calculator](/qr-size-calculator) for a practical way to verify the finished code.
- Check the [QR scanner](/qr-scanner) for a practical way to verify the finished code.
- Check the [QR safety checker](/qr-safety-checker) for a practical way to verify the finished code.
- Check the [printed QR tester](/printed-qr-tester) for a practical way to verify the finished code.
- Browse the [blog](/blog) for more guides on sizing, printing, and design for QR codes.
