Menus and bookings
Digital menus for restaurants: is it worth dropping the PDF?
The difference between a PDF menu and a menu built as a page, what each one costs in lost guests and what to do if you only have the menu as a photo.
In short
- A PDF adds at least one step between a guest's curiosity and the decision to come and eat.
- A menu page reads on a phone without zooming, and that is where most people open it.
- Only content on a page can be read, understood and shown in searches.
- Prices and dishes change. A menu page changes in minutes; a PDF means redoing the file.
- Keep the PDF for printing and for anyone who asks, but do not make it the main path.
The menu is the most visited page on almost every restaurant website. It is where people decide whether they are coming or not. It is worth treating it as the most important page on the website, because it is.
What happens when someone opens a PDF on a phone#
- They tap "See the menu" and the phone starts downloading a file.
- The file opens in another app, outside the website.
- The text appears tiny, because the PDF was designed for A4.
- The person zooms in, drags sideways, loses the line, zooms in again.
- To get back to the website, they have to close the app and find the tab again.
None of these steps is fatal on its own. Together, they turn a simple question, what do they have, into a small chore.
A direct comparison#
| PDF menu | Digital menu page | |
|---|---|---|
| Opens immediately | No, it downloads first | Yes |
| Readable without zooming | Rarely | Yes |
| Updating a price | Redo and re-upload the file | Edit and save |
| Can show up in searches | Very limited | Yes, it is website content |
| Works with a screen reader | Depends on the file | Yes, if it is well built |
| Good for printing | Yes, that is what it is good at | Not without its own version |
Why this also matters for Google#
When someone searches for a specific dish in an area, the search engine needs to be able to read that dish somewhere. If your dishes live inside an image or a file, it is as if they were not written at all. Google is explicit about content written for people and easy to understand, and a text menu is exactly that.
There is a useful side effect: a menu page gives material for the snippets that appear in search results and in generated answers. A PDF gives very little.
What a menu page should look like#
- Organised by sections, with the sections reachable from the top.
- Dish name, short description and price, always in the same order.
- Clear marking of what is vegetarian, vegan or gluten-free.
- Allergen information within reach, even if it is not dish by dish.
- No hidden prices and no "price on request" for dishes on the menu.
- A visible booking button, because whoever is reading the menu is closest to deciding.
When a PDF still makes sense#
- A version for printing, for the table or the window.
- Very long wine lists, where the sheet helps to compare.
- Catering or group documents, which are proposals and not menus.
In these cases, keep the PDF as a secondary file and not as the main path. The everyday menu lives on a page.
If you only have photos of the menu#
- Type the dishes once, in a simple document, section by section.
- Check the prices with the kitchen before publishing, not after.
- Publish with the sections the restaurant actually uses, not the ones that look nice.
- Keep the document as the single source. From then on, updates always happen in the same place.
It is a tedious job, but you only do it once. After that, changing a price takes a minute.
Frequently asked questions
Should the QR code on the table open a PDF?
No. The QR code should open the menu page. Someone sitting at the table wants to read now, not download a file over the weak signal inside the restaurant.
What if I only have the menu as photos?
You can start there, but it is the worst of the options. A photo of the menu does not read well on a phone, cannot be read by screen readers and cannot be searched. The way forward is to type the dishes once and then keep them up to date.
Do I need to show allergens on the website menu?
Allergen information has to be available to guests. Publishing it on the website is the simplest way to always have it at hand and up to date. Check the wording with whoever handles food safety at your restaurant.
Should I put prices online?
Yes. A menu without prices makes people close the page and look for another restaurant. The fear of showing prices costs more bookings than the prices themselves.
Sources and method
How we wrote this
The comparison is based on how each format behaves on a phone and on how search engines treat page content compared with files. Google's guidance on helpful content and on snippets is linked in the sources.
What this guide does not answer
This guide does not measure how many guests are lost because of a PDF. I do not have that number and I would be wary of anyone who presented it without explaining how it was measured.
Sources
- Google Search Central, Creating helpful, reliable, people-first content (accessed on 27 September 2026)
- Google Search Central, Snippets and meta descriptions (accessed on 27 September 2026)
- Google Search Central, Image SEO best practices (accessed on 27 September 2026)
Content checked on 27 September 2026.