QR menus for restaurants: the version that does not annoy people

The QR menu has a bad reputation it mostly earned. Someone sits down, scans, waits, gets a PDF, pinches to read a starter, loses their place, and asks for a paper menu.

Four things cause that, and none of them are the QR code.

The PDF

A PDF is a document laid out for A4. On a phone it opens in a viewer with its own controls, at a zoom level chosen by the viewer rather than by you, and it does not reflow. Every pinch is a person deciding this was a mistake.

An HTML page that reflows to the screen — headings, sections, prices in a readable size — is not a technical achievement in 2026. If your designer only produces a PDF, the answer is a page that presents the same content, with the PDF as a download link for anyone who wants it.

The speed

The scan happens in a dim room, often on hotel or mobile data, on a phone that is not new. A menu page carrying a hero video, three web fonts and an analytics stack takes several seconds to become readable, and several seconds at a table feels like a minute.

Aim for a page that shows text almost immediately. Photographs can load after the words.

The size and the placement

Placement	Read from	Code size	Format
Table card, tent card	Arm's length	2–3 cm	SVG
Menu corner, coaster	Arm's length	2–3 cm	SVG
Window sticker	1–2 m	8–15 cm	SVG
A-board on the pavement	2–3 m	20–30 cm	SVG

A workable rule of thumb is one centimetre of code per ten centimetres of reading distance, then round up. Print vector; a PNG enlarged to a window sticker is a soft-edged code that fails in sunlight.

Keep clear space around the code, and keep the code dark on a light background. Reversed codes — light on dark — are the single most common failure in restaurant print, because a phone camera has to work harder for them exactly when the light is worst.

The link that dies

This is the expensive one. A code encoding yourrestaurant.com/menu-autumn-2026.pdf is fine until the winter menu replaces it, at which point every printed card points at a dead file.

Encode a short link instead. The card says gc.mw/menu; the link points at whatever the current menu is. Changing the season is one edit and the redirect updates within about a second, because editing a link invalidates its cached entry everywhere.

1. 1

   Create one link per menu, with an alias you can say out loud

   Custom aliases on Pro: gc.mw/menu, gc.mw/drinks, gc.mw/specials. Short aliases produce simpler codes, which print smaller and scan faster.

2. 2

   Download the SVG for print

   Add .svg to the link. The .qr suffix gives a PNG for your website and social posts.

3. 3

   Print, laminate matt, and scan one from every table

   Corner tables, the dim ones, the one by the window at noon. Ten scans finds every problem you will otherwise hear about from a customer.

4. 4

   Repoint at each menu change

   The cards never change again. Only the destination does.

What you learn from the numbers

Scans through a QR are counted separately from ordinary clicks, so a menu link on both a table card and your Instagram bio gives you two readable numbers rather than one confusing one.

The hour breakdown is the useful one here. It shows when people actually look at the menu, which is rarely when you think — a drinks link that peaks at 9pm rather than 7pm is telling you where the second decision of the evening happens. The country and city breakdown separates regulars from tourists in a way that a booking system does not.

Keep one thing in proportion: a QR menu is a convenience, not a replacement. Print a few paper menus. The customer who asks for one is not a failure of your technology stack, and handing them one graciously costs nothing.

For sizing, colour and the print-ready formats, see QR codes — the same codes, the same editable destination, whether they end up on a table card or a bus shelter.