How to Convert a PDF Menu into a QR Menu (Without Retyping Everything)
The Duckhub team builds AI-powered QR menu and online ordering software used by cafes, bars, and restaurants. We write practical guides based on what we see working across thousands of published menus.
To convert a PDF menu into a QR menu, you have two options: generate a QR code that links directly to the PDF file (fast but clumsy for guests), or convert the PDF’s content into a structured web menu and point the QR code at that. The second option takes about 15 minutes now that AI can extract dishes and prices from the file automatically.
TL;DR
- A QR code pointing at a PDF works, but guests get a slow download and a pinch-zoom desktop layout on a phone screen.
- The better conversion extracts your PDF’s content into a real mobile menu page. AI does the retyping: upload the file, review, publish.
- Keep the QR code’s URL permanent so a menu change never means reprinting table cards.
- PDFs are nearly invisible to local search and AI answer engines; a structured web menu is indexable.
Can you just put a PDF menu behind a QR code?
Yes. Upload the PDF anywhere public (your website, Google Drive with public access, a file host), copy the link, and paste it into any QR code generator. Two minutes, zero cost, and it is genuinely better than having no QR option at all.
The problems show up at the table. A multi-megabyte PDF loads slowly on cellular, opens as a desktop-sized page that guests pinch and drag, and often downloads into the phone’s file storage instead of just opening. Every price change means editing the source file, re-exporting, and re-uploading, and if the file URL changes in the process, every printed code goes stale. It solves “we need a QR code” without solving “guests need a usable mobile menu.”
Treat the PDF-link route as a stopgap: fine for tonight, wrong for the season.
Why convert the PDF into a real web menu instead?
Because the PDF format fights the phone. A structured web menu is built for the screen guests actually use: it loads in a second, scrolls by category, shows photos per dish, switches languages, and updates in real time. The PDF was designed for print; the QR code’s whole job is to reach a phone.
| QR → PDF file | QR → structured web menu | |
|---|---|---|
| Load on mobile data | 5–15 s for a heavy file | Under 2 s |
| Reading experience | Pinch-zoom a print layout | Native mobile scrolling |
| Update a price | Re-export and re-upload the file | Edit in a dashboard, live instantly |
| Mark a dish sold out mid-service | No | Yes |
| Photos, translations, ordering | No | Yes |
| Visible to Google and AI assistants | Poorly (flat file) | Yes (indexable HTML) |
| Setup time | ~2 minutes | ~15 minutes with AI extraction |
The last row used to be the excuse: converting meant retyping the whole menu. That part is now automated.
How to convert a PDF menu with AI (step by step)
The conversion is mostly review work now, because AI reads the PDF for you. Upload the file, let the extraction run, check prices, publish. Here is the full sequence with Duckhub as the example platform:
- Create a free account at Duckhub (the Egg plan is free and needs no card).
- Hand over the PDF. Two routes: use Duckhub’s free menu migration (upload the file and the menu is set up for you), or connect ChatGPT or Claude to your account and upload the PDF in chat. Duck Hub MCP allows ChatGPT, Claude and other AI assistants to create a complete restaurant menu directly inside Duck Hub, so a prompt like “Extract every category, dish, price, and description from this PDF and build my menu” does the data entry as real menu items.
- Review the extraction. Check every price line by line: optical extraction is good but not perfect, and a dropped digit matters. Verify category grouping and fix dish names the layout mangled.
- Add what the PDF never had. Photos, allergen notes, a second language. This is where the converted menu stops being a copy and starts being an upgrade; the AI menu workflow can generate descriptions and translations in the same conversation.
- Publish and point your QR code at it. Publishing gives you a permanent URL (
yourvenue.duck-hub.com). Generate table QR codes in the dashboard, or repoint your existing dynamic codes. Print once; the URL never changes again.
If your PDF is a scan (an image, not selectable text), the AI route still works: assistants read menu photos too. Quality of the source affects review time, not feasibility.
What happens to your old printed QR codes?
If your existing printed codes point at a file URL, they will eventually break; if they point at a page you control, you can repoint them. This is the moment to fix the architecture: the printed code should encode a permanent menu URL, and all future changes should happen behind it.
Practically: codes that encode restaurant.com/menu.pdf cannot be saved once that file moves, so plan one final reprint to the new menu URL. Codes generated through a dynamic QR service can be redirected to the new menu without reprinting. And codes generated by the menu platform itself are permanent by design. Print-quality rules (size, contrast, quiet zone) are covered in our guide to making a QR code menu.
Does a web menu really matter for search and AI visibility?
Yes, and the gap is widening. A PDF is a flat file: search engines index it weakly, and AI assistants answering “what’s on the menu at [your venue]” or “best pasta near me” cannot reliably read prices and dishes out of it. A structured web menu is regular HTML that Google, ChatGPT, Perplexity, and other engines can crawl, quote, and recommend.
This matters because discovery is shifting toward AI answers. Restaurant operators already feel the platform shift: the National Restaurant Association’s 2026 State of the Restaurant Industry reports 26% of operators using AI-related tools in their own operations, and the same shift is happening on the guest side, where menus locked in PDFs simply do not surface. Converting the file is a guest-experience fix today and a discoverability fix for the next few years.
Frequently asked questions
How long does it take to convert a PDF menu to a QR menu?
About 15 minutes for a typical 40-to-60-item menu using AI extraction: a couple of minutes for the upload and automatic extraction, and the rest for reviewing prices and publishing. The manual alternative, retyping the same menu into software, takes several hours, which is exactly the step AI removed.
Is converting a PDF menu free?
Yes. Free AI assistants can extract the content, and a free menu platform plan can host the result: Duckhub’s Egg plan includes 70 products, 10 categories, 30 QR table codes, and no card requirement. Duckhub also migrates existing PDF menus free of charge on request. Paid plans only enter when you want ordering or built-in AI features.
What if my PDF menu is a scanned image?
It still converts. AI assistants read menu photos and scans, not just text PDFs; extraction quality depends on how legible the scan is. Expect a bit more review time on prices and unusual dish names. A phone photo of a physical menu works the same way if you have no digital file at all.
Can I keep the PDF for printing and still have a QR menu?
Yes, and it is a common setup: the structured web menu serves the QR codes and stays current, while the PDF remains your print master. Just fix one direction of truth: update the digital menu first, then regenerate print from it, so the table QR never shows stale prices.
Should the QR code open the menu or my website homepage?
The menu, directly. A guest scanning at the table wants dishes and prices in one tap; routing through a homepage adds a click and a decision. Put the website link inside the menu page footer for the guests who want opening hours or booking.
Have a PDF menu right now? Upload it to Duckhub and get a mobile QR menu on the free plan, or let ChatGPT or Claude do the conversion by chat. 0% commission, migration included.