QR code error correction
SmartQRCode editorial · Updated October 2026
QR code error correction is four named levels: L about 7 percent, M about 15 percent, Q about 25 percent, H about 30 percent of the symbol that can be restored. Higher correction survives scuffs and logos and packs the same payload into a denser pattern. It does not fix a cropped finder or a 12 mm stamp.
QR code error correction as a damage budget, not a quality grade
The mechanism restores modules the camera could not sample: glare, a thumb, uncoated stock that drinks ink. Level L seven percent is the smallest budget. Level H thirty percent is the largest. You pay for H as extra modules, so the grid looks busier at the same millimetres. That is dense grid after raising H, the same density story as a longer payload.
How QR codes work is decode plus this restoration. Anatomy is where finders sit; correction cannot rebuild a finder you covered. Data capacity is why H plus a long static URL turns a card into pepper. A logo generator spends this budget on purpose.
Uncoated stock needs a slightly larger symbol or a coated sheet, not a drop to L. Outdoor boards often want H and a size for the real distance. Packaging scuffs; test the formed pack.
Which level should a clean flyer use
M on coated toner is the boring default. L is for a short payload on clean paper when you need the coarsest grid. Q sits between. If you do not know the stock, M then a proof scan is cheaper than guessing H and shrinking the print to fit a leftover column.
A Canva one-off that will never be counted can stay at whatever that widget ships. QR code error correction still applies to that static file; Canva is not exempt from physics. If the Canva export looks busy after you add a giant crest, you spent the budget. Shrink the crest.
Does a centre logo need H
A logo in the centre is recovered by error correction, not by a special logo mode. Logo spends correction budget. If the artwork covers more than the level can restore, finders may still be visible and the code still fails. H is the usual spend. Then look at the millimetres. If the grid is pepper, enlarge or shorten what the modules store. Hosted short URLs help. Covering a finder is not a logo problem; it is a locate problem. QR code error correction never rebuilds a corner you trimmed. If the proof fails with finders intact, then raise H or enlarge. If a finder is gone, stop talking about L M Q H and restore the corner. QR code error correction is a payload budget. Location is a finder budget. Do not spend one on the other.
When high correction is the wrong lever
When the failure is quiet zone, invert, crop, or viewing distance. Raising H will not rebuild a corner you trimmed off a business card. Raising H will not make a footer stamp on a lecture slide readable from row twelve. Enlarge, host a shorter address, or move the mark. For a throwaway poster, a static Canva file at M is enough; spending H on a hosted code you will never reprint is not the honesty move.
Correction cannot rebuild a missing finder
QR code error correction restores payload modules. It does not rebuild a nested square you covered with a crest, cropped on a 16:9 slide, or bled off a round corner. If the camera cannot locate the symbol, the damage budget never runs. That is why layout failures look like "we should have used H" in a post-mortem. You needed millimetres, quiet zone, and three intact finders.
A logo in the centre is the legitimate spend. A logo on a finder is not. Test after the logo is in, at the final millimetres, on the final stock. If it fails, shrink the logo or enlarge the print. Raising H on a 12 mm stamp is the wrong lever. Packaging that scuffs still needs size. Outdoor UV ink chalks; plan a reprint. Hosted destinations can change; faded modules cannot. A Canva one-off that will never be counted can ignore this paragraph and still should not cover a finder.
Questions this raises
M is the usual starting point on coated toner. L is tighter on damage. Q or H when the stock scuffs, the mark is wiped, or a logo sits in the centre.
A logo is recovered by error correction, not a logo mode. If the logo covers more than the chosen level can restore, the code fails even with finders visible. H is the usual spend; then check density at your millimetres.
When the real problem is size, quiet zone, or a cropped finder. Raising H on a 12 mm stamp still leaves modules too small. Enlarge or host a shorter URL.
No. L through H change how much damage the camera can restore. Hosting is a separate hop after decode.
Often yes, with a size for the real viewing distance. Correction cannot invent millimetres.
Keep going
The tools and playbooks this post refers to, one click away.
Make the code this post is about
$1.99 for 7 days, then a paid plan. Pick a type, brand it, and edit the destination whenever you like, even after it is printed.