How to design a restaurant menu

Start with structure, not graphics

Before you think about fonts or color, decide what the menu contains and in what order. Group dishes the way guests order a meal: starters, mains, sides, desserts, drinks. Within each section, sequence items deliberately rather than alphabetically, because position changes what sells. The first and last items in a list draw the most attention, so place a strong-margin dish in each anchor position. Keep sections short. A section with fourteen options reads as a wall of text and pushes guests toward the safe, familiar choice. Six to nine items per section is a comfortable range for most full-service concepts. Decide your structure first and the design decisions that follow become obvious.

• Order sections by meal sequence, not by kitchen station
• Cap most sections at six to nine items
• Place high-margin dishes first and last in each list

Write descriptions that do one job

Every dish gets a single line. The line names the two or three components a guest needs to picture the plate and decide, then stops. Lead with the protein or the hero ingredient, follow with the preparation and one or two supporting elements. Avoid stacking adjectives — concrete nouns do more work than words like delicious or amazing. Consistency matters as much as wording: if one starter lists its sauce and another does not, the menu reads as careless. Set a pattern and hold it across every section. Mark dietary tags such as vegan, vegetarian, and gluten-free with a consistent symbol so guests with restrictions can scan without asking. The goal is a description a server never has to explain.

Price for margin, then present it cleanly

Pricing belongs to the design conversation because of where and how numbers appear. Cost each dish against its food cost and contribution margin, then set the menu price to protect the margin you need rather than matching the place down the street. Once prices are set, present them without leader dots — those rows of dots running from dish to price train the eye to read down the price column and shop by number. Drop the dots, drop the dollar sign where your design allows, and let the price sit quietly at the end of the description. Round to whole numbers or charm endings consistently. The aim is for guests to choose the dish first and notice the price second.

Lay it out for the way guests read

Guests do not read a menu top to bottom. They scan, landing on whatever the layout emphasizes — boxes, white space, bold type, or images. Use that. Give your one or two signature dishes a box or extra surrounding space so the eye stops there. Keep type large enough to read in low restaurant light, generally eleven points or more for body text, and pair one clear heading font with one readable body font. Resist the urge to fill the page; white space signals quality and slows the scan. On a digital or QR menu the same logic applies vertically — short sections, clear headings, and a tap-friendly layout that loads fast on a phone.

Build it as editable data, not a flat image

The most expensive menu mistake is locking your work into a flat design file you cannot easily change. Prices move, dishes get eighty-sixed, and seasons turn. Build the menu as structured data — sections, dishes, descriptions, and prices you can edit — then publish a hosted page for QR access and export a print-ready PDF from the same source. MenuCrafters works this way: describe your restaurant to get a structured draft or start from a cuisine template, refine every line, and publish once. When something changes, you edit the data and both the QR page and the PDF stay in sync, so the menu on the table always matches the menu in the kitchen.