# QR Code with Logo: How to Add Branding Without Breaking Scans

> How to add a logo to a QR code without breaking scans. Covers error correction, sizing, placement, common failure modes, and a multi-device test plan.

Canonical: https://fast-qr.app/learn/qr-code-with-logo
Last updated: 2026-04-26

Author: [Rehan Haider](https://fast-qr.app/author/rehan-haider)
Published: 2026-04-26
Tags: qr, logo, branding, design, error correction

A QR code with a logo is a standard QR code that has a small graphic embedded near its center, made readable by the QR specification's built-in error correction. The question behind almost every "QR code with logo" search is the same: how much branding can I put on this thing before it stops working. Adding a wordmark or icon to a QR code is the single most-requested customization, and it succeeds far more often than people expect. It also fails in predictable ways when designers push too far, place the logo wrong, or skip a real-world test pass.

This guide walks through what makes a logo'd QR code reliable, how big the logo can be, where to put it, what artwork holds up, and the failure modes that turn a beautiful proof into a useless print run. Everything here assumes you want a QR code that scans on a five-year-old budget Android in dim restaurant lighting, not just on your designer's iPhone.

## How error correction makes logos possible

A QR code is not a brittle pixel grid. It is a self-healing data structure built on top of Reed-Solomon error correction, the same coding family that protects data on CDs, DVDs, and deep-space transmissions. Each QR generator weaves redundancy bytes into the modules so that scanners can rebuild the payload even when chunks of the pattern are missing or covered.

That redundancy is what lets a logo sit on top of data modules at all. The logo is functionally a smudge from the scanner's perspective: data is missing from that region, and the decoder reconstructs it from parity bytes elsewhere in the code. The QR specification defines four error correction levels, with the highest one tolerating roughly 30% of codewords being lost. Denso Wave, the inventor of the QR code, summarizes this on its [error correction overview](https://www.qrcode.com/en/about/error_correction.html). The math behind it is the Reed-Solomon code, covered in detail on the [Wikipedia QR code page](https://en.wikipedia.org/wiki/QR_code#Error_correction).

For a centered logo to work, error correction has to be set to H. Levels L, M, and Q simply do not have enough redundancy once you obscure even a small chunk of the data area. The full mechanics, including the trade-off where higher correction means denser codes, sit in the [error correction guide](https://fast-qr.app/learn/qr-code-error-correction-explained).

## How big can a logo actually be?

The widely repeated rule is that level H tolerates 30% loss. The widely ignored caveat is that the 30% includes everything: print imperfections, scratches, bad lighting, glare, the logo, and any other obstruction. If you put a 30% logo on the code and then the print run has a slight smudge, you are out of recoverable headroom and the scan fails.

In practice, plan for the logo to occupy 20-25% of the total QR code area. That gives the error correction roughly five to ten percent of headroom for everything else that goes wrong between the design file and a real phone camera. Measure against the full module grid, not against the printed bounding box plus margin.

A concrete example. On a 5 cm by 5 cm QR code, the total module area is 25 square centimeters. A 25% logo can occupy roughly 6.25 square centimeters, which works out to a square logo of about 2.5 cm on each side. Most wordmarks and icon-style logos look balanced at well under that maximum. If the logo plate, meaning the white shape behind the artwork, is bigger than the logo itself, count the plate, not just the visible artwork.

<figure style="margin: 1.5rem auto; max-width: 560px;">
  <svg role="img" viewBox="0 0 560 220" xmlns="http://www.w3.org/2000/svg" style="width: 100%; max-width: 560px; height: auto;">
    <title>QR code logo size comparison at 15, 22, and 30 percent coverage</title>
    <desc>Three QR code mockups side by side showing increasing logo sizes. The first at 15 percent is labeled Conservative, the second at 22 percent is labeled Recommended max, and the third at 30 percent is labeled Risky and outlined in warm red.</desc>
    <rect x="0" y="0" width="560" height="220" fill="#FAF7F0"/>
    <!-- Mockup 1: 15% Conservative -->
    <g transform="translate(30,20)">
      <rect x="0" y="0" width="140" height="140" fill="#F2EDE2" stroke="#E8E2D9" stroke-width="1"/>
      <g fill="#00476b">
        <rect x="14" y="14" width="28" height="28"/>
        <rect x="98" y="14" width="28" height="28"/>
        <rect x="14" y="98" width="28" height="28"/>
        <rect x="56" y="14" width="14" height="14"/>
        <rect x="84" y="28" width="14" height="14"/>
        <rect x="14" y="56" width="14" height="14"/>
        <rect x="42" y="70" width="14" height="14"/>
        <rect x="70" y="56" width="14" height="14"/>
        <rect x="98" y="70" width="14" height="14"/>
        <rect x="28" y="84" width="14" height="14"/>
        <rect x="84" y="98" width="14" height="14"/>
        <rect x="56" y="112" width="14" height="14"/>
        <rect x="98" y="112" width="14" height="14"/>
        <rect x="112" y="56" width="14" height="14"/>
      </g>
      <g fill="#FAF7F0" stroke="#00476b" stroke-width="1">
        <rect x="20" y="20" width="16" height="16"/>
        <rect x="104" y="20" width="16" height="16"/>
        <rect x="20" y="104" width="16" height="16"/>
      </g>
      <g fill="#00476b">
        <rect x="24" y="24" width="8" height="8"/>
        <rect x="108" y="24" width="8" height="8"/>
        <rect x="24" y="108" width="8" height="8"/>
      </g>
      <!-- 15% logo -->
      <rect x="59" y="59" width="22" height="22" fill="#FAF7F0"/>
      <rect x="61" y="61" width="18" height="18" fill="#E8A21A"/>
      <text x="70" y="160" text-anchor="middle" font-family="system-ui, sans-serif" font-size="11" fill="#081e32" font-weight="600">15% — Conservative</text>
      <text x="70" y="174" text-anchor="middle" font-family="system-ui, sans-serif" font-size="10" fill="#4a7c59">Safe</text>
    </g>
    <!-- Mockup 2: 22% Recommended -->
    <g transform="translate(210,20)">
      <rect x="0" y="0" width="140" height="140" fill="#F2EDE2" stroke="#E8E2D9" stroke-width="1"/>
      <g fill="#00476b">
        <rect x="14" y="14" width="28" height="28"/>
        <rect x="98" y="14" width="28" height="28"/>
        <rect x="14" y="98" width="28" height="28"/>
        <rect x="56" y="14" width="14" height="14"/>
        <rect x="84" y="28" width="14" height="14"/>
        <rect x="14" y="56" width="14" height="14"/>
        <rect x="42" y="70" width="14" height="14"/>
        <rect x="70" y="56" width="14" height="14"/>
        <rect x="98" y="70" width="14" height="14"/>
        <rect x="28" y="84" width="14" height="14"/>
        <rect x="84" y="98" width="14" height="14"/>
        <rect x="56" y="112" width="14" height="14"/>
        <rect x="98" y="112" width="14" height="14"/>
        <rect x="112" y="56" width="14" height="14"/>
      </g>
      <g fill="#FAF7F0" stroke="#00476b" stroke-width="1">
        <rect x="20" y="20" width="16" height="16"/>
        <rect x="104" y="20" width="16" height="16"/>
        <rect x="20" y="104" width="16" height="16"/>
      </g>
      <g fill="#00476b">
        <rect x="24" y="24" width="8" height="8"/>
        <rect x="108" y="24" width="8" height="8"/>
        <rect x="24" y="108" width="8" height="8"/>
      </g>
      <!-- 22% logo -->
      <rect x="53" y="53" width="34" height="34" fill="#FAF7F0"/>
      <rect x="55" y="55" width="30" height="30" fill="#E8A21A"/>
      <text x="70" y="160" text-anchor="middle" font-family="system-ui, sans-serif" font-size="11" fill="#081e32" font-weight="600">22% — Recommended max</text>
      <text x="70" y="174" text-anchor="middle" font-family="system-ui, sans-serif" font-size="10" fill="#4a7c59">Safe with headroom</text>
    </g>
    <!-- Mockup 3: 30% Risky -->
    <g transform="translate(390,20)">
      <rect x="0" y="0" width="140" height="140" fill="#F2EDE2" stroke="#b04a3a" stroke-width="2"/>
      <g fill="#00476b">
        <rect x="14" y="14" width="28" height="28"/>
        <rect x="98" y="14" width="28" height="28"/>
        <rect x="14" y="98" width="28" height="28"/>
        <rect x="56" y="14" width="14" height="14"/>
        <rect x="84" y="28" width="14" height="14"/>
        <rect x="14" y="56" width="14" height="14"/>
        <rect x="42" y="70" width="14" height="14"/>
        <rect x="70" y="56" width="14" height="14"/>
        <rect x="98" y="70" width="14" height="14"/>
        <rect x="28" y="84" width="14" height="14"/>
        <rect x="84" y="98" width="14" height="14"/>
        <rect x="56" y="112" width="14" height="14"/>
        <rect x="98" y="112" width="14" height="14"/>
        <rect x="112" y="56" width="14" height="14"/>
      </g>
      <g fill="#FAF7F0" stroke="#00476b" stroke-width="1">
        <rect x="20" y="20" width="16" height="16"/>
        <rect x="104" y="20" width="16" height="16"/>
        <rect x="20" y="104" width="16" height="16"/>
      </g>
      <g fill="#00476b">
        <rect x="24" y="24" width="8" height="8"/>
        <rect x="108" y="24" width="8" height="8"/>
        <rect x="24" y="108" width="8" height="8"/>
      </g>
      <!-- 30% logo -->
      <rect x="46" y="46" width="48" height="48" fill="#FAF7F0"/>
      <rect x="48" y="48" width="44" height="44" fill="#E8A21A"/>
      <text x="70" y="160" text-anchor="middle" font-family="system-ui, sans-serif" font-size="11" fill="#081e32" font-weight="600">30% — Risky</text>
      <text x="70" y="174" text-anchor="middle" font-family="system-ui, sans-serif" font-size="10" fill="#b04a3a">May fail in print</text>
    </g>
    <text x="280" y="208" text-anchor="middle" font-family="system-ui, sans-serif" font-size="10" fill="#4a6070" font-style="italic">Coverage measured against the full module grid</text>
  </svg>
  <figcaption style="margin-top: 0.5rem; text-align: center; font-size: 0.85rem; color: #4a6070;">Logo size affects scan reliability. Error correction level H tolerates roughly 30% missing data, but real-world prints, glare, and aging codes need headroom. Stay around 20% in production.</figcaption>
</figure>

If your printed code will be smaller than 3 cm, drop the logo size proportionally and consider whether the brand mark adds enough value to justify the reliability cost. The [size and print guidelines](https://fast-qr.app/learn/qr-code-size-and-print-guidelines) cover the math by use case.

## What kind of logo works best

Not every logo is equally suited to embedding. The shapes and contrast that work well in a corporate header do not always survive being dropped into a module grid.

Solid shapes outperform thin lines. A monogram with bold strokes, a filled circle holding a letter, or a chunky wordmark all give scanners a clean boundary. Logos with delicate strokes, fine serif type, or hairline outlines tend to blur into the surrounding modules, especially at small print sizes or after JPG compression.

High-contrast wordmarks beat low-contrast badges. A dark logo on a clean white plate inside a black-on-white code reads instantly. A light gray icon on a textured beige plate inside the same code introduces ambiguity at every edge. The same luminance rules apply if you push the modules themselves to a brand colour — see the [colored QR code guide](https://fast-qr.app/learn/qr-code-colored) for the contrast math and inversion limits.

The logo plate trick is worth the extra five minutes. Most reliable logo placements use a small white circle or rounded rectangle behind the artwork, with five to eight pixels of padding around the logo itself. The plate gives the decoder a sharp light region instead of asking it to interpret module-on-logo transitions. It also visually separates the logo from the QR pattern, which makes the whole thing look intentional rather than glitchy.

Avoid full-color photographic logos inside the code. They almost always introduce mid-tone noise that scanners interpret as ambiguous module data. If the brand mark must be a photograph, reduce it to a single high-contrast silhouette before placing it.

## Where should the logo go?

Center is the safe placement, and almost every logo'd QR code in production uses it. The reasons are mechanical, not aesthetic.

The three large nested squares in the corners are finder patterns. A scanner uses them to detect the code, decide which way is up, and estimate the spacing of the module grid. Damaging any one of them breaks scanning before error correction even runs. The asymmetric three-corner layout is what tells the decoder the code is not upside down.

Larger QR codes also include alignment patterns: smaller nested squares used to correct for perspective and curvature. Like finder patterns, they are off-limits. A logo placed in the bottom-right quadrant of a Version 5 code will often clip an alignment pattern and break decoding even though the data area looks fine on screen.

The geometric center of the code, by contrast, is data and error-correction modules with predictable redundancy. Centering keeps the logo away from the special patterns and concentrates the data loss in a region the error correction was designed to recover. The [QR anatomy section](https://fast-qr.app/learn/what-is-a-qr-code) walks through what each pattern does in plain terms.

<figure style="margin: 1.5rem auto; max-width: 560px;">
  <svg role="img" viewBox="0 0 360 360" xmlns="http://www.w3.org/2000/svg" style="width: 100%; max-width: 420px; height: auto;">
    <title>QR code logo placement zones</title>
    <desc>A QR code mockup highlighting three corner finder patterns and one alignment pattern as no-go zones outlined in warm red, with the centered data area highlighted as a safe logo zone in green.</desc>
    <!-- Quiet zone background -->
    <rect x="0" y="0" width="360" height="360" fill="#F2EDE2"/>
    <!-- Code area background -->
    <rect x="30" y="30" width="300" height="300" fill="#FAF7F0" stroke="#E8E2D9" stroke-width="1"/>
    <!-- Data modules (decorative grid) -->
    <g fill="#00476b">
      <rect x="120" y="42" width="12" height="12"/>
      <rect x="156" y="42" width="12" height="12"/>
      <rect x="192" y="42" width="12" height="12"/>
      <rect x="42" y="120" width="12" height="12"/>
      <rect x="42" y="156" width="12" height="12"/>
      <rect x="42" y="204" width="12" height="12"/>
      <rect x="120" y="120" width="12" height="12"/>
      <rect x="144" y="120" width="12" height="12"/>
      <rect x="180" y="132" width="12" height="12"/>
      <rect x="216" y="120" width="12" height="12"/>
      <rect x="120" y="156" width="12" height="12"/>
      <rect x="216" y="156" width="12" height="12"/>
      <rect x="120" y="192" width="12" height="12"/>
      <rect x="156" y="192" width="12" height="12"/>
      <rect x="216" y="192" width="12" height="12"/>
      <rect x="120" y="216" width="12" height="12"/>
      <rect x="180" y="216" width="12" height="12"/>
      <rect x="252" y="120" width="12" height="12"/>
      <rect x="252" y="156" width="12" height="12"/>
      <rect x="252" y="204" width="12" height="12"/>
      <rect x="120" y="252" width="12" height="12"/>
      <rect x="156" y="252" width="12" height="12"/>
      <rect x="216" y="252" width="12" height="12"/>
      <rect x="252" y="252" width="12" height="12"/>
      <rect x="288" y="120" width="12" height="12"/>
      <rect x="288" y="180" width="12" height="12"/>
    </g>
    <!-- Top-left finder pattern (7x7) -->
    <g>
      <rect x="42" y="42" width="84" height="84" fill="#00476b"/>
      <rect x="54" y="54" width="60" height="60" fill="#FAF7F0"/>
      <rect x="66" y="66" width="36" height="36" fill="#00476b"/>
      <rect x="36" y="36" width="96" height="96" fill="none" stroke="#b04a3a" stroke-width="2.5" stroke-dasharray="4 3"/>
    </g>
    <!-- Top-right finder pattern -->
    <g>
      <rect x="234" y="42" width="84" height="84" fill="#00476b"/>
      <rect x="246" y="54" width="60" height="60" fill="#FAF7F0"/>
      <rect x="258" y="66" width="36" height="36" fill="#00476b"/>
      <rect x="228" y="36" width="96" height="96" fill="none" stroke="#b04a3a" stroke-width="2.5" stroke-dasharray="4 3"/>
    </g>
    <!-- Bottom-left finder pattern -->
    <g>
      <rect x="42" y="234" width="84" height="84" fill="#00476b"/>
      <rect x="54" y="246" width="60" height="60" fill="#FAF7F0"/>
      <rect x="66" y="258" width="36" height="36" fill="#00476b"/>
      <rect x="36" y="228" width="96" height="96" fill="none" stroke="#b04a3a" stroke-width="2.5" stroke-dasharray="4 3"/>
    </g>
    <!-- Alignment pattern (5x5) lower-right area -->
    <g>
      <rect x="246" y="246" width="48" height="48" fill="#00476b"/>
      <rect x="255" y="255" width="30" height="30" fill="#FAF7F0"/>
      <rect x="264" y="264" width="12" height="12" fill="#00476b"/>
      <rect x="240" y="240" width="60" height="60" fill="none" stroke="#b04a3a" stroke-width="2.5" stroke-dasharray="4 3"/>
    </g>
    <!-- Center logo zone -->
    <rect x="138" y="138" width="84" height="84" fill="#4a7c59" fill-opacity="0.18" stroke="#4a7c59" stroke-width="2.5" stroke-dasharray="5 3"/>
    <text x="180" y="178" text-anchor="middle" font-family="system-ui, sans-serif" font-size="12" fill="#081e32" font-weight="700">Logo zone</text>
    <text x="180" y="194" text-anchor="middle" font-family="system-ui, sans-serif" font-size="11" fill="#4a7c59" font-weight="600">≤ 25% area</text>
    <!-- Labels -->
    <text x="84" y="22" text-anchor="middle" font-family="system-ui, sans-serif" font-size="11" fill="#b04a3a" font-weight="600">Don't cover</text>
    <text x="276" y="22" text-anchor="middle" font-family="system-ui, sans-serif" font-size="11" fill="#b04a3a" font-weight="600">Don't cover</text>
    <text x="84" y="350" text-anchor="middle" font-family="system-ui, sans-serif" font-size="11" fill="#b04a3a" font-weight="600">Don't cover</text>
    <text x="270" y="350" text-anchor="middle" font-family="system-ui, sans-serif" font-size="11" fill="#b04a3a" font-weight="600">Alignment — avoid</text>
  </svg>
  <figcaption style="margin-top: 0.5rem; text-align: center; font-size: 0.85rem; color: #4a6070;">Logo placement zones: avoid the three finder patterns (corners) and the alignment pattern (lower right). Centered placement in the data area, sized at no more than ~20-25% of the code, is safest.</figcaption>
</figure>

Off-center placements are not impossible, but they require manually checking that the logo sits clear of finder patterns, alignment patterns, and the thin row of timing modules between the corners. If you want anything other than dead center, you are signing up for code-by-code QA.

## Common failure modes

Most failed logo'd QR codes share a small set of root causes. The pattern repeats often enough that it is worth memorizing.

A too-large logo is the most frequent. Designers measure the logo at 20% in the design file, then add a generous white plate behind it, and the combined obstruction is closer to 35% by the time it prints. Always measure the plate, not just the artwork.

Intricate logos with thin strokes are the second most common. A delicate script logo or a logo with hairline borders tends to blur into the surrounding modules under any imperfect print, and decoders cannot lock onto the boundary. Solid silhouettes are far more forgiving.

Logos placed over a finder pattern fail catastrophically. The code does not even register as a QR code in many camera apps, because the asymmetric three-corner detection fails. This usually happens when a designer manually moves the logo "for visual balance" and clips a corner without realizing what those corner squares do.

Low-contrast logos on busy QR backgrounds blur the boundary even when sizes are reasonable. A pale gold icon on a dark navy code looks elegant in the mockup and loses three out of ten scans on real phones. A high-contrast monochrome silhouette works better than a brand-colored one nearly every time.

Finally, error correction set below H combined with any logo at all is a slow-motion failure. The code might scan when freshly printed in a controlled studio. It will not survive a fingerprint, a scratched menu sleeve, or a poorly-lit room. Always pair logos with H.

## Testing a logo'd QR before you ship

A logo'd QR code passes when it scans instantly on the worst combination of phone, lighting, and print quality your customers will encounter. Anything less than that is a guess.

Build a simple test protocol and run it before any large print run.

1. Print the final design at the actual size you plan to ship. A monitor preview at 200% zoom is not a substitute, because the camera does not see the same thing your eye does on a 27-inch display.
2. Test on at least three phones: one current iPhone, one current mid-range Android, and one older Android (four to five years old). Older budget Android cameras are the floor for real-world reliability. If they fail, your most price-sensitive customers fail too.
3. Vary the lighting. Overhead glare, dim restaurant light, sunlight through a window, and a fluorescent office. Each one stresses the camera differently.
4. Vary the distance and angle. A table tent gets scanned from 30 cm. A wall poster gets scanned from one to two meters. A package label gets scanned at whatever angle the customer happens to be holding it.
5. Test the final substrate. A glossy menu sleeve, a matte vinyl sticker, and a printed business card all interact with light differently. Lamination especially can introduce reflections that change scan behavior.

If any device misses the scan more than once in five attempts, the design is not ready. Either reduce the logo size, increase the printed size of the code, or shorten the URL to lower the QR version (and therefore enlarge each module). The [design best practices guide](https://fast-qr.app/learn/qr-code-design-best-practices) covers broader pre-print checks beyond logos.

## When to skip the logo

Sometimes the right call is to ship the QR code without a logo. The brand mark belongs nearby, on the same card or sign, but not embedded inside the code itself.

Skip the logo when print sizes are very small. A QR code on a 3.5 cm by 5 cm business card has so few square millimeters that any logo eats meaningful module space. A nearby brand wordmark on the card itself works better than an embedded one inside a code that already has tight tolerances. The [business cards playbook](https://fast-qr.app/qr-code-for/business-cards) walks through this trade-off in context.

Skip the logo when the URL is long. Tracking parameters, UTM codes, and session IDs balloon a payload, which forces the encoder to use a higher QR version with smaller modules. At higher versions, the same physical print size leaves each module barely visible, and any obstruction at all degrades scans noticeably. Either drop the logo or shorten the URL via a redirect on a domain you own.

Skip the logo when the color scheme is already inverted or borderline. A light-on-dark QR code is already pushing decoder assumptions, since most camera apps assume dark modules on a light background. Stacking a logo on top of an inverted code compounds the risk. Keep one challenging customization at a time.

Skip the logo on packaging that lives in rough conditions. Outdoor labels, freezer goods, and warehouse stickers experience scratches, fading, and condensation. Reserve every point of error-correction headroom for those insults rather than spending it on branding. The [QR statistics roundup](https://fast-qr.app/blog/qr-code-statistics) shows how scan reliability translates directly to engagement.

When you do ship a logo'd code, export it in a format that preserves edges. Use the [URL to SVG generator](https://fast-qr.app/static/url-to-svg) for print and signage, and the [URL to PNG generator](https://fast-qr.app/static/url-to-png) for digital and quick sharing. The vector path keeps both the modules and the logo crisp at any size.

For the broader set of brand-customization decisions that surround logo placement — module shapes, frame designs, eye styling, color palettes, and when each customization is safe — see [QR code design principles](https://fast-qr.app/blog/qr-code-design-principles).

## Sources

- [Denso Wave — Error correction feature](https://www.qrcode.com/en/about/error_correction.html) — Inventor's overview of the four QR error correction levels and their recovery percentages.
- [Wikipedia — QR code (Error correction)](https://en.wikipedia.org/wiki/QR_code#Error_correction) — Reed-Solomon redundancy, level definitions, and how scanners reconstruct lost modules.
- [ISO/IEC 18004:2015](https://www.iso.org/standard/62021.html) — The international standard that formally defines QR code structure, including the patterns logos must avoid.

## Frequently asked questions

### Can you put a logo in the middle of a QR code?

Yes. With error correction set to level H (about 30% recovery), a centered logo covering up to 20-25% of the QR code area scans reliably on modern phones. The logo must sit in the center, never over the three corner finder patterns or any alignment patterns, and should keep enough contrast against the surrounding modules for scanners to find a clean threshold.

### What error correction level should a QR code with a logo use?

Use level H (High, around 30% recovery) for any QR code with an embedded logo. The logo blocks data modules, and H gives scanners enough redundancy to rebuild the payload. Lower levels like L or M leave too little headroom once you add a logo, especially when print or lighting is imperfect.

### How big can a logo on a QR code be?

A logo can safely cover up to about 20-25% of the QR code area when error correction is set to H. Going beyond that risks scan failures on older phones, in low light, or on small print sizes. Measure the logo against the full code including its quiet zone, not just the eye-catching center.

### Where should the logo go on a QR code?

Always center the logo. Centering keeps the three corner finder patterns and the timing patterns clear, and gives the scanner the best chance of locking onto the grid before the data area is decoded. Off-center logos often clip a finder pattern or alignment pattern and break scanning entirely.

### Why does my QR code with a logo fail to scan?

The most common causes are a logo that covers more than about 25% of the code, a logo placed over a finder pattern or alignment pattern, low contrast between the logo and surrounding modules, error correction set below H, or print conditions that compound an already tight design. Test on multiple phones at the final printed size to confirm reliability.

### Should I add a white background plate behind my logo?

Yes. A small white circle or rounded rectangle behind the logo gives scanners a clean light/dark threshold instead of asking them to interpret module-on-logo edges. Keep the plate just slightly larger than the logo itself so it does not eat extra modules unnecessarily.

### Can a QR code with a logo work on a business card?

It can, but the margin for error is tighter than on larger formats. Business cards often print QR codes around 2-2.5 cm, so a logo plus brand colors plus a long URL can push reliability below acceptable. Keep the URL short, error correction at H, the logo small and centered, and run a real print proof on multiple phones before ordering a full run.
