Menu design for reading, not for framing

Menu design is the set of decisions that turns a list of dishes into something a guest can read, understand and order from in a few minutes, often in dim light, often while talking. It is easy to treat a menu as a piece of branding, a handsome object that matches the room. It is more useful to treat it as the venue's most important sales tool, read by every guest at every table, and judged by one question: can people find what they want and order it with confidence?

Many menus fail that test while looking beautiful. Thin type on textured card, long paragraphs in capitals, prices tucked into the margins and sections in an order that only makes sense to the kitchen all look fine on a designer's screen in daylight. At a corner table at nine o'clock, they are hard work. Guests who struggle to read a menu tend to fall back on what they know, ask the server to explain, or order less.

This guide sets out menu design for reading rather than framing. It covers what the menu is for, typography that works in low light, layout in the order guests eat, how many dishes to offer, menu descriptions that sell without overselling, prices and menu placement, highlighting dishes on purpose, allergens, photographs, and the separate problem of the digital menu. It ends with how to test a menu in the room and measure whether a change worked.

A menu has three jobs. It tells guests what they can order, it helps them choose, and it steers some of their choices towards the dishes the venue most wants to sell. All three depend on the menu being easy to read. A guest cannot be steered by a menu they are squinting at.

The first job is information: what each dish is, what it costs, what it contains and whether it suits the guest's diet. The second is decision: helping a guest move from browsing to choosing without feeling overwhelmed. The third is influence: making the dishes that are good for the guest and good for the business easy to notice.

Good menu design serves those jobs in that order. Influence that gets in the way of information, such as hiding prices or burying the vegetarian dishes, tends to backfire. Guests who feel manipulated or confused trust the menu less, and a guest who does not trust the menu orders cautiously.

The most common failure in menu design is legibility. Restaurants are often dim in the evening, guests may not have their reading glasses, and the menu is read at arm's length across a table. Type that is easy to read on a laptop screen can be very hard to read in candlelight.

The usual culprits are familiar. Type that is too small, too thin or too light. Low contrast, such as grey on cream or gold on black. Long passages set in capitals, which are slower to read than mixed case. Script or decorative fonts used for anything longer than a heading. Textured or patterned backgrounds behind the text. Lines that run the full width of a large page, so the eye loses its place.

None of these choices is wrong in itself, and a strong brand can use some of them well. The test is simple: read the menu at a table, in the venue's evening lighting, at the distance a guest would hold it. If it takes effort, it needs changing, however good it looks.

Menu typography should be chosen for reading first. Use a type size that is comfortable at arm's length in dim light, usually larger than designers expect. Choose a weight with enough stroke to stay clear on textured paper, and avoid hairline fonts for dish names or descriptions.

Contrast matters more than colour. Dark text on a light background, or light text on a dark one, with a clear difference between them, is easiest to read. Keep coloured or metallic inks for headings and decoration, not for the text guests must read to order.

Keep the hierarchy simple. Section headings, dish names, descriptions and prices should each have one consistent style, so guests can scan the page and know what each line is. Two type families are usually enough: one for headings and one for everything else. Set descriptions in mixed case, keep lines to a comfortable length and leave space between dishes, so each one reads as a unit.

Menu layout should follow the order in which guests make decisions, which is usually the order in which they eat. Snacks or small plates first, then starters, mains, sides and desserts, with drinks on a separate page or card. Guests read a menu to plan a meal, and a layout that mirrors the meal makes planning easy.

Group dishes the way guests think about them, not the way the kitchen produces them. A guest looks for "something light" or "a main to share", not for "garde manger" or "grill section". Section names should be plain, and each section should be easy to find at a glance.

On a single page, give each section its own clear space. On a folded menu, think about what a guest sees first when they open it, and put the sections they need first there. Leave room around the edges and between sections; white space is what makes a full menu feel easy rather than crowded.

A longer menu does not always sell more. Too many choices slow guests down, make each dish harder to notice and make the kitchen's job harder too. A guest faced with a long list often orders something familiar, which is rarely the dish you most want to sell.

There is no universal number, but most venues benefit from keeping each section short enough to take in at a glance. If a section has grown long, look at which dishes actually sell. Our guide to menu mix covers how to read it, and our guide to menu engineering covers what to do about the dishes that do not earn their place.

A shorter menu is also easier to cook well. Fewer dishes mean fewer ingredients, less waste, faster prep and more consistent plates. Many venues find that cutting a menu improves both sales and reviews.

Menu descriptions do two jobs: they tell guests what a dish is, and they make them want it. The first job comes first. A guest should know the main ingredients, how the dish is cooked and anything surprising about it, such as heat, a raw element or an unusual texture.

Good menu descriptions are short and specific. "Grilled sea bream, fennel, blood orange, brown butter" tells the guest what to expect and sounds appealing. A long paragraph of adjectives tells them less and takes longer to read. Specific details, such as where an ingredient comes from or how long something is cooked, add interest when they are true and relevant.

Avoid words that promise more than the plate delivers. A dish described as "the best burger in the city" sets an expectation that every guest will test. Let the description be accurate and appetising, and let the dish do the rest. Keep the tone consistent across the menu, so no single dish sounds as though it came from a different restaurant.

Prices need to be easy to find and easy to read, without dominating the page. The most common approach is to place each price at the end of its description, in the same type as the text, rather than in a column down the right-hand side. A column invites guests to scan prices first and choose by cost; a price at the end of the description keeps attention on the dish.

Some venues drop the currency symbol or the decimals to make prices quieter on the page. Whatever format you choose, use it consistently, and make sure every price is clear. Guests should never have to ask what something costs, and the price on the menu should always match the price on the bill.

Avoid lining up prices from cheapest to most expensive within a section, which turns the section into a price list. Order dishes by the logic of the meal or by the dishes you want to highlight, and let price be one detail among several. Our guide to menu pricing covers how to set the prices themselves.

Menu placement is the decision about where each dish sits on the page. Positions differ in how much attention they get. The first and last dishes in a section tend to be noticed more than those in the middle, and a dish set apart with space, a box or a small illustration stands out from its neighbours.

You may have heard that guests' eyes follow a fixed path across a menu, often called the golden triangle, landing first in the upper right. The idea is widely repeated, but the evidence for it is mixed, and many guests seem to read a menu much as they read anything else: from the top, section by section. A safer rule is to place the dishes you most want to sell where they are easy to notice within their section, rather than relying on one magic spot.

Use emphasis sparingly. One featured dish per section, or one per page, draws the eye. Five boxes on a page draw nothing, because everything is shouting. The menu engineering approach of deciding which dishes deserve emphasis, based on their popularity and margin, is a good guide to where to spend it.

Every highlight on a menu should have a reason. The dishes worth highlighting are usually those with a good margin that guests do not yet order often, the dishes that represent the venue best, and dishes that are new or seasonal. Highlighting a dish that is already popular rarely adds much; it sells well anyway.

Choose the method to suit the menu. A box around one dish, a small badge such as "new" or "chef's choice", a short line of extra description or a photograph on a digital menu can all work. Keep the method consistent, so guests learn what a highlight means.

Review highlights regularly. A dish that was new six months ago is no longer new, and a highlight that no longer reflects the venue's priorities is wasted space. When the menu changes, revisit which dishes deserve the emphasis.

Allergen and dietary information is part of menu design, not an afterthought. Guests with allergies need to find the information quickly and trust it, and guests with dietary preferences need to see which dishes suit them without reading every description.

Use a small, consistent set of marks for dietary labels, such as vegetarian and vegan, explained once on the page. For allergens, many venues add a clear statement that guests should ask about allergens, with allergen information kept in a separate, accurate record that staff can show. Whatever approach you take, the information must be correct for every dish and kept up to date when recipes change. Our guide to building an allergen matrix that stays correct covers how to keep that record.

Local rules on allergen information vary, so check what applies to your venue. In the UK, for example, the Food Standards Agency publishes allergen guidance for food businesses that sets out what must be provided.

On a printed menu, photographs are a strong signal and a risky one. A good photograph of a signature dish can sell it; a page of photographs can make a menu feel like a fast-food board. Most sit-down venues use few or none on paper, relying on description and the dish itself.

On a digital menu, photographs work differently. Guests scrolling on a phone expect them, and a photograph helps them understand an unfamiliar dish quickly. If you use them, make them accurate, recent and consistent in style. A photograph that does not match the plate is worse than no photograph at all.

Wherever you use photographs, keep them honest. Portion size, garnish and presentation should match what arrives at the table. Guests forgive a plain photograph more readily than a plate that looks nothing like its picture.

A digital menu opened from a QR code on a phone is not a printed menu on a smaller screen. The guest sees a narrow column, scrolls rather than scans, and taps rather than turns pages. Menu design for a phone needs its own decisions: clear section links at the top, short descriptions, photographs where they help, and filters for dietary needs.

Keep the first screen useful. Guests should see the sections and the first dishes straight away, not a large logo, a welcome video or a cookie banner that fills the screen. Let them jump to a section, and keep the section names visible as they scroll, so they always know where they are.

The digital menu also has advantages paper cannot match. It can be updated in seconds, mark a dish sold out the moment it runs out, and let guests filter for the allergens they need to avoid. Our guide to the QR code menu five years on covers what has worked for venues that kept them, and our guide to QR ordering covers ordering from the table.

Most venues now show their menu in several places: a printed menu at the table, a digital menu behind a QR code, boards or screens in the room, a website and perhaps a delivery app. Each needs its own design, but they should all show the same dishes at the same prices.

The design of each format can differ, but the content should come from one source. When a dish changes, it should change everywhere. Our guide to updating the menu in one place, not five covers how to keep every format in step.

Keep the design language consistent across formats too. The same section names, the same dietary marks and the same tone of description help guests recognise the menu wherever they see it, and make each format easier to read.

Before a new menu goes live, test it where it will be read. Sit at a table in the evening lighting and read it at arm's length. Ask a few people who have never seen it to find a vegetarian main, the most expensive dish and something without nuts, and time them. Watch where they hesitate.

Ask the floor team as well. Servers know which dishes guests ask about, which descriptions confuse people and which questions come up every night. A menu that generates the same question at every table needs a clearer line, not a better-trained server.

Test the digital menu on several phones, in the room, on the venue's own connection. A menu that loads slowly or needs zooming to read will be abandoned in favour of asking the server.

A menu change can be measured. Compare the menu mix before and after: which dishes sold more, which sold less and whether the highlighted dishes moved. Look at average spend per head and the share of guests ordering starters, sides or desserts, which are often the first things a clearer menu sells.

Give each change a few weeks and compare like with like, such as Saturdays with Saturdays, because season, weather and events all affect what guests order. Change one thing at a time where you can, so you know what made the difference.

Listen to guests too. Fewer questions about what a dish is, fewer surprised faces when plates arrive and fewer requests for the server to explain the menu are all signs that the design is doing its job.

Here is an illustrative redesign of a dinner menu, to show how small changes add up. The details are examples, not rules.

The point is the method rather than the specific changes: read the menu in the room, fix what is hard to read, follow the order of the meal, and use emphasis deliberately.

In servearound, dishes live in one library behind every menu. A dish carries its photographs and video, its ingredients, calories and macros, its dietary and allergen tags, and a badge beside its name if you want one. Put the same dish on the lunch, dinner and bar menus and it stays one dish, with a price of its own on one menu if you want.

The QR code menu opens in the guest's browser, with no app to download, and guests can filter it by the dietary tags they want and the allergens they need to avoid. Boards for the screens in the room and print designs come from the same live menu, using templates in your type and colours, and a printed design says when it is out of date and lists what changed. Mark a dish sold out once and it is off every menu it is on.

With the Analytics module, the menu report shows every dish that sold with its units, revenue and share, and its margin once its cost is set, so you can see whether a design change moved the dishes you wanted. See the menus module, or get in touch to see it with your own menu.

Large enough to read comfortably at arm's length in your evening lighting. Test it in the room rather than relying on a number, and err on the side of larger.

Some venues do, to make prices quieter on the page. It is a style choice; consistency and clarity matter more than the symbol.

It is easier to scan and often encourages a shorter, better menu. Larger menus can work if they are well organised, with clear sections.

Review it whenever dishes change significantly, and look at the design at least once a year. Small changes, such as moving a highlight, can be made at any time.

Often they work better on a separate card or page, so the food menu stays short. A few suggested pairings beside dishes can still help.

On a digital menu they help guests understand unfamiliar dishes. On a printed menu, use them sparingly and only if they suit the style of the venue.

The dishes and prices should match. The design should suit each format: a phone needs shorter descriptions and section links, not a copy of the printed page.

Menu design is the craft of making a menu easy to read, easy to choose from and quietly persuasive, in the conditions where guests actually read it. Start with legibility: menu typography that works in low light, strong contrast and a simple hierarchy. Use a menu layout that follows the order of the meal, keep sections short, and write menu descriptions that are accurate, specific and appetising.

Place prices where they inform rather than dominate, use menu placement and highlights deliberately, keep allergen and dietary information correct, and design the digital menu for the phone it will be read on. Test every change in the room and measure it in the menu mix, then change the next thing.