QR Codes for Restaurant Menus: A Practical Guide

Sizing, placement, lighting and the mistakes that cost restaurants covers. What to link to, why static codes have a catch, and how to test before printing table cards.

QR menus went from novelty to standard fixture in about eighteen months, and plenty of restaurants are still running the version they threw together in a hurry. The difference between a code that works and one that quietly annoys every third table comes down to a handful of decisions.

What to link to

This is the decision that matters most, and it's not really about QR codes.

Link to a fast, mobile-friendly web page. Not a PDF.

A PDF menu on a phone means pinching and zooming through a document laid out for A4 paper. It's genuinely unpleasant, and it's the single most common complaint about QR menus. A simple HTML page with readable text costs little to build and is dramatically better.

Some specifics worth getting right:

• Keep it under 1 MB. Restaurant Wi-Fi and rural mobile data are both unreliable. A menu that takes 15 seconds to load has already lost.
• No app download. No sign-up. No email capture before the menu. People want to know what the fish is. Putting a form in front of the menu converts frustration into a bad review.
• Make it a permanent URL. More on this below — it's the biggest trap.
• Test it on a cheap old Android phone, not just your iPhone.

The static code catch

A standard QR code — including the ones this tool makes — is static. The URL is encoded directly into the pattern. That has a real advantage: it works forever, with no third party involved, no subscription, and nothing that can break if a service shuts down.

But it means the destination cannot be changed after printing.

If you print restaurant.com/menu-spring-2026 on 200 table cards and then change the menu, you reprint everything. If your web host changes and the URL moves, every card is dead.

The fix costs nothing: encode a permanent URL that you control the redirect for.

Use yourrestaurant.com/menu and point it at whatever the current menu is. Change the menu weekly, seasonally, whenever — the printed code never changes, because it just points at a URL whose content you update.

Avoid encoding:

• Anything with a date or season in it
• A third-party link (Google Drive, Dropbox, a menu platform's URL) — you don't control it, and those services change link formats
• A URL with tracking parameters that might expire

If you genuinely need to re-point a code after printing, that's a dynamic QR code — a short link with a redirect you can edit. Those require an ongoing service. Owning yourrestaurant.com/menu and controlling the redirect yourself gives you the same benefit without the subscription.

Size and placement

Table cards and tent cards: 3–4 cm square. Scanned from around half a metre, so 10:1 says 5 cm — but table cards are usually picked up, closing the distance. 3 cm is a safe floor, 4 cm is comfortable.

Window or door decals: 10–15 cm. Read from the pavement, through glass.

Printed on the physical menu itself (for a wine list or allergen info): 2.5–3 cm.

Placement details that matter more than people expect:

• Keep the code off the table surface itself. Codes laminated flat to a table get covered by plates, glasses and elbows, and reflect overhead lighting straight into the camera.
• Angle matters. A tent card standing upright is much easier to scan than something lying flat, because the reader isn't fighting glare.
• Avoid gloss lamination. Matte finish scatters light; gloss creates a mirror. Under restaurant spotlights, gloss is a genuine failure mode.
• One code per table minimum. A party of six passing a single card around is a bad first impression.

Lighting

Restaurants are dark. This is the most underestimated factor.

Your code will be scanned in conditions far worse than the ones you design it in. Candlelight, dim spotlights, evening service with the lights down. Phone cameras compensate by raising ISO, which adds noise, which makes module edges harder to resolve.

Practical consequences:

• Go bigger than the minimum. Every millimetre helps in bad light.
• Maximum contrast. Pure black on pure white. Not a tasteful dark brown on cream. Brand consistency is not worth a menu nobody can read.
• Use error correction Q. Table cards get handled, spilled on and bent. More on levels.
• Test at dinner service, in the actual room, with the actual lighting.

Design mistakes that break codes

Removing the white margin. The quiet zone is functional, not decorative. Designers trim it to fit the card. It breaks scanning. Four modules of clear space on all sides, minimum.

Putting the code on a photograph or texture. The background must be plain and light. A code over a wood-grain image is a code that doesn't scan.

Inverting the colours. White code on a dark card looks sophisticated and fails on most phones — readers overwhelmingly expect dark modules on a light background. Our generator blocks this outright.

Stretching it. QR codes must stay square. A designer nudging a corner handle to make it fit is a very common and completely fatal error.

Printing from a low-resolution PNG. Get a vector SVG for anything going to a printer.

Add a Wi-Fi code while you're at it

If you offer guest Wi-Fi, put a Wi-Fi QR code on the same card. It saves your staff from reciting a password twenty times a shift, and it's the sort of small thing people notice favourably.

Put it on your guest network, never the main one that your card terminal and back-office machines sit on.

Accessibility and the law

A QR-only menu excludes people. Some customers have no smartphone, a dead battery, no data, or visual impairments that make phone menus difficult.

Keep printed menus available on request, and make sure staff offer them without making it awkward. In several jurisdictions, accessibility legislation makes this more than a courtesy — and either way, turning away a table because they can't use your menu is a poor trade.

Make sure the menu page itself works with a screen reader: real text, not an image of text.

Before you print

1. Encode the permanent URL — check for typos by scanning, not reading.
2. Generate at error correction Q, export SVG.
3. Print one card at final size, on the actual stock and finish.
4. Take it into the dining room during evening service.
5. Scan it with an iPhone and an older Android, sitting down, at a real table.
6. Confirm the page loads in under three seconds on mobile data with Wi-Fi off.

Then print the rest.

Make your menu code in the studio — it's free, and the live preview shows exactly how dense the code is before you commit to a print run.