Static vs Dynamic QR Codes
What the redirect actually buys you, measured on real encoded codes, and which payloads are worse off for it.
16 min readA QR menu is two things: a page holding your menu, and a code pointing at it. The code is free and takes ten seconds. If your menu is already on your website, that is the whole job, and the monthly fee you were about to pay is for the half you have done.
✓ Scan-tested: this code reads back correctly.
Contrast 21:1, Strong
Version 3 · 37 modules · print at least 14.8 mm wide
Search for a QR menu and every result is a platform with a monthly price. They are not selling you the QR code. A QR code is a public standard that any tool generates for nothing, this one included. What they sell is the menu behind it: an item editor, photos, categories, translations, and in the better ones, ordering and payment at the table.
Those are real products and worth the money if you want guests ordering without a server. But if what you wanted was for people to read the menu on their phone, and your menu already exists as a page on your own site, you need a code and nothing else. That is the part nobody selling a subscription is going to put on their landing page.
The code is the easy half. What decides whether a guest reads your menu or gives up is what opens when they scan, and the four common answers are not equal.
Opens instantly, reflows to the phone, and you can edit a price without touching the printed code. The link is short, so the code prints small enough for a table tent.
Somebody has to keep the page updated, and if the site goes down at Friday dinner service the menu goes with it.
The right answer for anyone who already has a website. This is a code, not a platform, and you do not need to buy one.
Zero work. The file you send to the printer is the file you upload.
It is the single worst thing to put behind a menu code. A PDF opens in a viewer, arrives zoomed out to fit a page designed for A4, and asks a person holding a phone in one hand to pinch and drag around a document. Prices in three-point type at that zoom are unreadable.
Avoid unless there is genuinely no alternative. If you must, export it at phone width rather than A4, so it opens legible.
Item editor, photos, categories, sometimes ordering and payments. Worth paying for if you want customers ordering from the table.
A monthly fee for hosting a page, and the code points at their domain, so leaving means reprinting every table tent. Several of them price per location.
Buy it for ordering and payments. Do not buy it just to have a QR code, which is the thing being sold hardest.
Free and quick. A Doc set to anyone-with-the-link opens on a phone and reflows better than a PDF does.
It looks like a Google Doc, which reads as unfinished on a table in a restaurant. Sharing settings default to restricted, which shows guests a permission wall.
Fine for a pop-up, a food truck or a specials board. Check it signed out before printing.
Pointing a menu code at a PDF is the most common mistake in this whole category, and it is invisible to the person who set it up. On the laptop where the code was made, the PDF opens crisp and full-screen. On the phone it is opened on, it arrives as a page laid out for A4 paper, scaled to fit a screen a fifth of that width, with body text at three or four points on screen.
The guest is now holding a phone in one hand, pinching to zoom with the other, and dragging around a document to find the starters. In a dark room. Some viewers reflow the text and most do not. A plain web page, even an ugly one, is readable the instant it loads, and that single difference decides whether the code was worth printing.
If a PDF genuinely is the only option, export it at phone width rather than A4, with type set for a screen. It will look wrong to you and right to everybody scanning it.
A table tent has a fixed footprint, so the length of the menu address decides how small the code can be printed and still read at arm’s length. Each row below was encoded and decoded when this page was built.
| Link form | Characters | Version | Modules | Print at least |
|---|---|---|---|---|
| Short path on your own domainhttps://example.com/menuThe shortest realistic destination, and the smallest printed code on this table. | 24 | 2 | 33 | 13.2 mm |
| A page deeper in the sitehttps://www.example.com/restaurant/food-and-drink/dinner-menuWhat a site's own structure usually produces. Every extra folder is modules on a table tent. | 61 | 4 | 41 | 16.4 mm |
| A PDF filehttps://www.example.com/uploads/2026/03/spring-dinner-menu-final-v3.pdfUpload paths carry dates and file names, and the file name is often the longest part. | 71 | 5 | 45 | 18 mm |
| A hosted platform linkhttps://menu.example-platform.com/r/9f2c1a9b/menu?loc=high-streetTheir domain, their identifier, and a location parameter. You do not control any of it. | 65 | 5 | 45 | 18 mm |
The dated upload path is the one to watch. A file called spring-dinner-menu-final-v3.pdf is longer than the entire address of a page on your own domain, and it also guarantees that next season’s menu lives somewhere else, which breaks every table tent you printed.
If your menu changes with the season and lives at a new address each time, a static code is the wrong tool: every change means new table tents. Either keep one permanent address and change what sits behind it, which is the simplest answer, or use a dynamic code and repoint the same printed square whenever the menu moves.
For a set of codes across several locations or tables, the bulk generator takes a spreadsheet column and prints the table number under each code.
Put your menu on a web page, copy its address, paste it into the generator on this page, and download the SVG for the printer. If the menu is already on your website you need nothing else: the code is free, it never expires, and there is no subscription attached to it.
The code is free, here and anywhere else. What the menu platforms charge for is hosting the menu, editing items and taking orders, which are real services worth paying for if you want them. If you already have a menu page or a PDF on your own site, you are being sold a subscription for a QR code you can generate in ten seconds.
Preferably not. A PDF opens zoomed out to fit an A4 page, so the guest pinches and drags to read prices set in small type, one-handed, in dim light. A plain web page reflows to the screen and is readable immediately. If a PDF is the only option, export it at phone width rather than paper width.
The editor shows a minimum width in millimetres for your exact link. Treat that as the floor and go larger, because a table tent is read at arm's length, often at an angle, and frequently through a laminate that reflects the ceiling lights straight back at the camera.
Yes, in two ways. Keep the link the same and change what is behind it, which is why a page on your own domain beats a dated PDF filename. Or use a dynamic code, where the printed symbol stays fixed and you repoint it whenever the menu moves, which suits seasonal menus that live at a new address each time.
A static code cannot stop working by itself, because the address is inside the pattern. What fails is the destination: an expired file, a moved page, a site outage. Print the menu address in small text under the code so a guest can type it, and keep a handful of paper menus behind the bar.
QRMakery builds the code on your own device, free, with no account and no expiry.
Menus on tables, sized for the distance somebody reads them from.
What the redirect actually buys you, measured on real encoded codes, and which payloads are worse off for it.
16 min readThe usable square inside a round sticker is 70% of its diameter. Measured minimum sizes for real links, against every common sticker size.
8 min readWhat each platform already ships, the measured cost of each payload type, and how to check an offline claim yourself.
26 min read