Why most restaurants do this now
QR code menus went from a pandemic workaround to the default for a simple reason: printing a new paper menu every time a price or dish changes costs money and time, and a code pointed at a webpage costs neither. The code on the table never has to change — only the page it points to does.
The one decision that matters most: what you're linking to
This is where most setups go wrong before the QR code is even generated. People assume a menu that changes daily needs a "dynamic" QR code that can be edited after printing. It doesn't. You need a stable menu page URL that never changes, with menu content on that page you can update anytime. The code stays static and permanent; the page behind it is what you keep current.
In practice, that menu page can be:
- A simple webpage you or your web host controls — the most flexible option, easy to update text, prices, and photos.
- A hosted PDF (on your own site, Google Drive, or Dropbox with a public link) — fast to set up, but a pain to edit and often zooms awkwardly on phones.
- A published Google Doc or Google Site — free, decent for editing, but less control over how it looks.
Whichever you choose, the URL needs to be one you won't need to change. If you ever switch menu platforms, set up a redirect from the old URL to the new one rather than reprinting every table tent — see our static vs. dynamic QR code guide for exactly why that distinction matters.
Generating and sizing the code
- Get your final menu URL first. Don't generate the code against a placeholder page — test the real link.
- Use the standard generator with the URL type selected, paste your menu page link, and generate.
- Size it for scan distance. A code sitting on a table someone scans from 12-18 inches away should print at least 1 inch (2.5cm) square. A code on a window decal scanned from across a sidewalk needs to be considerably larger — the rule of thumb is the code should be roughly 1/10th the expected scan distance.
- Keep contrast high. Dark code on a light background scans far more reliably than the reverse or than low-contrast color pairs. If you're branding it to match your restaurant's palette, test the actual printed contrast before committing to a full print run.
Branding it without breaking it
Adding your logo to the center of the code is a nice touch for table tents, menus, and receipts — QR codes have built-in error correction specifically so a logo overlay in the center doesn't stop them from scanning. The logo generator on this site handles that placement automatically. The one thing to avoid is covering more than about 25-30% of the code's total area; past that, even the error correction can't compensate.
Multiple tables, multiple locations
If every table needs its own printed tent, or you're rolling this out across several locations, generating codes one at a time gets tedious fast. The bulk generator takes a list of links — one per table or per location — and outputs every code as a zip file in one pass, which is the difference between a five-minute job and an hour of repetitive clicking.
Print a test copy first. Before committing to a full run of table tents, print one at actual size on the actual paper stock, set it on a table under your restaurant's real lighting, and scan it with two or three different phones. Screen previews lie about print contrast and size more often than people expect.
Mistakes that leave codes unscanned
- No backup. Always print the plain URL in small text under the code. Some customers won't or can't scan — older phones, camera issues, or people who just prefer typing a link.
- No quiet zone. The blank margin around a QR code isn't decorative — it's required for the scanner to detect where the pattern starts and stops. Don't crop it tight against other design elements.
- Testing on a monitor, not in print. A code that scans fine on a laptop screen can fail on glossy, laminated table-tent paper due to glare.
- Linking to a PDF that doesn't render well on mobile. If most of your traffic is phones, test the actual mobile rendering of whatever the code points to, not just the desktop view.
Frequently asked questions
Should I use a dynamic QR code since my menu changes seasonally?
No — a seasonal menu is exactly the case a static code handles well. Keep the same menu page URL and update the content on that page each season. The printed code never needs to change.
What size should the code be for a table tent vs. a window sticker?
A rough rule: the code should be about 1/10th the distance it'll typically be scanned from. A table tent scanned from a foot away needs roughly 1 inch; a window decal scanned from several feet away needs to be several inches across.
Can I put my restaurant's logo in the middle of the code?
Yes, as long as it doesn't cover more than roughly a quarter to a third of the code's area. QR codes have built-in error correction that tolerates a center overlay up to that point without breaking the scan.
Does the menu page need to be mobile-optimized?
Yes — almost everyone scanning a table QR code is on a phone. Test the actual mobile view of whatever page or PDF you're linking to before printing anything.