The difference a guest notices
An HTML menu is part of the page: its text can adapt to the screen, and category links can take a guest directly to breakfast, seafood or wine. A PDF is a document with a fixed page layout. A small printed menu may work well; a dense multi-column design often needs zooming.
Try both on the phone your guests actually use. Check the smallest price text, long dish descriptions and whether returning to the reservation action is straightforward.
Updating dishes and prices
HTML content can be managed separately from the layout when the site has a suitable editing workflow. A PDF usually needs an updated document and a replacement file. Neither format guarantees correct information: someone must own the update process.
Avoid maintaining two conflicting menus. If both are public, update them together and agree which version is authoritative. For seasonal changes, record the date and confirm unavailable items with the restaurant.
Accessibility and search visibility
HTML supports headings, lists and selectable text that can reflow as a guest changes text size. An accessible PDF also needs care: real text, logical reading order and appropriate document structure. A photographed menu inside a PDF is harder to read and maintain.
PDF files can be indexed by Google. The claim that every PDF menu is invisible to search is incorrect. HTML gives you more direct control over surrounding page information, internal links and the path back to the restaurant’s contact details; it does not guarantee a ranking improvement.
A practical comparison
For a frequently changing menu, favour a structured HTML menu with clear category headings and consistent prices. For a carefully designed print menu, keep an optional downloadable PDF. When updates are infrequent and a short PDF reads comfortably on a phone, improving that document may be a sensible first step.
- HTML: responsive reading, category navigation and a visible reservation route.
- PDF: a portable document that preserves the print layout.
- Both: need verified prices, suitable accessibility and a named person to keep them current.
What to request from your designer
Ask how a price change is made, who approves the menu, how categories work on a phone and what happens to the old PDF link. Request a working demonstration with your real menu, rather than a screenshot of a generic list.
For a migration, keep a redirect for the old menu URL where appropriate. Check that visitors arriving from Google Maps or an old email reach the current menu. Include phone, address and a clear route to reserve near the menu.
Where Table & Host fits
Our standard restaurant website scope includes menu setup using the agreed material. Optional Website Care covers up to four small content requests per month, including menu and price edits. A new ordering system or custom menu management application is a separate project.
Sources and further reading
Written by Kai Chen, founder of Table & Host. This guide explains website decisions; the restaurant and any booking provider should confirm their operational information.