There's no magic percentage, only a safer range to test from.
A center logo can make a QR code instantly recognizable — or quietly break it. The honest answer to "how big can it be" is that it depends on several things at once, not one universal number.
Quick answer: there is no single logo percentage that's guaranteed safe for every QR code. A logo covers part of the QR pattern, and how much it can safely cover depends on the error-correction level, the QR version and data density, the logo's shape, whether a background or padding is used, the print size, contrast, and even the specific scanner or device. The safest approach is to keep the logo conservative and test the final QR at its intended size — not to rely on a fixed number.
QR codes support four standard error-correction levels, each trading pattern density for the ability to reconstruct missing or damaged data:
These percentages describe error-correction capability — how much of the encoded codewords can be mathematically reconstructed if part of the symbol is missing or unreadable. They are not a direct instruction that you can safely cover that same percentage of the visible QR area with a logo. Codeword restoration and visual area coverage are related but different things, and treating "H means 30% restoration" as "H means a logo can cover 30% of the code" is a common and risky assumption.
This trips people up constantly. A centered logo that's 25% of the QR code's width occupies far less than 25% of the QR code's total area — because area scales with the square of width, a 25%-wide logo covers roughly 6% of the total area, not a quarter of it. When you see a "safe percentage" quoted somewhere, it's worth checking whether it's describing a width, a diameter, or an actual area — the numbers look similar but mean very different amounts of covered pattern.
The three large squares in the top-left, top-right and bottom-left corners are the finder patterns — they're what a scanner uses to detect that a QR code is present at all and work out its orientation before it even starts reading data. A logo, no matter how it's placed, should stay well away from them. It isn't accurate to say "only the center contains unimportant data" — a center logo works because of where it sits and how error correction handles it, not because the modules there don't matter. Edge structures near the finder patterns deserve the same caution.
More conservative
Small, centered logo. Finder patterns untouched, plenty of pattern left visible.
Higher risk
Oversized logo overlaps into the finder patterns and covers most of the data area.
Centered placement is the conventional approach because it naturally keeps the logo away from all three finder patterns at once. But centered does not automatically mean safe — a centered logo can still cover too many data and error-correction modules if it's sized too large. A reasonable approach:
A simple light background or a small amount of padding around a logo can improve visual separation between the logo and the surrounding pattern, which can help a scanner's detection algorithm. But that background or padding also obscures additional QR modules of its own — it isn't "free" space. The logo image and its background or padding together should be treated as the total area being covered, not just the visible logo artwork. Adding a white box around a logo doesn't automatically make a larger logo safe; it can just move where the coverage happens.
Higher error-correction levels provide more restoration capability, but they generally also increase how much QR data or how many modules are needed to encode the same payload, since more of the symbol is dedicated to redundancy. Logo-based QR designs are commonly built with a stronger error-correction level for this reason, though the ideal setting can depend on the specific generator and the content being encoded.
Frame's actual behavior: the generator exposes four error-correction options (L, M, Q, H) for a plain code, defaulting to M. As soon as a logo is added, Frame automatically switches to the highest level, H, for that code's export — regardless of whatever level was previously selected. This isn't optional or something you need to set manually; it happens automatically whenever a logo is present.
Frame calls its logo customization "Smart Logo Fit." Based on the actual generator behavior, here's what it verifiably does:
What it does not do is mathematically guarantee that any logo you choose within its size range will scan reliably. Scanning reliability still depends on the factors covered throughout this guide — data density, contrast, print size and conditions — none of which Smart Logo Fit can fully control for. Treat it as a set of guardrails that make a reasonable logo size easier to achieve, not as a promise that the result is "guaranteed scan-safe." The only way to confirm a specific design works is to test it.
If a logo QR code that used to scan stops working, it's worth checking these one at a time rather than assuming the logo alone is at fault — see the QR code not working guide for the broader troubleshooting list.
Yes. More encoded data can require a higher QR version with more modules packed into the same square, which changes the physical module geometry the logo sits on top of. A logo setting that looks comfortable on a short URL won't necessarily behave the same way on a denser payload:
Don't assume one logo size and padding setting will behave identically across different QR content types — test each one, especially anything denser than a short link.
See the QR code size guide for how logo customization interacts with minimum print sizes.
These are separate requirements. Logo coverage is an internal issue — it's about how much of the pattern inside the code is obscured. The quiet zone is the clear margin around the outside of the code. A branded QR code can fail because of either one independently, or both at once, so fixing a logo-coverage problem doesn't automatically fix a cropped margin, and vice versa. See the QR code quiet zone guide for the margin side of this.
A safer workflow. Start with a smaller logo. Test it. Increase the size only if the test still scans reliably. Retest after every size or design change. Test the actual printed version before mass production. This is more defensible than any universal percentage, because it confirms the specific design in front of you actually works, rather than trusting a number that was never guaranteed to apply to your code.
There's no single percentage that's guaranteed safe for every QR code. Safe size depends on error-correction level, how much data is encoded, logo shape, whether padding is used, print size, contrast and the scanner being used. Keep the logo conservative and test the specific final design rather than relying on a fixed number.
H-level error correction can restore roughly 30% of the code's data, but that's a codeword-restoration figure, not a direct instruction that 30% of the visible QR area can safely be covered by a logo. Treating those numbers as interchangeable is a common mistake — the real answer depends on the specific design and needs testing.
QR codes include error-correction data that lets a scanner reconstruct part of the pattern even if some of it is missing or covered. A centered logo takes advantage of this, but the restoration capability isn't unlimited and doesn't mean any size logo will work.
Frame automatically switches to the highest error-correction level (H) whenever a logo is added, regardless of what's manually selected for a plain code, since a logo needs the most restoration headroom available.
No. The three large corner finder patterns are what a scanner uses to detect and orient the QR code at all. A logo — center or otherwise — should stay clear of them; covering a finder pattern is a common cause of a branded QR code failing to scan.
A light background or small padding area behind a logo can improve visual separation from the surrounding pattern, but it also covers additional QR modules. The logo and its background together count as the total covered area — adding a white box doesn't automatically make a larger logo safe.
Usually the logo (plus any background/padding) covers too many modules, overlaps a finder pattern, or the remaining pattern loses contrast. Denser payloads, small print sizes and low resolution can make the same logo behave differently on different codes.
It can. More encoded data generally produces a denser QR pattern with smaller individual modules, so a logo that works comfortably on a short URL code may need to be smaller — or the code sized up — on a fuller vCard or WiFi code.
Yes. A logo that looks fine on a large screen can behave differently once printed small, where print quality, ink spread and camera focus all reduce tolerance further. Test the actual printed piece at its intended size rather than judging from an on-screen preview alone.
Finish the QR content and logo design, download it at full resolution, run it through a QR code checker, then print one proof at the intended size and scan it with more than one phone before printing in volume.
No. Frame's logo tools — size and padding controls, automatic high error correction — are designed to help, but no generator can guarantee scanning in every real-world condition. Testing the finished design is still the only way to confirm it works.