Restaurant menu design: make each choice easier

Arrange sections around the meal

For a sit-down dinner, try starters, mains, sides and desserts. A lunch counter may work better with complete meals first and optional extras next. A drinks-led venue may need beverages before food. These are starting points to test, not a universal eye-tracking rule.

Put comparable choices together: a guest deciding between a grilled and a braised dish should not have to search separate pages. Do not assume a “golden triangle” guarantees attention or sales. Watch a first-time reader use your actual menu and note where they hesitate.

Write descriptions that distinguish dishes

Original example, not an actual restaurant item: replace “Chef’s special chicken” with “Charcoal-grilled chicken, lemon yogurt and roasted carrots.” The second version explains preparation, sauce and accompaniment. If the dish is spicy, creamy or served cold, name that difference where it helps someone choose.

Avoid “best,” “famous” or “authentic” when a concrete detail does more work. Use the same structure across neighboring items so people can compare them. Leave room for special preparations and portion choices rather than burying them in a footnote.

Make prices and options unambiguous

Keep a price close to the dish it belongs to. Put the price of an extra beside that extra, and state what the base dish includes. If a dish has two sizes, name the sizes before their prices. Compare the final layout with what staff actually charge.

Example: “Noodles — regular 12 / large 16; add egg +2” tells a reader more than an isolated “from 12.” The numbers here are invented layout examples in one consistent currency, not a pricing recommendation or a SeEat menu.

Use hierarchy, contrast and space

Use section headings, then dish names, then supporting descriptions. Web headings help convey content structure.^[1] W3C’s web guidance sets minimum contrast at 4.5:1 for ordinary text and 3:1 for large text.^[2] These are web thresholds, not a guarantee that a printed board is readable from any distance.

On a phone, avoid squeezing a paper-style multi-column sheet into a narrow screen. Check long names and translations with the real text. On paper, test a printed copy under dining-room lighting. Keep an accessible alternative when a guest cannot comfortably read the chosen format.

Translate the decision, not just the name

Keep a recognizable original dish name when it matters, then explain the preparation in the reader’s language. A literal translation can hide what a guest needs to know. Ask a fluent reviewer who knows the food to check ambiguous terms.

Dietary information should reflect verified recipes. Do not infer it from a generated image. Invite guests to ask about ingredients and shared equipment; a label does not establish that a dish is safe for an allergy.

A practical workflow

1. Draft one section with names, distinguishing descriptions, prices and optional changes.
2. Ask a new reader to find a dish, compare it with another and explain the final price. Fix the point where they hesitate.
3. Review the menu on a phone and a printed copy, including your longest translated names, before publishing.

Frequently asked questions