Back to Updates

QR Codes: Best Settings by Medium

A
Admin
2026-11-15
Last updated 2026-11-15

Quick answer

Error correction at M for ordinary print and screen use, Q or H for anything handled, folded or partly covered. Keep the modules black or near-black on white or near-white. Four modules of quiet zone is the minimum and more is safer on busy artwork. Size is the one setting you cannot judge on screen: decide the printed width, print a proof, and scan it from the distance a user will stand.

What this article covers

The four settings that matter by medium, and the reasoning behind each. It also covers the one interaction people miss — that raising error correction makes the symbol denser, which makes it need more width — and what to do about it without making the code unreadable.

What it actually does

Error correction adds redundant data so a scanner can reconstruct what it could not read. L survives about 7 per cent damage, M about 15, Q about 25, H about 30. The cost is capacity: the same text at H uses more modules than at L, so the symbol is denser and each module is smaller at a fixed printed width.

Symbol width sets the nominal size. Because the output is an SVG, it scales cleanly; the number mostly matters as the size the file declares and as a way to keep consistent assets. The real constraint is the printed size and the module count: a phone needs each module to be large enough in the camera's view.

Quiet zone is the clear margin. Four modules is the specification's minimum and the encoder refuses less. On busy packaging, taking 6 to 8 modules makes the symbol easier to find.

Colours must keep the modules darker than the background. The default black on white is the most reliable. Brand colours work if the contrast is strong; an inverted palette is a gamble.

Caption is composed below the symbol and adds height. It is useful on a menu or a label, and harmful if it crowds the quiet zone.

The setting people underestimate is the relationship between module count and printed width. A short URL at level M might be 25 modules across; the same URL at level H might be 33. Printed at the same width, each module in the denser symbol is smaller, and a phone camera needs a minimum number of camera pixels per module to read it reliably. That is why "raise the level" is not a free safety measure: it buys damage tolerance with density, and density has to be paid for in millimetres. On a small label the cheaper fix is almost always a shorter payload — a path like /q/7 instead of a full address with tracking parameters.

Step by step

  1. Choose the medium and read the row below.
  2. Shorten the payload before raising error correction — removing characters is cheaper than adding density.
  3. Set the error correction level for the medium.
  4. Set the width for the asset, and note the physical print size separately.
  5. Keep the quiet zone at 4 or more.
  6. Use dark modules on a light background.
  7. Generate, proof, and scan.
Medium Error correction Printed width Notes
Packaging, handled H 25–30 mm survives folds and scuffs
Menu or table card M–Q 20–30 mm matte paper scans better than gloss
Equipment label Q–H 15–25 mm small labels need short payloads
Business card M 15–20 mm short URL, high contrast
Invoice or letter M 20–25 mm black on white, plenty of margin
Screen or slide M 200+ px 320 px default is fine
Poster Q 40+ mm scan distance is longer

What to check after download

  • Proof at final size, on the real material if possible.
  • Scan distance, from where a user would actually stand.
  • Contrast in the lighting the code will live in.
  • A fold or curve, if the code sits on packaging.
  • The quiet zone, including any caption or border the designer added.
  • A second phone, because cameras differ.
  • The decoded URL, character for character.
  • The material at the scanning angle, because a gloss laminate reflects the light a camera needs and a matte one does not.
  • A second print sample, ideally from the same run, since ink density can vary across a sheet.

Common beginner mistakes

Raising error correction to H "for safety" without increasing the printed size. The symbol becomes denser and may scan worse, not better.

Using a long tracking URL with many parameters. Every character costs modules; a short link on your own domain is better.

Placing the code on a curved bottle without a proof. A flat screen test says nothing about a cylinder.

Choosing a brand palette with low contrast because it looks better on the mock-up. The mock-up is not the scanner.

Putting the code where a shelf edge, a sticker or a hand will cover it.

When this tool is the right choice

When the medium is fixed and the payload is short. The settings above are a starting grid, not a guarantee: the proof scan is the acceptance test, and it is the only one that counts.

Related tools

Resize an Image prepares the photograph or artwork the code sits on. Merge PDF Files combines a designed sheet with its instructions, and PDF Converter renders that sheet as images when a layout tool needs pixels.

Use this tool

Pick the medium's row on QR Code Generator, generate, and proof at the real size before the print run.

Next step

Read business use cases for the workflows where a code is printed at scale and the proof step has to become a procedure.

Tags