123QR.net

Guide

How to create a QR code menu

Put your menu on a mobile-friendly web page or a clean PDF, generate a dynamic QR code that points at it, and print that code on table tents or stickers. Because the code is dynamic, you can update prices and dishes without ever reprinting.

Published 28 August 2026 by 123QR

Create a QR menu code

Step 1: choose a web page or a PDF

A web page (even a simple one) beats a PDF for most restaurants. It loads faster on mobile data, reflows to fit any screen without pinch-zooming, and you can edit text directly without re-exporting a file. A PDF menu, viewed on a phone, is usually a scaled-down image of a print layout — readable, but often requiring zoom and horizontal scrolling.

A PDF makes sense if you already have a polished print-design menu and don't want to rebuild it as a web page, or if the menu is long and works better as a structured, paginated document (a wine list, a large multi-course menu). If you go this route, at minimum check it renders sensibly on a phone screen before printing any codes.

Step 2: make it mobile-readable

  • Single column layout — no side-by-side columns that force horizontal scrolling on a phone.
  • Font size that doesn't require zooming; test on your own phone, not just a laptop preview.
  • Group items clearly with headings (starters, mains, desserts, drinks) so people can jump to a section.
  • Keep the file or page small — slow-loading menus lose people standing at a table waiting.
  • If using a PDF, export at a reasonable file size and check it opens directly in the phone's browser rather than forcing a download.

Step 3: generate the dynamic code

  1. 01

    Host the menu

    Publish the web page or upload the PDF somewhere with a stable URL.

  2. 02

    Create a code on 123QR

    Paste that URL as the destination and name the code for where it will physically live, e.g. "Menu — terrace tables".

  3. 03

    Download the QR image

    Export it at a size large enough for your intended print format, well above the minimum for table-distance scanning (see our size guide).

  4. 04

    Test before printing in volume

    Print one at final size, place it on an actual table, and scan it with a couple of phones from a normal seated distance.

Step 4: print and place

  • Table tents work well because they're at eye level and easy to reprint individually if a design changes.
  • Laminated cards survive spills better than paper, but check laminate glare doesn't wash out contrast under bright lights.
  • Leave the quiet zone (blank margin) around the code intact — don't crowd it with your logo or a border touching the pattern.
  • Place codes where people are already seated and have a moment to scan, not somewhere they'll be rushed past.

Step 5: update weekly

Because the code is dynamic, updating means editing the destination content, not reprinting the table tents. If your menu changes with the season or you run daily specials, update the underlying page or swap the PDF and the same printed code picks up the change automatically on the next scan.

Keep a simple routine: update prices and availability on a fixed day each week, and check the live page looks right on a phone straight after publishing, since typos are easier to miss in a quick edit than a full redesign.

Step 6: track scans

Scan analytics show you when the menu gets scanned (useful for spotting lunch vs dinner patterns), on what kind of device, and roughly where from if you have multiple locations sharing branding. It won't tell you what anyone ordered or whether they liked the menu — it only measures that the code was scanned, not what happened after.

If you run more than one location or seating area, use a separate code per area rather than one code for the whole restaurant. That's the only way to tell which physical placement is actually getting used.

Practical checklist

  • Menu hosted at a stable URL, readable on a phone without zooming
  • Dynamic code created and named for its physical location
  • Printed at or above the minimum size for table-scan distance
  • Quiet zone and contrast checked
  • Test-scanned with at least two phones before full print run
  • Weekly update routine agreed with whoever manages the menu
  • One code per table area if you want location-level scan data

Common questions

Should I use a web page or PDF for a QR menu?
A web page, in most cases — it's more reliably mobile-readable. A PDF is fine if you already have one and it's been checked to render well on a phone screen.
How often can I update the menu without reprinting?
As often as you like, since the printed code stays the same. Many restaurants update weekly for specials and immediately for price or availability changes.
Do I need a different code for each table?
No, one code per seating area (not per table) is usually enough to see which section of the restaurant gets more scans, without generating excessive codes to manage.
Can scan tracking tell me which dishes are popular?
No. It tells you the menu page was opened, not what someone read or ordered once there. For dish popularity, you'd need data from your point-of-sale system, not the QR code.

Keep reading

Print once. Change the destination anytime.

Create a free account, generate your code and edit where it points whenever you need to.

Create a QR menu code