Notes on Restaurant Menu Page Design

The menu page is typically the most visited page on a restaurant website. It's where guests confirm whether the food is what they're looking for, calibrate the price range, and decide if the occasion fits. It does a lot of work.

It's also the page where most restaurants put the least thought into structure. The gap between what a menu page does and what it could do — in terms of clarity, scannability, and guiding attention — is usually noticeable once you start looking.

What a guest is actually doing on your menu page

Guests don't read menus the way they read articles. They scan for signals: something that catches their attention, a price point that calibrates expectation, a section that matches their mood. They're not starting at the top and working through sequentially.

This means the structure of your menu page — what appears first, how sections are labeled, how long descriptions are — affects what guests notice. It's more of a UX problem than a design problem.

The PDF problem, and why it keeps happening

A PDF is the path of least resistance for most restaurants, and I understand why. The menu exists in a design file. Converting it takes seconds. It feels like the job is done. But a PDF has consistent problems: it doesn't display cleanly on mobile without zooming, it can't be read by Google, and it isn't accessible to screen reader users.

The counterargument — that an HTML menu is harder to update — is true if the site is built inflexibly. A well-built menu page can be updated by anyone who can edit a text document. The constraint is usually the initial setup, not the ongoing maintenance.

Giving context before the item list

A menu page that opens directly with a list of 40 items is asking guests to work harder than they need to. A brief introduction — the style of food, how the menu is structured, a note about sourcing if that's part of the identity — orients guests before they start scanning. It takes two or three sentences.

Section headings should be legible at a glance. Guests are pattern-matching against every menu they've ever read. Conventional labels ('Small Plates', 'Mains', 'Desserts') work because they're instantly interpretable. Creative alternatives can work too, but they need to be immediately clear — not clever in a way that requires a moment's thought.

Description length

Most restaurant menu descriptions are either absent entirely or too long. The useful range is roughly one to three lines — enough to establish the character of the dish and its key ingredients, not enough to read like a recipe. An item with an obvious name often needs only the key accompaniment and cooking method.

Price presentation

Research from Cornell found that removing currency symbols from menu prices is associated with higher average spend, likely because it reduces the salience of cost. Whether that's appropriate depends on context — it fits naturally in environments where guests aren't primarily cost-focused. In a casual setting, it can feel slightly off.

More broadly: right-aligning prices invites guests to compare vertically across the column. Embedding prices within descriptions shifts attention to the dish first. Neither is objectively correct — but the choice is worth making deliberately.