QR code menu for restaurants: rebuild it at phone size

A guest sits down, aims the camera at the card on the table, and your menu opens as a PDF. It was laid out for 11x17 paper, two columns, a decorative face at nine points. On a six-inch screen that means pinch, zoom, lose the line, pinch again. Someone at the table gives up and asks for the printed one, which you printed anyway.

The file is not the problem. The mismatch between paper layout and phone screen is. A flipbook menu on i3Dify is the same content re-rendered for the screen it opens on, turned with the gesture people already use for magazines instead of the scroll they use for documents.

On a phone the flipbook drops the spread and shows one page

A QR-PDF hands the phone a print document and asks it to cope. The flipbook viewer detects the phone, drops the two-page spread, and frames a single page to fill the screen, turned with a swipe. It keeps two pages loaded either side of the one the guest is on, so the next turn is already there before the guest asks for it.

Then you pin the dishes. Drop a hotspot on a dish name and attach a note, and the guest taps it to read the tasting note or the allergens without leaving the page. A hotspot can open a URL instead, so the special of the week points at the booking page. Pin three to five, the ones you want ordered, not twenty. On the free plan the viewer carries a small i3Dify pill in the corner. Pro at 3 dollars a month removes it.

The QR encodes one URL, so a price change never costs a reprint

Printed menus fail at the seasonal rotation. Somebody moves eight prices, the whole run goes back to the printer, and the old cards stay on the tables until the box arrives. The QR you download from the share panel is a PNG at up to 1024 px pointing at one permanent address. Re-upload the PDF and the same code on the same table card serves the new menu that evening.

Print it at 2 cm square or larger with white space around it, then scan it yourself at a table at night, with the lights at service level. Below that size the code starts failing in low light, which is the exact condition it gets used in. Fix the print once and the menu is the only thing you ever change again.

The link outlives the table

A QR-PDF exists only where the card is. A menu at a permanent URL goes in your Google Business Profile, in the Instagram bio, and into the message a guest sends the friend who is picking the restaurant. Someone can open it the morning before a reservation and arrive already knowing what they want. The same address you print is the one you paste, so there is nothing to keep in sync.

Two languages are two projects and two codes

An in-menu language switcher asks the guest to choose after they have already scanned and waited. Build one project per language instead, put a hotspot on each cover linking to the other, and print both codes side by side with a label under each. The guest picks before scanning. Free gives you 3 projects and 50 MB, and a typical eight-page menu PDF is a few MB, so English, Spanish and the wine list all fit before you pay anything.

A flat PDF is still right in two rooms

A four-item counter cafe where nobody scans anything, and fine dining where the menu is a physical object the server hands over and a code on the table would break the room. Everywhere between those, the guest is reading on a phone whether the menu was designed for one or not.

A menu built at phone size gets read past the starters, and the code on the table stops being something you reprint. Change the prices, keep the QR. Start from the 3D restaurant menu template.