Menu Descriptions: 16 Examples & How to Write Your Own

A menu description is the short line under a dish name that tells a guest what arrives on the plate and why this version is worth ordering. The best ones do three things in one or two sentences: name the dish plainly, front-load the one detail that sets it apart, and flag anything that changes the decision — heat level, portion size, allergens.

In a US Foods survey of 1,003 American diners, 83% check a restaurant's menu before they walk in and half have already decided what to order before arriving. For those guests, your description is the whole sales conversation.

Below: 16 before-and-after examples, the ten rules behind them, the words that carry legal risk, and a two-week test that tells you whether your rewrite moved anything.

Three things, in this order.

Say what the dish is. The first few words should let a guest scanning twenty items know what they're looking at. If it's a burger, the opening words say what kind of burger.
Front-load what makes your version different. Dry-aged 28 days. Fried to order. No cream. Made in our kitchen. This separates your dish from the same dish down the street, and it belongs early.
Flag anything that changes the decision. Heat level, portion, wait time, what's packed separately for delivery. If a guest would have asked the server, it goes in the description.

Everything beyond those three costs attention without earning an order. That's the whole test: does this word do one of the three jobs? If not, cut it.

Every pair shows the same dish written twice. The weak version isn't wrong — it's just doing nothing. Swap in your own ingredients and the structure holds.

These are descriptions, not layouts: for the page itself, see our restaurant menu examples, and for the running order, grouping dishes into menu categories comes first.

Starters

❌ Weak	✅ Better	Why it works
Calamari	Salt-and-pepper calamari, flash-fried, with lemon aioli and pickled chili.	Cooking method plus one contrast
Bruschetta with tomatoes	Grilled sourdough, tomatoes marinated in garlic and basil, whipped ricotta.	Naming the bread makes it specific

Mains

❌ Weak	✅ Better	Why it works
Grilled chicken sandwich	Buttermilk-brined chicken thigh, grilled, with smoked chili mayo on a toasted brioche bun.	The differentiator leads
Steak frites	10 oz ribeye, dry-aged 28 days, grilled over charcoal. Duck-fat fries.	Portion and process justify the price
Vegetable curry	Slow-simmered coconut curry with roasted cauliflower, chickpeas and lime. Mild. Vegan.	Heat level and diet as single words
Fish and chips	Beer-battered cod, fried to order, with triple-cooked chips and house tartare.	Sets the wait expectation

Pizza and pasta

❌ Weak	✅ Better	Why it works
Margherita pizza — tomato, mozzarella, basil	72-hour cold-fermented dough, San Marzano tomato, fior di latte, basil.	The differentiator nobody mentions
Carbonara — pasta with bacon and cream sauce	Guanciale, pecorino romano, egg yolk, black pepper. No cream.	Answers the question before it's asked

Salads and sides

❌ Weak	✅ Better	Why it works
Caesar salad	Baby gem, anchovy dressing made in our kitchen, parmesan, sourdough croutons.	Naming the anchovy prevents a return
Side of fries	Twice-fried, skin-on, rosemary salt. Serves two.	The portion cue prevents a double order

Desserts

❌ Weak	✅ Better	Why it works
Chocolate cake with ice cream	Warm dark chocolate cake with a molten center, salted caramel ice cream. Made to order, 12 minutes.	Wait time belongs here, not in an apology
New York cheesecake	Baked vanilla cheesecake, roasted rhubarb, shortbread crumb.	Concrete nouns beat a borrowed place name

Drinks

❌ Weak	✅ Better	Why it works
House margarita	Blanco tequila, fresh lime, agave. On the rocks, salt rim.	On a drinks list, the build is the description
Flat white	Double ristretto, steamed whole milk, 6 oz. Single-origin Ethiopian, roasted locally.	Size prevents the usual counter question

Delivery and takeout

Descriptions written for a dining room quietly fail in a delivery bag. The guest can't ask a question, can't see the plate, and won't open it for 25 minutes. Two details fix most of it: how the dish travels, and what to do on arrival.

❌ Weak	✅ Better	Why it works
Chicken bowl	Grilled chicken, rice, black beans, pico, avocado. Sauce packed separately so nothing goes soft.	Delivery-native information nobody writes
Pasta bake (large)	Baked rigatoni with pork ragù and mozzarella. Feeds 3–4. Reheat 20 minutes at 350°F / 180°C.	Reheat instructions cut refunds

The same description works differently on different channels. On your own online ordering channel, you control the length, the fields, and the formatting — which is where these versions perform best.

Does a better description actually sell more food?

Almost every article quotes the same number: descriptive menu labels lift sales by 27%. It comes from a 2001 Cornell study run over six weeks in one cafeteria with 140 diners.

Its lead author, Brian Wansink, resigned from Cornell in 2018 after the university found academic misconduct, and 18 of his papers have been retracted. That paper isn't among them, but Cornell told journal editors it couldn't vouch for his results.

Later work is mixed: an experiment with 424 diners found no statistically significant effect of descriptive wording on purchase intention.

Better evidence exists for what diners say they want. In a US Foods survey of 1,003 diners:

65% named item descriptions a key menu factor
68% wanted every ingredient in a dish listed
78% weighed portion size when ordering

1. Name the dish before you describe it

Plain name first, description second. If a guest needs the whole line to work out what the dish is, the name has failed.

2. Front-load what makes it different

One fact usually sets your dish apart: time, a technique, a cut. "Slow-cooked pork ribs in garlic marinade" beats "pork ribs with garlic" because it says what happened to the plate.

3. Use sensory words

One adjective per description, two at most. The cooking method says more than the flavor word.

Texture and flavour	Cooking method	How it lands
Crispy, velvety, juicy, succulent	Slow-cooked, char-grilled, wood-fired	Comforting, warming
Zesty, tangy, bright, sharp	Roasted, braised, smoked	Refreshing, light
Flaky, buttery, silky, tender	Flash-fried, sous-vide, griddled	Rich, filling
Smoky, peppery, earthy	Baked, cured, pickled	Sharp, clean

4. Say where it comes from (if you can prove it)

Origin sells — Nielsen found 46% pay more for locally sourced products; the NRA found 60% pay more for sustainably produced food, which makes restaurant sustainability a menu argument.

5. Label dietary options with a word, not a sentence

Gluten-free, vegan, contains nuts. A label or icon does the job; a paragraph doesn't. UpMenu applies ready-made or custom labels across any menu templates you use.

6. Give the portion when it changes the decision

"Serves two." "Feeds 3–4." "6 oz." The most under-used detail on most menus — 78% of diners weigh portion size before ordering.

7. Tell a story only if it's true

Two dishes across the menu, maximum. And keep it true: a guest who checks and finds it invented remembers the menu, not the meal.

8. Match the tone to your brand, not to a trend

Funny descriptions travel well on social and land badly on the wrong menu. Start with your restaurant's target audience and keep one tone of voice for coherent branding.

9. Write for the screen your guest is holding

One or two sentences; lead with the differentiator. The description and photo must tell the same story — 66% of diners have rejected a dish based on its picture alone.

10. Avoid these nine mistakes

Filler adjectives. Delicious, mouthwatering, tasty say how to feel, not what to picture.
Culinary jargon. If someone searches "gastrique" mid-order, you've lost them.
Too many adjectives. Three in one line cancel each other out.
Negative associations. Burnt, greasy, sugary → charred, velvety, glazed.
Typos. They read as carelessness about the food.
Overpromising. "The best you've ever had" invites dispute.
Insider nicknames. Regulars get the joke; new guests get nothing.
Copied descriptions. Guests notice, and it puts your brand behind theirs.
Price fighting the description. See how menu pricing works.

What belongs in a field instead of the description

Four kinds of information look like they belong in the sentence but don't: the full ingredient list, allergens, calorie counts, and portion prices.

Each has its own field, and each stops working once you bury it in prose — a guest filtering for gluten-free never sees the words inside a paragraph.

That also resolves an apparent contradiction: 68% of diners want every ingredient listed, while every menu-writing guide says don't list them all. Both are right — the full list belongs where a guest can filter it; the description carries the two or three that sell the dish.

Information	In the description?	Where it belongs	Why
What the dish is	Yes	—	The one mandatory job
What makes your version different	Yes	—	The part that moves the order
Heat level, wait time, "no cream"	Yes	—	Changes the decision at the point of order
Portion cue that affects the choice	Yes	—	78% weigh portion size
Full ingredient list	No	Item detail	Want available, not in a sentence
Allergens	No	Allergen field	In prose, it can't be filtered
Calories and nutrition	No	Nutrition field, per size	Changes with portion; text can't
Portion sizes and prices	No	Price options	A sentence can't go in a cart
Serving hours	No	Availability schedule	Text goes stale; a schedule doesn't

Editing one dish across the website, app, QR code menu, and delivery listings is the argument for fields over sentences. Menu management software keeps them separate, so a recipe change updates once — the principle behind a structured digital menu.

Words that carry legal risk

Some words that make a description work are also claims you can be asked to back up. In the US, menu accuracy falls under state and local "truth in menu" rules — California treats knowingly mislabeling food as a criminal offense — and enforcement has targeted exactly the words restaurants reach for first: "fresh" juice from concentrate, "homemade" entrées that arrived frozen, "Maine" lobster from elsewhere.

Separately, the FDA regulates nutrient content claims: "low fat", "light" and "heart healthy" need a documented basis, one location or twenty.

The rule: if you can't produce an invoice, a certificate, or a photo of the process, keep the word off the menu. "Fresh salmon" becomes "salmon delivered daily"; "homemade pasta" becomes "pasta rolled in our kitchen each morning" — safer, more specific, better.

Keeping descriptions current in more than one language

Every sentence is one someone translates, checks, and maintains, and the edit repeats once per language every time a recipe changes. On a 200-item menu in three languages, a generous writing habit becomes a standing obligation nobody scheduled. Write the shortest line that does the job, and tie translations to the item, not to a layout.

How to tell whether a rewrite worked

A two-week comparison, no special tooling.

Pick 5 to 10 dishes. Read the menu out loud in the order a guest reads it. The items where you pause are the ones to rewrite.
Change one thing. Leave price, photo, and position alone, or you won't know which did the work.
After two weeks, compare views against orders.

What the gap tells you:

Lots of views, few orders — the description, price, or photo. This is where a rewrite pays.
Few views at all — the dish name, or which dishes need the description work. Rewriting won't fix it.
Both up — apply the structure to the next batch.

A description can't fix a dish people send back, and it can't make an implausible price plausible. It can justify a price a guest already finds believable — past that, better wording just moves the disappointment later in the visit.