PDF menus vs. menus on the page

Of the 76 menus we could detect in our 2026 benchmark, 29.9% of analysed sites involved a PDF and only 7.9% of found menus were clean, structured HTML. A PDF is not automatically wrong — but the trade-offs are real.

What the benchmark found

  • Structured HTML7.9% · n=6
  • PDF46.1% · n=35
  • On the page, unstructured42.1% · n=32
  • Mixed (HTML + PDF)3.9% · n=3
n=76

The trade-offs

PDF · in favour

  • — Matches the printed menu exactly, including layout and typography.
  • — One file to update when the kitchen changes something.
  • — Easy to hand to a designer or a printer.

PDF · against

  • — Downloads and pinch-zoom on a phone — friction exactly where menu-reading happens.
  • — Largely invisible to search engines: the dishes are not indexed.
  • — Hard for assistive technology to read.
  • — Goes stale quietly, because updating it is a re-export.

A reasonable rule

Put the menu on the page as text. Offer the PDF as a download for people who want to print it. That keeps the printed-menu fidelity without making it the only way in.

How does your restaurant compare?

Enter your website. Restoire scores it on the same signals and shows a redesigned version built from your real menu, photos and brand.

No sign-up required. Your current website stays unchanged.

Based on Restoire's 2026 benchmark of 127 restaurant websites we could reach and fully analyse (2026-08-29). Detection is automatic, so a missing signal is not proof of absence. Read the full methodology →

Source: Restoire Restaurant Website Benchmark, 2026-08-29, n = 127 analysed websites. Restoire