Three things every static menu QR gets wrong.
Most menu QR generators encode the Drive or Dropbox link directly into the modules. Print 80 table tents, swap to the winter menu in October, and every table tent points at the wrong file. The QR built here doesn't do that — it routes through a short link, the menu lives in your dashboard, and you can swap it any time the kitchen does.
Swap menus seasonally
The table tents stay on the tables. The menu file gets swapped in your dashboard whenever the kitchen changes — summer to autumn, lunch to dinner, weekday to weekend brunch. One edit, every QR points at the current menu.
Daily specials, weekly soup
The chef writes today's specials on a whiteboard out the back. Drop them into the same PDF every morning, save, every table tent in the room now serves the day's menu. The whiteboard becomes the source of truth; the table tents become eternal.
See which tables actually scan
Every scan logs a row. Print one QR slug per table (or per section) and the dashboard shows which placements pull and which sit unused. Window tables vs back room vs bar. Server-section A vs section B. Without analytics you're guessing; with them you redesign the room.
Three steps. Upload the menu or paste a link.
Upload the menu PDF straight from your device (up to 10MB), or paste a link if it's already hosted on Drive, Dropbox, or your own site. Either way the QR routes through a short link you can edit any time the kitchen changes.
Upload your menu (or paste a link)
Click Upload menu PDF and pick the file from your device — 10MB cap, PDF only. Already on Drive or Dropbox? Paste the public link into the field below. Direct PDF URLs also work.
Pick a short-link slug
Choose something memorable like linkedco.de/sundance, or hit the dice for a random one. Optionally pick a QR template and customise the design.
Print, place, swap when the kitchen does
Hit save. The QR is yours. Print table tents, lamination, whatever the room needs. When the menu changes, swap the file in the dashboard and the next guest who scans sees the new menu — no reprint.
Anywhere the menu changes more often than the table tents do.
A static QR menu works until the kitchen ships a new menu. The places this matters most are the rooms that change a menu more than once a year — and that's most of them.
Table tents that outlast the season
Print once per restaurant. Swap the linked menu for the autumn refresh, the lunch-vs-dinner split, the day's specials. The plastic tent stays where it is.
Drinks list + happy hour
Cocktail menu updates monthly, happy-hour pricing differs by night. One QR on the bar, swap the file Tuesday night for the Wednesday set. No reprint, no laminating.
In-room dining + minibar
Room-service menu in the binder, minibar list on the desk. Both QRs go to dynamic files — swap when the kitchen rotates, when prices change, when the minibar supplier swaps brands.
Menu that fits the truck
Window decal with the QR stays on the truck for years. Menu rotates with the festival, the location, the season. One scan, the current menu — no chalkboard rewriting.
Pastry case + counter
Today's bakes change every morning. Drop the day's PDF in the dashboard, the QR on the counter serves the morning's actual offerings, not yesterday's. Pair with the guest WiFi QR on the same card.
Per-event menus
One QR on the venue's table-tent template, the menu file swaps per booking. Wedding Saturday gets the wedding menu, corporate Monday gets the corporate one. The print doesn't have to know the difference.
Why static QR menus die the moment the kitchen changes.
A static QR menu encodes the menu URL directly — https://drive.google.com/file/d/abc123/view. Upload a new menu file, the URL changes, the print is dead. The dynamic version encodes a short link you control, which routes to whichever menu file is current in your dashboard.
Menu URL baked into the print
The file URL is encoded directly into the QR modules. Every generic "menu QR" generator that doesn't host a redirect does this. Fine for personal use; brittle for a working restaurant.
- Reprint every menu rotation
- Dies if you move or delete the file
- No scan analytics — total or per-table
- Long URL → denser, harder-to-scan QR
Menu link lives in your dashboard
The QR encodes a short link. The link routes to whichever menu file you've set as current. Autumn menu today, winter menu in October, daily specials swapped at 7am — same printed table tent, every time.
- Swap the menu file any time
- Move hosts without reprinting
- Per-scan analytics, per-table tracking
- Short URL → cleaner, sturdier QR
Things restaurants ask before they save.
Do I need a website or Google Drive to use this?+
No. The generator has an Upload menu PDF button at the top — pick the file from your device, 10MB cap, PDF only, no signup required. Already on Drive or Dropbox? Paste the link instead. After signing up the dashboard adds versioning, replace-in-place, and per-table analytics.
Can I have different menus for lunch and dinner on the same QR?+
Not on the same QR automatically. Two options: (a) put both menus in the same PDF, lunch on page 1, dinner on page 2 — one QR serves both. (b) Make two QRs, swap which one is on the table per service. Most restaurants pick option (a) because the print stays simple.
What about multi-language menus?+
Same answer — put the languages side by side in one PDF (English left, French right, Mandarin on a separate page block). The QR points at the multilingual document. Travel-heavy restaurants do this on every table tent.
How do guests open the menu — do they need an app?+
No app. Every modern iPhone and Android camera scans the QR natively and opens the URL in the system browser, which opens the PDF in the built-in viewer. Old phones (pre-2017) sometimes need a free QR reader app, but the camera-native flow covers ~98% of guests.
Can each table have its own QR so I can see scan counts per table?+
Yes — make one QR per table or section. They all point at the same menu file but each has its own short slug (linkedco.de/table-1, linkedco.de/table-2). The dashboard shows per-slug scan counts, so you can see which tables convert and which don't.
Can I serve allergen information through the QR?+
Yes — either bake it into the menu PDF (a final page with the allergen table) or use a second QR specifically for allergens. Some restaurants make the second QR per-dish so a guest scans the steak photo and sees ingredients + allergens for that dish only.
Will the QR keep working if I move my menu to a different host?+
Yes — that's the whole point. Move from Drive to Dropbox to your own site to your supplier's portal, the printed QR doesn't care. Update the destination URL in your dashboard, every scan from then on routes to the new host.
Can I brand the page — custom domain, my colours, my logo?+
The redirect is silent by default — guests scan and the PDF opens. If you want a branded landing page in between (with the venue logo, a reservations CTA, allergen icons), the lifetime tier lets you point a custom domain at it. menu.yourvenue.com/dinner reads better than linkedco.de/abc123.
Print the table tents once. Swap the menu as often as the kitchen does.
Free to start. Lifetime tier for your own domain, upload-from-dashboard, and unbranded redirect pages.
Get started free →