How to translate your menu for tourists
Keep the local dish name and add a short description underneath rather than translating the name itself. Tavče gravče should stay Tavče gravče, followed by a line explaining it is baked beans with peppers. A translated name loses the dish; a description sells it and teaches the visitor something.
5 min read Published
Should you translate the name of a dish?
Usually not. A traditional dish name is part of what a visitor came for, and translating it flattens the thing they wanted to try. "Baked beans" tells a tourist nothing about Tavče gravče, makes it sound like something from a tin, and removes any reason to order it over the pasta.
The approach that works is to keep the original name in its own language and add one clear sentence underneath saying what arrives on the plate. The guest learns the name, understands the dish, and can say it to the waiter. That is a better result than a translation on every count.
What should the description actually say?
Say what it is made of and how it is cooked, in plain words. A visitor is deciding whether they will like something, not reading a recipe. One sentence of ten to fifteen words does the job; a paragraph does not get read.
Lead with the main ingredient, then the method, then anything distinctive. "Slow-baked beans with red peppers and paprika, served in the clay dish it is cooked in" tells somebody everything they need in one line. Avoid words that sound the same in every language but mean nothing specific, like "traditional" or "special".
- Name the main ingredient first — that is what people scan for.
- Say how it is cooked: grilled, baked, fried, raw, smoked.
- Flag anything a visitor would not expect: very spicy, very large, served cold, contains pork.
- Keep it to one sentence. Two at most.
Which languages are worth adding?
Start with the languages your actual guests speak, not the ones that feel prestigious. For most venues in North Macedonia, Albania and Kosovo that means the local language plus English, then whichever visitor language turns up most often in your dining room. Ask your waiters — they know before any analytics do.
This is where printed menus lose badly. Every additional language means another printed version, another stack to store, another reprint when a price changes, and a guest who has to ask the waiter for the right one. A digital menu carries every language at once and lets the guest choose, so adding a fourth language costs nothing but the typing.
What about allergens and dietary information?
Mark them clearly and in every language. A visitor who cannot eat pork, gluten or dairy will usually order the safest-looking thing on the menu rather than ask, which normally means they order less than they would have. Simple, visible labelling turns that hesitation into an order.
Be accurate rather than exhaustive. Marking the obvious cases — contains pork, contains nuts, vegetarian, can be made without gluten — covers most of the real questions. Do not claim a dish is free of something unless the kitchen can genuinely stand behind it.
Frequently Asked Questions
Should I translate traditional dish names into English?
No. Keep the original name and add a short description underneath saying what the dish is. Translating the name loses the thing a visitor came to try, while a one-line description explains the dish, sells it, and teaches the guest a word they can say to the waiter.
How many languages should a restaurant menu have?
Start with your local language plus English, then add whichever language your guests actually speak most often — your waiters will know before any data does. On a printed menu each language is another version to reprint; on a digital menu the guest simply picks their own.
Is machine translation good enough for a menu?
For descriptions of ordinary dishes, usually yes. For traditional dishes it often fails badly, because it translates the name into something misleading. Have a person who speaks the language read the finished menu before you publish it, particularly the local specialities.