A menu in English (and German, and French): translating your menu without the cringe

The menu is the first thing a foreign guest reads about your restaurant — before the food, before the service, before the bill. It's also where the most memorable fails happen, the ones that get photographed and posted. Translating your menu well isn't a fine-dining affectation: it's the difference between a tourist who orders with confidence and one who closes the card and asks for "a pizza" because they didn't understand the rest. Here's how to do it without the cringe.

The fails that actually happen

Machine translation has gifted the world some classics. You've probably seen a few:

• "Penne all'arrabbiata" → "Angry pens". In Italian penne is both the pasta and the writing tool, so the machine picks the wrong sense and the tourist ends up ordering furious biros.
• "Lingua in salsa verde" → "Language in green sauce". Lingua is both tongue and language — so the dish promises to serve you English, drowned in parsley.
• "Crema di gamberi" → "Cream of shrimp" is fine — but "Cozze alla marinara" turning into "Mussels sailor-style" isn't wrong so much as unhelpful: a guest can't tell if that's a broth, a sauce, or a person.
• French menus giving you "frog thighs" for cuisses de grenouille, German ones offering "moved egg" for Rührei (scrambled egg): technically related to the words, culinarily nonsense.

They're funny, but there's a real cost behind them: a menu that looks auto-translated tells the guest "we don't pay much attention here," and that impression rides along all the way to the tip.

Why Google Translate breaks on regional dishes

Machine translation is great for an email and a disaster for a menu. The reason is that a menu isn't made of sentences: it's made of dish names, and the names of regional dishes are almost proper nouns.

• It translates word by word, with no culinary context. "Strozzapreti" becomes priest stranglers: technically accurate, gastronomically deranged. The tourist reads a horror dish, not a pasta shape.
• It doesn't know some names shouldn't be translated. "Cacio e pepe", "amatriciana", "orecchiette" are recipes, not descriptions: translating them dismantles the dish instead of explaining it.
• It doesn't know the allergens. This is the serious one. A machine can turn "buckwheat" into something it isn't, or quietly drop the "may contain nuts." At that point it's not a laughing matter: it's a risk for anyone with an allergy.

How to render a signature dish

The golden rule is counter-intuitive: your signature dishes shouldn't be translated — they should be explained. The name is part of the value. A tourist comes for the "real carbonara," not for "pasta with egg and pork cheek."

The pattern that works, in any language, is this:

1. Keep the original name. Cacio e pepe, Osso buco, Coq au vin.
2. Add one short line of explanation in the guest's language: Cacio e pepe — Roman pasta with pecorino and black pepper.
3. Keep the allergens attached to the dish, always, in every language: if you switch language but lose the gluten or the dairy, you translated the wrong part.

That way the dish stays recognisable, the guest knows what they're ordering, and you don't sell your identity short behind a flat translation. You adapt the descriptions — you protect the names.

What to never translate (and what to always translate)

A practical rule to keep in the kitchen while you write the card:

• Don't translate: the proper names of dishes (cacio e pepe, osso buco), grape varieties and wines, PDO cheeses, the names of traditional desserts. They're identity, not description.
• Always translate: the ingredients (so the dish is understood), the cooking methods, and — non-negotiable — the allergens. A coeliac tourist must understand the gluten even if they don't understand "cacio e pepe."
• Explain, don't translate: terms with no equivalent (cover charge, the primo/secondo sequence, "al dente"). A line of context beats a forced word.

The difference between a translated menu and one a foreign guest can actually use comes down to this: protect the names, explain the rest, and never leave the allergen behind.

Translate the culture, not the words

The subtlest part isn't the names: it's the expectations. Every guest reads the menu with their own country's assumptions, and a good multilingual menu accounts for that.

• Cooking temperatures. "Al sangue" isn't bloody, it's rare. A German guest expects a precise doneness; an American wants to know if it's medium or medium-rare. Translating literally here just confuses.
• The cover charge. Obvious to an Italian; to an American, "coperto" needs explaining or it looks like a scam. One clear line avoids the argument at the till.
• Portions and courses. "Primo" and "secondo" don't exist in most tourists' heads: they know a starter and a main, but they need guiding. A menu that explains the sequence sells more, because the guest trusts it.
• Ingredients that land differently. "Guanciale" isn't bacon, and it's worth saying so. "Baccalà" is familiar to a Spaniard (bacalao), much less to a German. You localise the reference, not just the word.

Translating a menu well means exactly this: taking the same idea and rephrasing it the way someone from that country would write it — not running it through a machine and hoping.

The practical problem: six languages, a menu that changes

All true — but who actually does it? Translating six languages by hand is slow and expensive, and every time you change a dish you have to redo six versions. That's why most restaurants have, at best, an English menu done once and never updated again: the new dish only ships in the local language, tourists never see it, and the versions drift apart dish by dish.

This is exactly what Menudetto solves. You write the menu once in your own language and translate it into all 6 languages with one tap — keeping the dish names the way you want them, with the allergens staying attached to every dish, in every language. Change the carbonara? It changes everywhere. Add a dish tonight? It ships already translated for the tourist scanning it ten minutes from now.

In short

A badly translated menu isn't just funny: it tells a foreign guest you didn't think about them, and in the worst cases — when it's the allergens that get mangled — it becomes a genuine risk. The rules are few and clear: signature dishes keep their name and get a one-line explanation; Google Translate isn't enough because it knows neither the cuisine nor the allergens; and you translate the guest's culture, not the dictionary's words.

With Menudetto a multilingual menu stops being a project and becomes a tap: try it free and see your menu in 6 languages without redoing anything. And if you want to get the most delicate part right first — the allergens — start from the free allergen-table tool — no sign-up — so that when you translate, you don't lose the information that matters most.