QR Codes on Brochures: What to Link and Where to Put It

A brochure already carries the long explanation. That is the whole point of the format: three or six panels of copy, photography, and detail that a poster could never hold. So when a QR code goes on one, it is competing with the paper it is printed on, and a code that points at "our website" loses that competition every time. The scan has to deliver something the reader cannot get by turning the leaflet over.

What is actually worth linking

The test is simple. Ask what the reader would want in their hand five minutes after they put the brochure down, and whether the paper can supply it. If it can, print it. If it cannot, that is your link.

Destinations that survive the test:

• A PDF the reader keeps. The spec sheet, the full price list, the technical drawing, the terms. Brochures get recycled; a downloaded file lives on the phone and gets forwarded to a partner or a colleague.
• A video walkthrough. A property tour, a machine in operation, a procedure explained by the clinician who performs it. Motion is the one thing print genuinely cannot do, so it is the strongest case for a scan.
• A booking or enquiry form. The shortest path between reading and acting. If the brochure exists to generate appointments, viewings, or quotes, this is the highest-value target on the panel.
• A map to the location. Far better than a printed address someone has to retype, and it works while they are already standing outside with the leaflet.
• A price list that changes. Anything with a number that will be wrong in six months belongs behind the code rather than in the ink.

Destinations that fail it: the homepage, a social profile, a generic contact page, a newsletter signup. None of them answers a question the brochure raised, and a code landing on a homepage is asking someone to do navigation work as a reward for scanning.

One code per brochure is usually right. Two can work if the panels serve genuinely different jobs, say a video on the front and a booking form on the back. Beyond that you are asking the reader to choose, and choosing is friction.

Matching the link to the brochure

Brochure type	Best destination	Static or dynamic
Conference handout	Slide deck or demo booking form	Dynamic
Estate agent property leaflet	Video tour and floor plan	Dynamic
Clinic or patient information leaflet	Aftercare PDF or appointment page	Dynamic
Product or equipment brochure	Full specification PDF	Dynamic
Tri-fold service menu	Current price list	Dynamic
Museum or venue leaflet	Map and opening times	Dynamic
Company profile with a contact panel	vCard for the named contact	Static

The pattern in that column is not an accident. Almost everything on a brochure wants to be dynamic, and the reason is the format itself.

Why a dynamic code matters more here than almost anywhere else

Brochures have unusually long lives. They sit in a rack by a reception desk, in a conference tote at the bottom of a wardrobe, in a glovebox, in a folder someone opens when they finally get around to the decision. A poster comes down after the campaign. A brochure is still being picked up eighteen months later by someone who has no idea the campaign ended.

A static code encodes the destination in the pattern, so it is fixed the moment the ink dries. When the landing page moves or the campaign URL is retired, every copy in every rack becomes a dead end, and you cannot fix it without reprinting.

A dynamic code encodes a short redirect on a domain you control. The printed pattern never changes; the destination behind it does. That means the leaflet from the 2026 trade show can be repointed at the 2027 page, a retired product's code can be sent to its replacement, and a page rebuild does not orphan ten thousand pieces of paper. For a format that outlives its own campaign by a year or more, that single property is worth more than everything else on this page.

The trade-off is honest: a dynamic code depends on the redirect service running and the domain staying renewed. For a brochure that is an acceptable dependency, because the alternative is a printed link that will certainly break. For something permanent like an engraved plaque, weigh it differently.

Where it goes on the panel

The reliable default is the back panel, bottom right. Two reasons, and both are physical. That is where a thumb naturally rests when someone holds a tri-fold, so the code is under the eye at the moment the reader is deciding whether to keep the thing or bin it. And on almost every fold layout, the back panel is a clean rectangle with no crease running through it.

The crease is the part people get wrong. Never place a code across a fold or in the gutter. A fold does not just bend the paper, it lifts and cracks the ink along the crease, and the raised edge throws a shadow line straight through the module grid. Scanners read that line as damage.

Keep clear of the trim edge too. Guillotine drift of two or three millimetres is normal, and a code that loses part of its quiet zone to the cut stops working. Give it the full four modules of blank margin, then hold it at least 8 mm inside the trim line.

Two other placements work well: the inside back panel beside the contact details, and directly under the item a code relates to if the brochure is a product grid. What does not work is floating the code over a photograph or shrinking it into the footer strip with the legal text.

Whatever panel it lands on, write a line of text next to it saying what the scan gives. "Scan for the 3 minute video tour" earns more scans than a bare code, and it tells a reader holding a two year old leaflet whether the link is still worth their time.

Size it for reading distance

A brochure is held, not viewed across a room. That puts the code roughly 25 to 40 cm from the camera, and the standard rule applies: the code should be about one tenth of the scanning distance across.

Held at	Minimum width	Comfortable width
25 cm	2.5 cm	3 cm
30 cm	3 cm	3.5 cm
40 cm	4 cm	4.5 cm

In practice, 3 cm square is the number to design around for a standard tri-fold, and it is worth defending against whoever wants to shrink it for layout reasons. Two things push you toward the larger end. Older eyes hold paper further away, so a clinic or pension leaflet should assume 40 cm rather than 25 cm. And a long URL with tracking parameters produces a denser grid that needs more physical space to stay readable, which is another quiet argument for a short redirect link.

Getting it through print intact

Send the code as vector, in the artwork, at final size. Module edges have to land crisply, and a PNG scaled up in the layout file gives you soft grey fringes exactly where the scanner is looking for a hard boundary.

Then check these before the file leaves your hands:

• Convert to CMYK yourself and re-check contrast afterwards. A brand colour that looks strong in RGB can arrive noticeably lighter in CMYK, and contrast that was marginal on screen becomes a failure on paper.
• Build the dark modules from a solid ink, not a four-colour mix. A spot colour or a rich black holds its edges. A build of four plates can misregister by a fraction of a millimetre, and on a fine grid that produces a coloured halo around every module.
• Specify matte lamination if you laminate at all. Gloss on a brochure is a real problem because brochures are read indoors under overhead lighting, and gloss bounces that light straight back into the lens. Matte scatters it. The same code on the same stock will scan first time matte and fail repeatedly gloss.
• Keep the code off spot UV and foil. Both are shiny by design and both sit slightly proud of the paper.
• Use error correction Q or H. Brochures get folded, stuffed into bags, and rained on between the rack and the car.

Then test-scan the printed proof, not the PDF on your screen. A backlit screen flatters the pattern in a way paper never does. Ask for a folded dummy on the actual stock, scan it with two phones including one a few years old, under the overhead lighting the brochure will be read in, held at a slight angle rather than square on. Confirm the destination loads properly on mobile, not just that the code decodes.

Working out whether it did anything

The temptation is to check the numbers the week after the brochures ship and judge the code on that. Launch week measures the distribution event, not the format.

What you want is the shape of the curve over the whole shelf life. Brochure scans look nothing like a poster's spike and decay. They look like a low, persistent trickle with small bumps whenever a new batch goes into circulation. A trickle still running nine months later is the brochure doing its actual job: sitting in a rack, getting picked up by one person a week, and converting some of them.

Two habits make that readable. Use a separate tracked code per batch or per channel, so the conference handout, the reception rack, and the mail drop stay distinguishable rather than pooled into one meaningless total. And note the date each batch went into circulation, because in six months nobody will remember which run was which.

Be honest about the ceiling. A scan tells you someone lifted their phone while holding your leaflet. It does not tell you who they were or whether they booked anything, and one person scanning twice looks like two scans. What it answers well is comparative: which batch, which destination, which month. That is enough to decide what the next print run should do differently.

Before you send the file

Pick the one destination that the paper cannot supply and point the code at it directly. Make it dynamic so you can repoint it when the page moves. Put it on the back panel, bottom right, at least 3 cm square, clear of every fold and 8 mm inside the trim. Specify matte, solid ink, error correction Q or H. Then scan the physical proof before you approve the run, because that is the only test that counts.

You can build a tracked code for each batch in our generator and download it as print-ready SVG, then compare the batches later in the scan analytics.