QR code color and contrast

QR code color and contrast is a camera problem. Keep dark modules on a lighter field, or build a true invert the camera accepts. Dark on dark fails. A white patch on glass is the window fix. Canva one-offs still owe the same contrast. Brand palettes do not override finders.

QR code color and contrast

You are about to pick inks. This is not a hosted-versus-static lesson except that both encodings fail the same way when contrast dies. Packaging plus foil is the usual trap. A with-logo file adds a second way to wreck finders.

ISO/IEC 18004 cares that the camera can locate three nested squares. It does not care that your brand book loves navy on charcoal.

Pick inks that stay dark-on-light, then proof on the real stock

1. Set module colour darker than the ground. Measure with your eyes at arm length, rather than trusting a backlit laptop.
2. Keep finders high contrast. Do not recoup them in a pale tint.
3. If you want light modules on a dark poster, invert the whole symbol correctly or put a light patch down first.
4. On glass, add a white patch on glass so the street is not the ground.
5. On foil or metal, print the symbol on a solid white patch, then foil around it.
6. Prefer spot ink not four-colour fringe for the dark modules on offset.
7. Avoid gloss-only on the symbol if downlighters sit above tables. Matte the code area.
8. Export SVG or 300 dpi at final millimetres. Size at least 2 cm at 30 cm.
9. Scan proofs with iOS Camera and Android Camera. If only one brand reads it, contrast is still marginal.

Can you use brand colours in the modules

Yes, inside the contrast rule. Red on white often works. Yellow on white often does not. Test. Error correction H helps scuff, not pale ink.

A website in brand colours still 302s. Colour is not analytics.

When does invert actually scan

When it is a true invert or finders remain dark-on-light. A navy square on a navy poster with no patch is unread. Dark wood and brick need a light patch for the same reason.

How do you proof contrast before the run

Real stock, real light, two phones. The designer preview is RGB and /qr-preview besides.

Failure modes of a colour brief

Four-colour grey fringes. Metallic modules. Transparent window stickers. Logo over a finder. Screenshot upscaling.

When you only needed black squares on white for a fridge URL, Canva black-and-white is enough. Sibling: black and white QR code design. Dark grounds: QR code on a dark background.

Foil, glass, and the proof that the laptop cannot give you

Foil is not a module colour. Print the symbol on a white patch, then foil the frame. Glass is not a ground. Back it with white or the street becomes the light modules. Dark wood and brick need a light patch for the same invert reason as D8. Emboss breaks edges. Keep QR on flat ink.

Spot colour at 100% of one ink beats a four-colour build that fringes on register. Gloss on the symbol area under downlighters is a flare. Matte that patch. Size still at 2 cm or above at 30 cm. H if you add a logo or scuff. Finders intact. Quiet zone intact.

Proof on the real stock with iPhone Camera and Android Camera. If only the calibrated monitor looks fine, you do not have contrast. You have a backlit lie. Canva one-offs owe the same proof. Hosted 302 hops cannot rescue a navy-on-navy square. Brand colours are allowed when they still threshold. Yellow on white usually does not. Test rather than argue with the brand book.

Low toner on a 'black' module is grey. Grey on cream fails more phones than a brand red on white that you actually tested. Printers must hit 100% of the dark ink. Designers must stop adding drop shadows to modules. Shadows are grey on purpose. Finders are nested squares, not rounded stickers. If you round them for friendliness, Camera loses the locator. Quiet zone is empty, not filled with a faint pattern. Proof. Two operating systems. Real light. Then run. Canva exports owe that proof too.

Neon inks look dark to designers and pale to cameras. Proof. Pastel grounds look friendly and kill modules. Proof. The how-to is the proof, repeated on stock, not a palette meeting. When the proof fails, revert to black and white QR code design on a white patch and put the neon in the caption.

Last proof: two phones, real stock, real light, finders dark enough, ground light enough, or a true invert, white back on glass, white patch on foil, no drop shadows on modules, no rounded finders, quiet zone empty. Fail any one and colour was a hobby. Revert to two-tone on a patch. Hosted 302 will not threshold a pale module. Canva will not either.

If the brand book loses the scan test, the book yields, not the camera. White patch. Dark modules. Proof two phones. Then wrap colour around the square. Hosted hops and Canva files fail the same way when contrast dies. Neon is not dark because it is loud. Grey from a drop shadow is not a module. Rounded finders are not finders.

A navy square on a charcoal vehicle wrap is a contrast failure wearing brand confidence. White patch first, then the symbol, then the wrap colours around it. Proof from the neighbouring lane, not from a laptop in the garage. Hosted 302 will not save it. Canva will not save it. Size for the lane. H for scuff. Finders intact. That is colour-and-contrast as a wrap brief.

Drop shadows, rounded finders, pale neon, four-colour grey, foil modules, and glass without a back are the usual contrast autopsies. Fix those before you change generators. Canva and SmartQRCode fail the same autopsy. Proof is the procedure. Brand is the frame around a square that already scans.