Open your own menu on your phone, standing outside the venue, on mobile data rather than the house Wi-Fi. If it is a PDF, you now know what the guest sees.
The file exists because it was made for the print run, so putting it on the site felt free. It is not. A print file and a web page have opposite requirements, and a PDF fails both the phone and the search engine.
Below are seven concrete consequences, ordered from the most expensive.
1. The guest has to zoom to read anything
A PDF has a fixed layout. Opened on a phone it renders as a whole A4 page shrunk to screen width — the type is then 3–4 pixels tall in real terms.
To read prices, the guest has to zoom in, pan right, pan down, zoom out to work out where they are, then zoom in again. On a three-page menu that is a dozen operations.
Three quarters of visits to restaurant websites come from phones. Which means this is the default experience of your menu.
2. Google does not tie PDF content to your site
The most expensive consequence, because it works quietly.
Search engines do index PDF files. But they treat them as separate documents rather than part of the venue's site, so dish names, ingredients and prices in such a file do almost nothing for your restaurant's visibility.
It matters for searches about specific dishes: "gluten-free ramen Berlin", "beef tartare near me", "vegan brunch Kreuzberg". These are very high-intent queries — somebody knows exactly what they want to eat. A 50-item menu is 50 such phrases. In a PDF, not one of them works.
3. The old version stays in circulation
A PDF can be downloaded, forwarded and saved. That sounds like an advantage until somebody sends friends a menu from a year ago.
Worse: old files stay indexed under their own addresses. menu-2024.pdf can sit in search results long after you uploaded menu-new-final.pdf. A guest opens whichever comes first and sees prices from before two increases.
4. You cannot switch off a single item
The fish is gone. On a digital menu you disable the item and that is that. In a PDF you have to find the source file, open it in a graphics program, delete the item, export and upload. Or — what actually happens — do nothing and explain at the table.
The same goes for the daily special, the seasonal offer and lunch. A whole class of changes that should take 10 seconds is impossible with a PDF — so it simply does not happen.
5. The menu does not work for an international guest
A second PDF in a second language is a second document to maintain and a guaranteed divergence within months. A third language is a third file.
In practice it ends with one English version, made once and never updated — the kind servers hand over "just in case" and are quietly embarrassed by. More on that in multilingual menus.
6. Allergens almost never fit
The duty to declare allergens covers every venue, and the list has to be available to the guest before ordering. On a menu designed for print, space is scarce, so allergens end up at best as numbers next to items and at worst nowhere.
This is not a matter of aesthetics but of a duty under Regulation 1169/2011. The rules allow electronic form — and there space costs nothing.
7. The file is heavy and slows the site down
A print-ready menu with graphics is often 8–20 MB. On LTE with one bar it downloads for a dozen seconds, and the guest sees nothing during that time — not even a progress bar, because the browser is waiting for the file.
On top of that, in many mobile browsers a PDF does not open in the window but lands in downloads. The guest has to leave the browser, find the file and open it in another app.
What to replace it with
The menu should be an ordinary HTML page you can scroll with a thumb. That is all. It does not have to be striking — it has to carry prices, be current, and read without zooming at 16 px and up.
This does not require rebuilding the site. It is enough for the menu to have its own address, pointed to by:
- the "Menu" button on the site, where the PDF link is today,
- the "Menu link" field in your Google Business Profile,
- the QR code on the table, if you use one,
- the link in your Instagram bio.
In WMenu the menu is exactly such a page: it opens with no app, shows current prices and photos, carries allergens at each item and a language switch, and you change it in the panel in seconds. More on the PDF menu alternative page.
If you already have a finished PDF and do not want to retype the menu by hand — we will move it across for you.
When a PDF does make sense
As an addition, not as the only version:
- to download and print for guests organising an event with you,
- as a banquet menu sent by email,
- as an internal print for the floor team.
In each of those cases the file supplements a normal menu page rather than replacing it.
Frequently asked questions
Is a PDF menu bad for SEO?
Less bad than useless: Google treats the file as a separate document and does not tie its content to the venue's site. Dish names and prices in a PDF do almost nothing for visibility in local results.
Can I keep the PDF next to a normal menu?
Yes, and that is a sensible setup — provided the page is the default version and the PDF sits beside it as "download to print". The other way round does not work.
How fast can a PDF be replaced with a menu page?
Retyping a 40–60 item menu is usually 1–2 hours of work. If you would rather not do it yourself, the menu can be moved across from the existing file.
Is a photo of the menu better than a PDF?
No, it is worse. A photo has the same drawbacks as a PDF, cannot be enlarged without going soft, and contains no readable text at all.
