How to Make a Rounded or Custom-Shape QR Code (2026)

Modern QR generators let you style several distinct parts of a code. Knowing what each part is helps you style confidently without breaking anything.

This is the main lever for a modern look, and it is generally safe in moderation.

The finder patterns (the "eyes"). The three large squares in the corners help scanners locate and orient the code. Most generators let you restyle these, the outer frame and the inner dot, into rounded or custom shapes. Styling the eyes has a bigger impact on recognizability than styling the dots, so this is where more caution is needed (more below).

The overall frame and background. You can add a frame, a call-to-action, colors, and a logo. These sit around or within the code rather than changing the core pattern shapes. For "scan me" frames specifically, see QR code frames and CTAs.

What you cannot change: The underlying arrangement of light and dark, the actual pattern, is fixed by the data. Styling changes how the modules look, not where they are. That is why strong contrast still matters no matter the style: scanners read light versus dark, so your styled modules must stay clearly dark on a clearly light background. See how to make a colored code that scans.

The art of a styled code is knowing how far each element can go before scannability suffers. Here are sensible limits.

Rounded dots: generally safe. Switching the data modules to rounded dots or a mild connected style is usually fine and is the single most effective change for a modern look. Scanners handle rounded modules well, as long as contrast stays strong and the rounding is not so extreme that adjacent modules blur together or nearly disappear. Moderate rounding: safe. Extreme, barely-there dots: risky.

Custom eye shapes: style with more care. Rounding the corner eyes is popular and usually works, but the eyes are critical for scanner orientation, so keep them recognizable as the distinct corner markers they are. Gentle rounding is fine; heavily distorted, tiny, or low-contrast eyes are a common cause of a stylish code failing to scan. When in doubt, keep the eyes closer to standard than the dots.

Contrast is non-negotiable, whatever the shape. No amount of styling overcomes weak contrast. Keep dark modules on a light background. A beautifully rounded code in two similar mid-tones will not scan. This is the rule that underlies all the others.

Do not over-combine. Styling, color, and a logo all draw from the same "readability budget." A rounded, colored code with a center logo is asking the scanner to cope with three departures from the plain standard at once. Each is fine alone; stacked aggressively, they can tip a code into unreliability. If you are doing several, be conservative with each and test harder. See how to add a logo without breaking it.

Use error correction as a safety margin. A higher error-correction level gives a styled code more tolerance. It is not a license to over-style, but it adds resilience. See error correction levels explained.

Here is a reliable process for creating a rounded or custom-shape code that looks modern and scans every time.

1. Start with a dynamic code. So you can fix the destination later without reprinting, and so styling is purely about appearance while function stays flexible. See dynamic vs static.

2. Apply a moderate rounded dot style. Choose rounded dots or a mild connected style for the data modules, this gives most of the modern look with minimal risk.

3. Gently round the eyes, if you like. Apply a subtle rounded style to the corner eyes, keeping them clearly recognizable as corner markers. Do not shrink or heavily distort them.

4. Keep strong contrast. Dark modules, light background. If adding color, keep the code genuinely dark against a genuinely light background.

5. Add a logo only if needed, and keep it small. If you want a center logo, keep it modest and centered, and lean on higher error correction. See how to add a logo without breaking it.

6. Preserve the quiet zone. Keep the clear margin around the code; do not let styling or frames crowd the pattern.

7. Export crisp. Download a vector (SVG) for print so the styled shapes stay sharp at any size. See SVG vs PNG.

Then test, which is the step that separates a stylish working code from a stylish broken one.

A styled code departs from the plain standard scanners handle most easily, so it deserves more testing than a basic code, not less. This is the step that protects you.

Test on multiple phones. Styling that scans instantly on a new flagship phone can struggle on an older or budget device. Scan your styled code on several phones, including an older one if you can. Real scanners vary, and your audience uses all of them.

Test in real conditions. Try it in normal and slightly dim light, at the distance and size it will actually be used, and on the real material if printing. A styled code that scans on your monitor up close may behave differently printed small on a glossy package. See why codes fail to scan and the size guide.

If it hesitates, dial the styling back. The fix for an unreliable styled code is almost always to reduce the styling: less extreme dots, more standard eyes, stronger contrast, smaller logo. Step back toward the standard until it scans instantly every time, then stop. A slightly less adventurous code that always works beats a bolder one that fails on some phones.

The balance to aim for: The goal is the maximum modern style that still scans instantly on every device in real conditions. That line is usually: moderately rounded dots, gently rounded recognizable eyes, strong contrast, and a small logo at most. Within those bounds you get a code that looks designed and works flawlessly, which is exactly the point.

The bottom line: You can absolutely have a rounded, modern, on-brand QR code. Just remember it is a functional pattern first: style it confidently within the limits, test it harder than a plain code, and never let the look compromise the scan.