How to Create a QR Code Menu for Your Restaurant

A QR code menu is a printed code on your table that opens your menu in a guest's phone browser. No app, no download, no typing. The code itself is trivial to make — free generators produce one in seconds. What decides whether it works for the next three years is everything around it: what the code points at, how you print it, and whether you can change the menu afterwards without touching the print.

This guide walks the whole thing end to end.

Step 1: Decide what the QR code opens

This is the decision that everything else hangs on, and it is the one most restaurants get wrong on the first attempt.

You have three realistic options.

A PDF file. Fast to set up, painful for guests. Phones open PDFs in a viewer that ignores screen width, so your guest lands on a page-sized document they have to pinch and drag around in a dim room. See why a PDF link is the most common menu mistake for what actually goes wrong.

Your website's menu page. Works if — and only if — that page is genuinely mobile-first and you keep it current. In practice, restaurant menu pages are often the least maintained page on the site.

A dedicated digital menu. A page built for a phone held one-handed: readable type, sections you can jump between, a search box, prices that are easy to scan. This is what a guest expects in 2026.

Whichever you choose, the important question is the next one.

Step 2: Choose a QR code type you will not regret

There are two kinds, and the difference is not cosmetic.

A static QR code stores the destination inside the pattern itself. The URL literally is the black and white squares. Change the destination and you change the pattern — which means new codes, new printing, new table tents.

A dynamic QR code stores a short, permanent link that you control. The pattern never changes. Where that link sends people is a setting you can update whenever you like.

For a menu, this is not a close call. Menus change: seasonal dishes, supplier costs, a sold-out item, a new location. If your code is static, every one of those changes is a print run. We covered the full comparison in static vs dynamic QR codes.

Rule of thumb: if the thing behind the code will ever change, the code must be dynamic. A menu will always change.

Step 3: Get your existing menu in, without retyping it

Most restaurants already have a menu — usually a PDF from a designer, sometimes just a photo. You do not need to start over.

There are three ways in, in descending order of effort:

1. Import it. Upload the PDF or a photo and let it be read into sections, dishes, descriptions and prices. This takes minutes and you spend your time reviewing rather than typing.
2. Host the PDF as-is, wrapped in a mobile-friendly viewer that adds section tabs and search on top. You keep your designer's exact layout — useful if the menu's look is part of the brand.
3. Type it in by hand. Slow, but total control. Fine for a short drinks list.

Whichever route you take, check the prices yourself before publishing. This is the one field where an error is expensive and public.

Step 4: Structure the menu for a phone, not for paper

A paper menu is read at arm's length in one glance. A phone menu is read in a narrow column, often one-handed, often in low light. The same content needs different structure.

• Keep sections short. Six to ten items per section. If a section runs to twenty, split it.
• Lead with the dish name. Guests scan names, then decide whether to read the description.
• Put the price on the same line as the name. Not in a column that drifts away on a narrow screen.
• Write descriptions that earn their space. One line, concrete ingredients. "Slow-cooked lamb, smoked aubergine, mint yoghurt" beats "our chef's signature creation."
• Mark what is unavailable rather than deleting it. A guest who came for a dish should learn it is off today, not be quietly confused.

Photos are worth it for the dishes you want to sell, and only those. A menu where every item has a photo reads like a fast food app and slows the page down.

Step 5: Print the code so it actually scans

A QR code that needs three attempts costs you more goodwill than a slightly slower waiter. The rules are boring and they matter:

• Minimum 2 × 2 cm (0.8 × 0.8 in) for a code scanned from arm's length on a table. Bigger for a window or a wall.
• Keep the quiet zone — the blank margin around the code. Crowding it with a border or logo is the most common reason a code fails.
• Dark code on a light background. Inverted codes work on some phones and not others. It is not worth the risk.
• Matte, not gloss. Gloss lamination throws overhead light straight back into the camera.
• Test it before the print run. Old phone, new phone, dim light, at an angle.

Add one line of text under the code: "Scan for our menu." It sounds obvious. It measurably increases scans, because it tells guests the code is not a payment link or a survey.

The full detail is in QR code menu best practices.

Step 6: Put a plan behind the code

Once the codes are on the tables, the work shifts from setup to operation.

Decide who can change the menu. In a single site, that is you. Across several locations, you want roles — someone who can edit the lunch menu should not necessarily be able to delete it.

Watch the scans. Scan counts tell you when guests actually look at the menu, which is usually a spike as they sit down and a second, smaller one before dessert. That second spike is worth designing for.

Keep one thing permanent: the link. Everything else can change.

The mistakes that cost the most

After the code is printed, these are the expensive ones:

• A static code. Every menu change becomes a print job. This is the single most common and most avoidable mistake.
• Linking to a PDF. Works on your laptop, frustrating on a phone.
• A code with no fallback. Print a short, typeable URL under the code for the guest whose camera will not cooperate.
• A menu nobody updates. A digital menu showing last season's prices is worse than paper, because guests assume a screen is current.
• Removing paper entirely on day one. Keep a few printed copies. Some guests want them, and some phones are out of battery.

How long this actually takes

For a single restaurant with an existing PDF menu: about an hour to import and review, another hour to check the layout on a phone and order the table tents. The printing is the slow part.

The ongoing cost is where the design decision pays off. With a permanent link, changing a price is a two-minute job at any hour. With a static code, it is a purchase order.

---

Survenix turns a PDF, photo or hand-typed menu into a mobile digital menu behind one permanent QR code — change prices as often as you like, the printed code never changes. See the pricing or start a 7-day free trial.