Free Restaurant Menu QR Code Generator — Table Tents

Five options work. Your restaurant website's menu page (you control the design and updates). Your Google Business Profile menu (free, low-effort, integrates with Maps and Search results). A restaurant platform like Toast, Square, Lightspeed, Owner.com, or Slice (mobile-optimized by default, may include online ordering). A third-party menu builder like BentoBox or Popmenu (designer-quality with menu-specific features). Or a PDF hosted on your domain (works but reads badly on phones). Pick based on how often the menu changes and whether you want online ordering through the QR.

Dynamic, almost always. Restaurant menus change constantly — seasonal specials, price updates, platform migrations, brunch/dinner swaps, holiday hours. Each change breaks a static QR encoded to the old URL, which means reprinting every table tent, every window decal, every catering packet. A dynamic QR ($5/month Lite plan) survives every change — update the destination in the dashboard, every printed code keeps working.

The QR encodes a URL; what the URL does is up to the platform. If your menu URL is a Toast, Square, or Owner.com page with online ordering enabled, the diner's order goes from the phone to the kitchen printer the same as any online order. If the URL is a static menu page without ordering, the QR is view-only and the server still takes the order. Pick the URL based on whether you want the QR to be view-only or order-capable.

Generally no. PDFs zoom badly on phones, force pinch-and-pan navigation, and rarely reflow text for small screens. If your menu exists only as a PDF, either convert it to a web page (most restaurant platforms do this for you) or accept the friction. For high-volume use (table tents at a 60-cover restaurant), the friction adds up to lost orders. HTML menus convert 30–50% better than PDFs at the same content depth.

Two approaches. Put a separate 'Daily specials' QR on the table tent that points at a dedicated platform page you update each morning — the QR stays printed, the destination URL stays the same, only the content on that page changes. Or use a dynamic QR repointed to today's specials URL each morning — works the same but with stronger analytics. Either way, the daily-specials QR is distinct from the main-menu QR; combining them produces a navigation page that converts poorly.

Two patterns work. Separate QRs per language printed on the table tent with flag icons — the diner picks their language at scan-time, one tap to the right menu. Or a single QR pointing at a landing page with a language selector — adds one click of friction but reduces table-tent complexity. Tourist-heavy venues prefer the multi-QR pattern; less language-diverse venues prefer the selector. Both are common; pick based on your audience mix.

You can encode the platform menu URL — doordash.com/store/... or ubereats.com/store/... — and the QR works as expected. But these QRs typically serve a different purpose than dine-in menu QRs: they're for off-premises ordering. Most restaurants run a separate QR for delivery platforms (printed on takeout signage, gift cards, or business cards) distinct from the table-tent dine-in QR.

4 cm × 4 cm minimum for arm's-length scanning seated at the table (40–60 cm scan distance). 5–6 cm is comfortable and is what most successful table tents use. The 10:1 rule applies: code width ≥ scanning distance ÷ 10, with a 1.5× safety margin for dim restaurant lighting. Pair with explicit CTA copy ('Scan for menu') and a written URL as fallback for older phones.

With a static QR, no — the URL is encoded directly in the pattern, no analytics layer. With a dynamic QR ($5/month Lite plan), every scan is logged: timestamp, device type (iOS vs Android), city-level scan location, and referrer. This tells you peak scan times (which align with peak-dining-hour staffing decisions), which storefronts the QR works at, and whether the menu QR is actually replacing physical menu requests.

With a static QR, the new website URL is a new URL, and the static QR encoded to your old URL breaks immediately. Every table tent, window vinyl, and catering packet needs reprinting. With a dynamic QR ($5/month Lite plan), update the destination in your dashboard during the migration window, and the printed assets keep working through and after the migration. For any restaurant operating more than 3 months on a single menu URL, dynamic pays for itself the first time the URL changes.

Yes — static menu QRs are free forever. No signup, no credit card, no watermark, full color and logo customization, PNG download. SVG and PDF export, plus dynamic codes with scan tracking and survival through URL changes, start at $5/month (Lite plan). For most restaurants, the Lite plan pays for itself the first time the menu URL changes and you save the reprint cost on every table tent.