TasteGraph
Menu EngineeringJanuary 23, 2026 · 3 min read

Using Descriptions Instead of Photos to Sell a Dish

A great photo isn't always available, and it isn't always the best tool anyway. A well-crafted description can sell a dish just as hard.

Photos get treated as the default winning move on a digital menu, and often they are. But a mediocre photo, poorly lit, shot with a phone in a rushed kitchen moment, can undersell a dish worse than no photo at all. A carefully written description, by contrast, has no risk of looking unappetizing, because it works entirely through the guest's own imagination rather than a literal image that can go wrong.

What a description can do that a photo cannot

A photo shows a single frozen moment: one plate, one angle, one lighting setup. A description can layer in the sound of something sizzling, the origin of an ingredient, the technique behind a sauce, none of which a static image conveys well. Words let a guest imagine the dish at its absolute best, seasoned exactly to their own taste, rather than judging it against one specific plate that may not even be the one that comes to their table.

This matters most for dishes that photograph poorly despite tasting excellent. A rich stew, a braised dish, anything brown and homogeneous on a plate tends to look far less appealing in a photo than it tastes in person. For those dishes, a strong description is doing real work a camera cannot.

What actually makes a description work

  • Specific ingredient origin or method beats generic adjectives like delicious or tasty
  • Sensory language, smoky, tangy, slow-braised, gives a guest something concrete to imagine
  • Length matters less than specificity; a short, precise line beats a long, vague one
  • Naming a technique or region signals effort and justifies a price without stating it outright

Compare "chicken curry" to "slow-simmered chicken in a cashew and tomato gravy, finished with fresh coriander." Both describe the same dish. Only one gives the guest a reason to choose it over three other curries on the same page.

Writing descriptions when you're not a natural copywriter

Most owners aren't professional writers, and that's fine, because the goal here isn't literary flair. Start with what actually makes the dish different from the version a guest might get elsewhere: a specific spice blend, a cooking time, a family recipe origin, an unusual pairing. Write that down plainly first, then trim it down to the shortest version that still includes the specific detail. A description that reads a little plain but includes one genuinely specific fact beats a flowery one built entirely out of generic adjectives.

It also helps to read your descriptions out loud. If a line sounds like something you'd actually say to a friend recommending the dish, it's probably working. If it sounds like it was lifted from a menu template, it probably needs another pass.

One more thing worth checking: does your description actually answer the question a guest is likely to have before ordering? For a spicy dish, that's how spicy. For a large plate, that's whether it's meant to be shared. Anticipating that one question and answering it directly in the description removes a genuine barrier to ordering, often more effectively than any amount of flowery language around the dish itself.

When to use both, and when photos genuinely win

Photos still have a clear edge for dishes where visual presentation is part of the appeal: a colorful dessert, an elaborate platter, anything where the plating itself is a selling point. For those, a good photo and a tight description together outperform either alone. The mistake is treating photos as mandatory for every single dish regardless of whether the dish actually photographs well, which leads restaurants to publish mediocre images out of obligation rather than skipping the photo and writing a stronger description instead.

TasteGraph's AI dish explainer gives guests a way to ask questions about a dish directly, how spicy it actually is, what's in the sauce, whether it's very rich, which means a description doesn't have to do every bit of persuading alone. Between a well-written line and a guest able to ask a follow-up question in plain language, a dish gets a fair shot at being understood even without a flattering photo.

TasteGraph

See what a menu that reorders itself around every guest looks like on your own dishes. Bring what you already have and go live in about 10 minutes.

Build your menu free

More on Menu Engineering