OnlineQRCodeGenerator.com

Make a QR code for a PDF menu

The pattern: upload your menu PDF somewhere stable, encode that address in a QR code, print once. When the menu changes, replace the file at the same address — every printed code now serves the new menu. The code never changes; only what it points at does.

  1. 1

    Upload the PDF to a stable address

    Your own website is best (yoursite.com/menu.pdf). Cloud drives work if sharing is set to 'anyone with the link' — test in a private browser window to be sure there's no sign-in wall.

  2. 2

    Set sharing to anyone with the link

    The most common failure is a permission prompt after scanning. Your customers are anonymous; the file must be public.

  3. 3

    Paste the link here and download

    Generate the code, scan it with your phone, check the PDF opens quickly on mobile data — then print.

Try it now

Point a code at a hosted PDF, menu, manual or price list.

Fill in the fields to encode your own content

Waiting for content

Free, no sign-up, no watermark. Your code never leaves this browser.

The replacement trick

Print is permanent; menus aren't. If the code points at yoursite.com/menu.pdf, updating the menu means uploading a new file over the old one. Same for cloud drives that let you replace a file while keeping its share link. One discipline to keep: never change the file name or move the folder, or every table tent in the building breaks at once.

For seasonal menus, some restaurants point the code at a redirect (yoursite.com/menu) that they repoint to the current PDF — same idea, one more layer of flexibility.

PDF vs web menu

Honest advice: a mobile-friendly web page reads far better on a phone than a PDF — no pinch-zooming, faster loading, easier to update. Use the PDF when the printed design fidelity matters (a beautifully typeset menu) or when a webpage isn't an option. If you do use PDF, keep it under a couple of megabytes; your customers are on mobile data in a cellar restaurant.

Also export a text-accessible PDF where possible — it helps screen readers and search indexing alike.

Table codes done right

One code per venue pointing at the menu is standard. Going further — a different code per table, with the table number passed to an ordering page — is where QR dining gets interesting, but that's an ordering system, not a menu link. For the simple case, print at least 4–5 cm for across-the-table scanning, matte laminate, and test under your actual lighting.

Mistakes to avoid

  • Test the link signed out and on mobile data — permission walls and 20 MB files are the two killers.
  • Never rename or move the PDF after printing codes.
  • Don't laminate in gloss — glare defeats scanning under restaurant lighting.

Common questions

Can the PDF be stored inside the code?

No — a QR code holds a few kilobytes at most. The code always links out to a hosted file.

How do I update the menu without reprinting?

Replace the file at the same address. The code points at the address, not the file contents.

Google Drive or my own site?

Your own site is more durable. Drive works if sharing is public — verify in a private window.

What size should the table code be?

At least 4 cm for across-table distance; 3 cm if it's a card diners pick up.