A PDF QR is a link, not the file stuffed into the square
You cannot usefully encode a 12-page menu inside the QR pattern itself. The code would be unreadably dense. A PDF QR code is a URL QR aimed at a publicly shared file: Google Drive, Dropbox, your own website, or any CDN. The phone downloads or previews that file after the scan.
That design is a feature. Replace the PDF at the same URL when prices change, and every sticker already on the table updates. If you burn a file into a static pattern, you would reprint the whole restaurant.
How to make a QR code for a PDF that opens on phones
Upload the PDF to Drive or your site. In Drive, set the file to “Anyone with the link”. Use a direct or preview link, not a login wall. Paste that URL here, generate, and scan from a phone that is not logged into your Google account — that is the test that catches private files.
Keep the PDF lean. A 40 MB scan of a printed brochure crawls on 4G. Export from InDesign or Word at a web-reasonable size, with selectable text if you can. Phones handle multi-page PDFs well; they do not handle 200 dpi full-bleed product shots in one file.
When a PDF QR is the wrong tool
If you run a restaurant and want photos, veg filters, and daily specials, a live HTML menu (our Menu QR) beats a static PDF. If you need a single image, use the Image QR page. If you need a fillable form people submit, a Google Form URL is better than a printable PDF form.
Use a PDF QR when the artefact already exists as a PDF: a compliance manual, a rate card, a school circular, an AGM notice, a takeaway menu you already designed in Canva.
Drive “preview” vs download vs your own domain
Google Drive preview links open in a viewer; some Android browsers then ask to download. Hosting the PDF on your domain (yourbrand.in/menu.pdf) looks more trustworthy and avoids Google login quirks. Whatever you choose, never rotate the filename if you want old stickers to keep working — overwrite the file at the same path.