Guides

QR Code Best Practices: A Checklist Before You Print

Before printing a QR code, use a dynamic code, check the page on a phone, add a call to action, size it right and test on iPhone and Android. Full checklist.

By the myqr team · Updated · 7 min read

The short answer

  • Use a dynamic QR code for anything printed in volume, so you can change the destination without reprinting.
  • Put a short call to action next to the code and make sure the page it opens works well on a phone.
  • Give each placement its own code, and test a printed proof on both iPhone and Android before the full run.
  • Print a short URL under the code so people who can't scan can still get there.

The best QR codes are easy to notice, easy to scan and lead somewhere worth going. Before you print, check five things: the code can be changed later (use a dynamic code for anything printed in volume), the page it opens works well on a phone, there's a short call to action next to it, it's big and clear enough for the distance, and you've test-scanned a printed proof on both iPhone and Android.

This is the checklist we'd run through before sending any QR code to a printer. Each section explains one item, and there's a copyable version at the end.

Should you use a static or dynamic QR code for print?

Use a dynamic QR code for anything printed in volume or meant to last. A dynamic code holds a short link that redirects to your page, so you can change the destination after printing and see how many people scan it.

A static code stores the destination directly in the pattern. It never expires and needs no account, but if the URL changes, every printed copy points to the old one. That's a real risk for menus, flyers, packaging and signs, where reprinting is expensive.

Static codes are still the better choice for a few things:

  • A Wi-Fi card on your café counter (try the free Wi-Fi QR code generator)
  • A contact card that won't change
  • A link to your homepage that you'll never move

For the full comparison, see static vs dynamic QR codes.

Is your destination page ready for phones?

Almost everyone who scans your code will be on a phone, often on mobile data, so the page needs to load fast and be readable without zooming. Open the link on your own phone, away from Wi-Fi, and see how it feels.

Check that:

  • The page matches the promise. If the sign says "Scan for the menu," open the menu, not your homepage.
  • Text is readable without pinching. PDFs designed for paper are often hard to read on a phone. A simple web page is usually better.
  • The next step is obvious. If you want a booking, a sign-up or a purchase, that button should be near the top.
  • Nothing blocks the content. Large pop-ups and cookie walls are frustrating on a small screen.

What should the text next to a QR code say?

Tell people what they'll get when they scan. A bare QR code gives no reason to pull out a phone, while a short call to action turns it into an offer.

Good examples:

  • "Scan for the menu"
  • "Scan to book a viewing"
  • "Scan to see this week's specials"
  • "Scan to join the guest list"

Keep it to a few words, put it directly above or below the code, and make it large enough to read from where people will first notice the code. If the scan leads to a discount or something free, say so: people scan when there's a clear benefit.

Is the code big enough, with enough contrast and margin?

Size the code at about one tenth of the scanning distance: 2.5 cm (1 in) wide for something held in the hand, about 10 cm (4 in) for a poster read from 1 m (3 ft) away. Use a dark code on a light background, and leave a blank margin called the quiet zone (4 modules wide) on every side.

Common mistakes to check for in the final layout:

  • The code was shrunk to fit a tight design.
  • The quiet zone was cropped, or text sits right against the code.
  • The code sits on a photo or pattern instead of a solid light panel.
  • Light-on-dark or low-contrast brand colors were used.
  • A low-resolution PNG was scaled up. Use SVG for print.

Our QR code size guide has a full size chart for cards, flyers, posters and signs. If you're adding a logo, follow the rules in how to add a logo to a QR code.

Where should you place a QR code?

Put the code where people naturally stop, at a height they can reach comfortably with a phone, and where their phone has a signal. Scanning takes a few seconds of attention, so it works best when people are already waiting or browsing.

Good spots:

  • Where people wait: counters, checkout lines, waiting rooms, bus shelters, restaurant tables
  • Around eye level: not down by the floor or above a doorway
  • On flat, well-lit surfaces: away from glare, folds and curves

Places to avoid or rethink:

  • Moving vehicles and roadsides: nobody should scan while driving.
  • Spots with no signal: basements, parking garages and remote venues. If the page can't load, the code fails. Consider offering guest Wi-Fi nearby.
  • Behind reflective glass: test window displays in both daylight and evening.

Does each placement have its own code?

Give every placement its own code if you want to know what's working. If the window poster, the table tents and the flyers all share one code, you'll see a total but never know which one earned the scans.

With dynamic codes this is easy: create one code per spot, such as myqr.sh/menu-window and myqr.sh/menu-table, pointing to the same page. Tag them by campaign so you can still see the total. Our guide to tracking QR code scans explains how to read the results.

Have you test-scanned a printed proof?

Test a printed proof on both an iPhone and an Android phone before the full run. A code that scans from your screen can still fail on paper because of size, ink spread, glare or a cropped margin.

Here's a quick routine:

  1. Print the final design at 100% scale.
  2. Put it where it will actually go, or at the same distance and height.
  3. Scan it with the iPhone Camera app (it reads QR codes natively since iOS 11).
  4. Scan it with an Android phone, using the camera app or Google Lens.
  5. Confirm it opens the right page, and that the page loads on mobile data.

If you can, include an older phone in your test. Older cameras are less forgiving of small or low-contrast codes.

Do you have a plan for changes?

Decide now what happens when the destination changes, the promotion ends or the page moves. Printed codes often outlive the campaign they were made for.

With a dynamic code in myqr:

  • Changing the page takes effect immediately for every printed copy. See how to change a QR code after printing.
  • Time-limited offers can have an expiration date with a fallback URL, so late scanners land on your current offers instead of an error.
  • Check what happens when a plan ends. Dynamic codes depend on the service, and many providers switch codes off when you stop paying. On myqr, every code keeps redirecting if a Pro plan ends; codes beyond the 2 oldest become read-only until you resubscribe.

With a static code, the only plan is keeping the destination URL working for as long as the print is out there.

Can everyone use your QR code?

Not everyone can or wants to scan a QR code, so offer another way in. Print a short URL people can type, right under the code.

A short link works well for this. If your code points to myqr.sh/menu, print "or visit myqr.sh/menu" underneath. It's easy to read aloud and type, it goes to the same place as the code, and myqr counts typed visits separately as link clicks, so you can see how many people used it.

Other accessibility checks:

  • Make the call to action and short URL large enough to read at the scanning distance.
  • Don't put essential information only behind the code. A menu code should come with a few printed menus for people who ask.
  • When you use a QR code on a screen or in a PDF, give it alt text that says what it links to.

The pre-print QR code checklist

Copy this list into your print brief or project notes:

QR CODE PRE-PRINT CHECKLIST

Code
[ ] Dynamic code for anything printed in volume or long-lived
[ ] Static code only for content that will never change
[ ] Destination URL is final and correct (with UTMs if you use them)

Destination page
[ ] Loads quickly on mobile data
[ ] Readable on a phone without zooming
[ ] Matches what the call to action promises

Design
[ ] Call to action next to the code ("Scan for the menu")
[ ] Size is about 1/10 of the scanning distance
[ ] Dark code on a light background, good contrast
[ ] Quiet zone of 4 modules on every side, nothing cropped
[ ] Logo (if any) is centered and small, corner squares untouched
[ ] SVG file used for print

Placement
[ ] Around eye level, where people stop or wait
[ ] Flat, well lit, no glare
[ ] Phone signal or Wi-Fi available
[ ] One code per placement, named and tagged

Testing
[ ] Printed proof at 100% scale
[ ] Scanned on iPhone
[ ] Scanned on Android
[ ] Scanned from the real distance, in the real lighting

After printing
[ ] Plan for when the destination changes or the offer ends
[ ] Short URL printed under the code for people who can't scan
[ ] Analytics checked after the first week

Frequently asked questions

Where is the best place to put a QR code on a flyer?

Near the bottom or in a corner where it won't be folded, with the call to action right next to it. Keep it on a plain light area, not over a photo.

Should a QR code go to my homepage?

Usually not. Send people to the specific page the call to action promises, such as the menu, the booking form or the offer, so they don't have to search for it.

Is it fine to use the same QR code on all my materials?

It works, but you lose the ability to see which material gets scanned. One code per placement, all pointing to the same page, gives you the same experience plus useful data.

How long should I test a QR code before printing?

A few minutes is enough: scan a printed proof at full size with an iPhone and an Android phone, from the real distance and in the real lighting, and confirm the right page opens.