A menu is one of the few documents that changes on a schedule and is also, physically, glued to furniture. The QR code on the table was printed once — twenty tables, laminated, done. Then the fish is off, the supplier puts the coffee up forty cents, and the Sunday brunch card needs a paragraph. The question isn’t how to make a menu page; anyone can make a menu page in an afternoon. It’s whether next Tuesday’s edit costs you an upload or a reprint. That comes down to a single property of wherever you put it: does the address survive the next version of the file?
Try it now
Drop a file — get a private link in seconds. No sign-up.
Drop an HTML file or ZIP bundle, or click to choose.
Single file or ZIP. Max 3 MB.
Up to 3 MB, link self-destructs after 7 days. Sign up free to keep links forever, password-protect them, and store more.
Upload the menu as a self-contained web page — one HTML file, or a zip if there are photographs of the dishes alongside it — and you get a link ending in 32 random characters. Generate the QR code from that link, print it, and stick it on the tables. Nothing about that first step is unusual; the part that matters comes later.
When something changes, you replace the file at the same address instead of publishing a new page. The link doesn’t move, so every sticker already on a table, every code on the window and the takeaway flyer keeps working and starts showing the new prices. That is the whole reason to care where a menu lives: the alternative is a host that mints a fresh URL on each upload, and each of those uploads quietly invalidates a print run you already paid for.
Two settings are worth getting right before the print run rather than after. First, expiry: a menu is meant to sit there indefinitely, so it needs to be one of your always-on links — a free account keeps one such link alongside its seven-day default, and Solo and Studio let you set “never” on as many as you like. Second, reach: pages here are unguessable and carry a noindex tag by default, which is right for most documents and is a decision worth making deliberately for a menu, since a restaurant usually does want to be findable. A registered account can opt a page in to being searchable — one page on Free, five on Solo, unlimited on Studio — so the menu can be the one you let out.
Yes, provided the code points at a link whose address doesn’t change when the file does. Replace the document in place and every printed code follows automatically, because the code never encoded the menu — it encoded the address. Where this goes wrong is with hosts that treat each upload as a new page: the old code still resolves, just to last month’s prices, which is worse than a dead link because nobody notices.
A self-contained web page: one HTML file, or a zip containing the page plus its images. A word-processor document or a design-tool export isn’t served directly, so there’s an export step at the beginning. In practice most people have an AI build the page from the text and the photographs, which is a few minutes once and then a few seconds per edit afterwards.
For a restaurant, usually findable — a menu is marketing. Pages here are unguessable and no-indexed by default, so being searchable is something you switch on for that page rather than something you get by accident. The quota is one searchable page on a free account, five on Solo and unlimited on Studio. The default matters for the other documents a small business ends up hosting — the staff rota, the supplier list, next season’s prices — which should stay off search while the menu is on it.
No. The code opens the page in whatever browser is on their phone. It’s worth testing the page on a real phone on mobile data before printing, because a menu is read one-handed, at a table, often by someone whose reading glasses are at home — the type size and the tap targets carry more weight here than the design does.
A free account covers one permanently-online page within a 10 MB total budget, which is enough for a text menu with a few compressed photographs. The reasons to move up are quantity and control: Solo and Studio let you set “never expires” on any number of pages, raise the space, and show you the detailed view figures. A single café with a single menu can sit on the free tier indefinitely; a group with six sites and a changing specials card will want the paid one.
Publish them as separate pages, each with its own link and its own QR code, and file them under one project so they stay grouped in the dashboard. Separate links are also what lets you see which one is actually being scanned — a specials card that nobody opens is telling you something about where the code is placed.
They stop resolving to a page. That’s worth planning for the same way you’d plan the print run: if the codes are going onto something expensive and long-lived, keep the link always-on and replace its contents rather than deleting and re-creating it. Deleting a document frees the address for good; the sticker on the table has no way to know.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.