The words on your menu are doing sales work whether you've thought about them or not. Research from Cornell University found that descriptive menu labels — dishes with evocative, specific language — increased sales by around 27% compared to the same dishes listed with plain names. Guests rated the food as tasting better and gave the restaurant higher scores for quality, even though the food was identical. That's the power of menu description writing for restaurants: the right words don't just inform, they persuade, they set expectations, and they make the dining experience start before the first dish arrives.
Most restaurant menus undersell their food. They list ingredients in a neutral, functional way — as if they're writing a stock inventory rather than a sales document. If your kitchen is putting care and craft into every dish, your menu descriptions should reflect that. This guide covers the psychology behind menu language, the specific techniques that work, what to cut, and how to know when a description isn't doing its job.
The Psychology of Menu Language
Why do words change how food tastes? Partly because they set expectations: if you read "hand-rolled pasta with slow-braised Herefordshire beef ragu," your brain is already anticipating richness and depth before the plate arrives. When the dish delivers on that expectation, the experience feels more satisfying. Generic descriptions set lower expectations — and even a good dish can feel ordinary when it's been introduced as "beef pasta."
There's also a signalling effect. Specific, confident language communicates that a restaurant knows and cares about its food. "Free-range Berkshire pork belly" signals provenance and quality. "Pork belly" signals nothing. Guests can't taste the difference in the description, but they can feel the difference in their confidence about what they're ordering — and that confidence translates into a more enjoyable experience and a more positive review.
Sensory Words vs Generic Words
The most impactful change you can make to your menu is replacing generic process words with sensory or specific ones. Here are common swaps that make an immediate difference:
"Cooked" → "slow-braised," "wood-roasted," "pan-seared," "chargrilled" "Sliced" → "hand-cut," "thinly shaved," "thickly carved" "Made" → "hand-rolled," "house-cured," "stone-baked," "freshly churned" "With sauce" → "finished with," "dressed in," "resting in"
The goal isn't to fill descriptions with unnecessary adjectives — it's to replace vague words with specific ones that paint a clearer, more appealing picture. "Pan-seared sea bass" is more evocative than "cooked sea bass" and no longer than it. Every word is doing more work.
Sensory language — texture, temperature, aroma — is particularly powerful. "Crisp," "silky," "smoky," "warm," "cooling," "fragrant" all activate the senses in a way that plain ingredient lists don't. Use them sparingly and accurately: don't describe something as "crispy" if the texture varies, and don't use "delicate" for a dish that's robustly flavoured.
Provenance and Origin: Where Ingredients Come From
Naming the origin of key ingredients adds perceived value without adding cost. "Scottish salmon" outperforms "salmon." "Cornish crab" outperforms "crab." "Lincolnshire Poacher cheese" outperforms "hard cheese." This works because it signals that someone in your kitchen made a deliberate sourcing decision — which implies quality, care, and authenticity.
You don't need to source from a different county for every dish. If your key protein comes from a named local farm or a well-known region, put that on the menu. If your bread is made in-house, say so. If your ice cream is churned by a local supplier, name them. Guests increasingly care about where food comes from, and menus that acknowledge this connect more strongly with modern dining values.
Be accurate. Never claim provenance you can't verify, and don't name a region if your supplier sources from multiple locations. Guests notice inconsistencies, and a well-informed guest who asks about the "Herefordshire beef" and gets a blank look will lose trust quickly.
What to Leave Out of Menu Descriptions
Just as important as what you include is what you omit. Three things that consistently clutter menus and reduce their effectiveness:
Prices in pence. "£14.50" reads fine. "£14.50p" looks amateurish. And if you're in a positioning where it's appropriate, dropping pence entirely ("£14" or even just "14") makes the price feel less transactional.
Allergen codes in the description. Allergen information is important, but it belongs in a separate section, a footnote system, or an allergens guide — not embedded in the dish description. "Grilled salmon (GF, DF)" interrupts the flow and reminds guests of restrictions rather than appetite.
Long ingredient lists. "Lamb rump with dauphinoise potatoes, wilted spinach, roasted cherry tomatoes, red wine jus, and crispy capers" is exhausting to read. Pick the two or three most compelling elements and describe those. The rest can be discovered on the plate — that's part of the experience.
Formatting: Length and Structure
Two to three lines is the right length for most dish descriptions. Long enough to give sensory context and signal quality; short enough to read at a glance. If your description runs to four or more lines, it's doing too much work — cut it back to the strongest two or three elements.
Dish names should be distinctive without being opaque. A name like "The Garden" is evocative but tells a guest nothing without the description. A name like "Roast Heritage Beet" does enough on its own that the description only needs to add one or two supporting details. If your dish names are purely poetic or abstract, your descriptions need to work harder to orient the reader.
Writing Dish Names That Intrigue Without Confusing
The best dish names give a clear anchor — the main ingredient or cooking method — and add one layer of intrigue or character. "Burnt Honey Tart" is clear and intriguing. "Twilight Dream" is neither. Think about names from the guest's perspective: they're scanning a menu while having a conversation, and they need to process each name in under two seconds.
Named specials can work well ("The Chef's Rib-Eye") if they're used sparingly and backed by a strong description. Overuse of named dishes can feel gimmicky. Keep named dishes for the ones that genuinely have a story worth telling.
Updating Descriptions When a Dish Underperforms
If a dish is consistently one of your lower sellers and you've verified the quality is good, the description is the first thing to review before pulling it from the menu. Rewrite it: make the name clearer, add a sensory detail, name the provenance of the key ingredient, and remove any language that's flat or generic. Then monitor sales over the following two or three weeks. A well-written description won't rescue a bad dish, but it can absolutely transform the performance of a good one that hasn't been communicated well.
Frequently Asked Questions
How long should a menu description be for a restaurant? Two to three lines is the standard for most main courses and starters. That's typically 20–40 words. Dessert descriptions can be slightly shorter — one to two lines — as guests are often scanning quickly at that point in the meal. If you find yourself writing more than three lines, you're either listing too many ingredients or using too many adjectives. Cut to the most compelling two or three details.
Should I write menu descriptions in a formal or casual tone? Match your restaurant's overall voice. A fine dining restaurant benefits from precise, restrained language that signals expertise. A casual neighbourhood bistro can be warmer and more conversational. The key is consistency across all your dishes — a menu where some descriptions are formal and others are chatty feels unedited and unprofessional. Decide on a tone and apply it throughout.
Does menu description writing really increase sales? Research strongly suggests yes. The Cornell study on descriptive menu labels found a 27% sales increase for dishes with evocative descriptions compared to plain names. Beyond the data, the logic holds: guests who are drawn in by a description are more confident in their choice, more likely to feel the dish met expectations, and more likely to order it in the first place rather than defaulting to the safest option on the menu.
Make your menu work as hard as your kitchen. Design a beautiful restaurant menu with Hero Content's menu generator.