How to Make a QR Code With a Logo That Still Scans
A QR code on a business card, menu or package is almost always a faceless black‑and‑white square. Yet dropping a logo in the middle and painting the code in brand colors takes five minutes and zero budget — and it will still scan. The key is understanding why it works, so you don't cross the line where cameras stop reading it.
A QR code survives a logo in the middle thanks to redundancy: at error‑correction level H the code stays readable with up to 30% of its surface damaged. Safety rules: logo no larger than 20-25% of the area, correction level H, dark code on a light background (never inverted), a mandatory quiet zone around the edges, and a test on several phones before printing.
Why the code works with a "hole" in the middle
The QR code was engineered for harsh environments — Toyota factories, dirt, damaged labels. So it ships with Reed–Solomon error correction: data is written redundantly, and a share of modules (the little black‑and‑white squares) can be lost without losing the content.
There are four correction levels:
| Level | Recovers | When to use |
|---|---|---|
| L | up to 7% | maximum data, no logo |
| M | up to 15% | the everyday default |
| Q | up to 25% | a small logo |
| H | up to 30% | a centered logo — your pick |
To the scanner, a logo in the middle is just "damage". As long as it stays within the safety margin, the code reads as if nothing happened.
30% is the budget for all damage combined: the logo, glare, package curvature, print wear. If the logo eats 25%, only 5% is left for real life. So the practical ceiling for a logo is 20-25% of the area, not the full 30%.
Step by step
Step 1. Prepare the logo
A compact mark works best — the icon, not the full lockup with text (see types of logos for the difference). Download the SVG or PNG of the brand you need — for example from our logo catalog, where every brand ships a standalone icon. A logo on a backing plate (white square or circle) scans more reliably than a "bare" mark over the modules.
Step 2. Generate the code
Plenty of free generators support logos: QRCode Monkey, QR.io, Flowcode and others; Canva and Adobe Express
have built‑in ones. What to set:
- Correction level — H. Sometimes hidden under "advanced settings".
- Logo — centered, no more than a quarter of the code.
- Export as SVG if the code goes to print: vector stays crisp at any size (why that matters — vector vs raster). PNG is fine for the web.
Step 3. Color by the contrast rules
You can paint the code in brand colors, with limits:
- Dark code on a light background. Inverted codes (light on dark) aren't read by all scanners.
- Maximize contrast. Pale yellow on white doesn't count. Quick check: photograph the layout in black‑and‑white mode — the code must remain obviously darker than the background.
- Gradients are fine if both ends of the gradient are dark enough.
The exact brand color is easy to grab right from the logo's page in our catalog — see how to find out a logo's color.
Step 4. Don't touch the functional zones
A QR code has untouchable parts:
- Three big corner squares — finder patterns: the camera uses them to locate and orient the code.
- The quiet zone — an empty margin at least 4 modules wide around the perimeter. Don't crowd the code with text or borders.
- The small square near the bottom‑right — the alignment pattern.
The logo must sit strictly in the center and clear all of these marks.
Step 5. Test before printing
Test the code on at least two phones (iPhone and Android), with the stock camera, in poor light and at an angle. For print runs, print one copy at real size first. The minimum physical size for handheld scanning is about 2×2 cm; for posters use the rule: code size ≈ scanning distance ÷ 10.
The shorter the link, the tougher the code
Another reliability lever almost nobody thinks about — payload size. QR codes come in 40 "versions": version 1 is a 21×21 module grid, version 40 is 177×177. The more characters you encode, the higher the version, the smaller the modules and the fussier the scanning — especially with a logo eating part of an already fine grid.
Practical consequences:
- Shorten the link.
example.com/qrinstead of a long UTM‑laden URL drops the code several versions down — modules get bigger, the code scans from farther away and shrugs off damage better. - UTM tags via redirect. Let a short link on your own domain 301-redirect to the long tagged one: analytics survive, the code stays simple.
- Don't encode text "just in case". A business card with a 500-character vCard is version 20+ with microscopic modules; a link to a contact page works better.
Rule of thumb: if the code looks like fine checkered grit in the layout, the payload is too big. Shrink the data, not the logo.
Styling the modules: where the line is
Generators race to offer "pretty" codes: rounded dots, circles instead of squares, decorative finder eyes. What's actually safe:
- ✅ Slightly rounded module corners — scans fine.
- ✅ Brand color within the contrast rules from the earlier section.
- ⚠️ Circle dots instead of squares — work, but shrink each module's effective area; don't combine with a large logo.
- ⚠️ Shaped finder eyes (rounded, leaf‑shaped) — acceptable while the overall "square in a square" silhouette survives.
- ⛔ Light‑to‑dark gradients, patterns inside modules, a photo background under the code — the top scannability killers.
A good rule: styling should be invisible to the scanner. If a decorated code stops reading in shade or at an angle, roll back one effect at a time, starting with the most aggressive.
Common mistakes
- Logo bigger than a third of the code. Pretty in the mockup — dead in the field.
- Correction level L "to keep it compact" plus a logo — the code won't read at all.
- Light code on a dark background. Some scanners don't handle inversion.
- Code saved as JPG. Compression artifacts blur module edges; use PNG or SVG (formats compared in PNG vs JPG).
- A dynamic link through a questionable middleman service. If the service dies, every printed code dies with it. For important runs, encode a direct link to your own domain.
Pre‑print checklist
- Correction level — H.
- Logo ≤ 25% of the area, centered, clear of the corner finder patterns.
- Link shortened; UTM handled by a redirect on your own domain.
- Dark code on a light background, contrast verified.
- Quiet zone — at least 4 modules of emptiness around the perimeter.
- Export as SVG (print) or PNG (screen), never JPG.
- Test: two phones, stock camera, poor light, 45° angle.
- For print runs — a proof print at real size.
- The link opens a mobile‑friendly page: people scan with phones.
- The code is captioned with an action — "Point your camera — open the menu": captioned codes convert noticeably better.
In short
A QR code with a logo isn't a hack — it's a built‑in feature of the format: level‑H redundancy honestly pays for the "hole" in the middle. Keep the logo within a quarter of the area, set correction to H, watch contrast and the quiet zone, test before printing — and a branded code will scan as reliably as a black‑and‑white one. Brand icons to drop into your code are in our logo catalog, in SVG and PNG.