Restaurant Menu QR Code Generator
Turn your menu link into a QR code diners scan at the table. Update the menu anytime without reprinting a single card.
Printed above the code. Clear it to remove the line entirely.
Fill in the fields to generate your QR code
How to create a restaurant menu QR code
Publish your menu at a stable URL
Put the menu somewhere publicly reachable — a page on your restaurant site, a hosted PDF, or a document shared as "anyone with the link". Choose the address carefully, because that URL is what gets baked into the printed code and everything afterwards depends on it staying the same.
Paste the menu link
Enter the full address including https://, exactly as it appears in the browser bar. A link that only works when you are signed in will fail for diners, so open it once in a private window to confirm it loads for someone who has never visited your site.
Generate and scan it yourself
The code updates as you type. Scan it with your own phone on mobile data rather than the restaurant WiFi, which is the closest approximation of what a diner at the table actually experiences.
Download and print
Take the SVG for anything going to a printer and the PNG for screens or social posts. Print a single test copy at the real size first and check it scans from a seated position before ordering a full run of table tents.
How a menu QR code works
The code encodes a plain web address and nothing more. A diner points their camera at it, the phone recognises the link, and one tap opens your menu in the browser they already use. There is no app to install and no account to create on either side.
Everything needed to resolve the scan lives inside the image, so the code is self-contained. It does not route through a redirect service that could expire, and this tool records nothing when a code is scanned — there is no tracking layer between the diner and your menu.
The practical consequence is that the code and the menu are separate things. The image points at an address; whatever sits at that address is what diners see. That separation is what makes the next section the most useful property of the whole setup.
Update the menu without reprinting the code
As long as the URL stays identical, you can change the menu behind it as often as you like and every printed code keeps working. Reprice a dish, pull a sold-out special, add a new season's list — the table tents, window decals and packaging already in circulation all point at the current version the moment you publish it.
This is the single biggest operational advantage over printed cards, and it only holds if the address is treated as fixed. Redesigning the site and moving the menu from /menu to /our-menu breaks every code already printed, so decide on the URL before the first print run and leave it alone. If a move becomes unavoidable, set up a permanent redirect from the old address rather than letting it return a 404.
Keeping prices current matters more here than it does on paper, because diners assume a live page is accurate in a way they never assume of a laminated card. The same applies to allergen and dietary information: a web page can carry full allergen notes, vegetarian and vegan markers, and spice levels without the layout compromises that force those details off a printed menu.
Why a web page beats a PDF menu
A PDF works with this generator, and for a small restaurant it is a reasonable starting point. But a PDF opens as a fixed-width document on a phone, which means the diner has to pinch and zoom to read anything, then pan around to compare dishes. Files are often several megabytes, so on a patchy mobile connection at the table the wait is noticeable.
A mobile-friendly HTML page avoids all of that. Text reflows to the screen width, headings let people jump to a course, and the page is readable by screen readers — which matters both for accessibility obligations and for diners with low vision who would otherwise need to ask a member of staff to read the menu aloud.
There is a search benefit as well. Google can index the individual dishes, prices and descriptions on a real page, so the menu can rank for searches combining your restaurant name with "menu", and for dish-level queries in your area. A PDF is indexed far less effectively and rarely earns those results. If you have the option, publish the menu as a page and point the code there.
Where to use it
Table tents and tabletop stickers
A code at every table lets diners open the menu the moment they sit down, without waiting for a printed card to be cleared and brought over.
Window and door displays
Passers-by deciding whether to come in can check dishes and prices from the pavement, which turns a glance at the window into a table booked.
Takeaway packaging and delivery inserts
A code on the bag, box or receipt puts the full menu in front of someone who has already bought once, at the point where a repeat order is most likely.
Seasonal and daily specials
Because the printed code never changes, a specials board or seasonal menu can be swapped as often as the kitchen likes by editing the page behind the same URL.
Best practices
- Fix the menu URL before the first print run and never change it, since every printed code depends on that exact address.
- Publish the menu as a mobile-friendly web page rather than a PDF so it reflows, loads quickly and can be indexed.
- Print table-top codes at a minimum of 2 × 2 cm, and scale up window and poster codes for the longer scanning distance.
- Keep the quiet zone clear and use a dark code on a light background — low-contrast colour pairs fail first in dim restaurant lighting.
- Laminate or seal codes used on tables, as grease, spills and scuffing degrade scan reliability faster than anything else.
- Review prices, allergen notes and dietary markers on the linked page whenever the kitchen changes the menu.
Frequently asked questions
Your whole SEO stack, finally in one place
Search Console, GA4, site audits, keyword research and backlinks feed one AI that tells you what to fix and why — instead of five tools you stitch together yourself.