How to Translate Your Restaurant Menu — and Why Google Translate Loses You Money (2026)
A tourist looking at a menu they don't understand orders the cheapest thing on it. Every time. Not because they're careful with money — because they're guessing, and nobody guesses expensively.
Short answer: translate your menu properly and you'll usually see bigger tickets from international guests. Do it in three parts. Machine-translate the descriptions as a first draft, have a native speaker fix them, and never let a machine anywhere near your allergen text. Keep dish names in the original language and add a short explanation underneath. Publish it digitally, so one edit updates every language instead of four print runs.
Google Translate isn't bad at language anymore. It's bad at menus. That's a different problem, and it's the one costing you money.
What machine translation actually gets wrong on a menu
Modern AI translation handles normal sentences well. A menu is not normal sentences. It's a list of proper nouns, cooking methods, regional dishes, and legal declarations — all with no context around them.
Here's where it breaks, every single time:
| The problem | What the machine does | What it costs you |
|---|---|---|
| Dish names | Translates them literally | "Ropa vieja" becomes "old clothes". Guest scrolls past |
| No context | Guesses at short phrases | "Plancha" becomes "iron". "Sepia" becomes "sepia colour" |
| Cooking methods | Picks the wrong sense | "Al dente" becomes "to the tooth". Nobody orders that |
| Allergen words | Translates them like normal words | This is the dangerous one. See below |
| Portion words | Converts nothing | "8 oz" stays "8 oz" for a guest who thinks in grams |
| Your brand names | Translates them too | Your signature "Firehouse Burger" becomes something odd |
| Tone | Flattens it | Your warm, funny descriptions come out sounding like a manual |
None of that is a bug in the tool. The tool is doing exactly what it was built for. A menu just isn't prose — it's a database with adjectives.
The allergen mistranslation is the one that ends careers
Everything above is embarrassing. This one is different.
Machine translation regularly softens, flips or drops negation. "Contains no nuts" and "contains nuts" are one word apart in most languages. Auto-translate a menu into six languages and nobody on your staff can read four of them well enough to catch it.
Rule, no exceptions: allergen text is never machine-translated and never left unchecked. Get it translated by a person, then checked by a second person who eats in that language. It's maybe 40 words per language. It's the cheapest safety work you'll ever buy. Our guide to declaring allergens on a digital menu covers how to lay them out once you've got the words right.
The money: what a confusing menu really costs
Let's do the arithmetic, because "improve guest experience" doesn't pay a supplier invoice.
Take a 60-seat restaurant doing 1,200 covers a month. Say 30% are international guests — normal for a city center, a coastal town, or anywhere near a hotel. That's 360 covers.
An international guest with a menu they can't read does three things:
- Skips the starter. Can't tell what it is, doesn't risk $12 on it.
- Skips the wine list entirely. Wine descriptions are the hardest text on any menu.
- Orders the dish they recognize. Which is usually the cheapest, most generic one you serve.
Now assume a readable menu recovers just one extra item on a quarter of those covers — a starter, a dessert, a second drink at around $8.
90 covers × $8 = $720 a month. $8,640 a year. From text you write once.
And that's the friendly version. It ignores the guest who walked past your door because the window menu meant nothing to them, and the review that says "lovely food, but we had no idea what we were ordering". Reviews like that suppress bookings quietly for years — and they show up in search, which our piece on getting more Google reviews gets into.
There's a staff cost too. Every unreadable menu turns your waiters into live translators. Four minutes explaining the menu at table nine is four minutes not spent selling at table twelve.
Which languages should you translate into?
Not all of them. This is where most owners either do nothing or do nine languages badly.
Start with two or three. Add more when the data tells you to.
Where to find that data — in this order:
- Your own menu analytics. A digital menu can show you which countries scanned it. That's the most honest signal you'll ever get, because it's your actual guests, not a tourism board average.
- Google Business Profile insights. Search terms and where people find you.
- Booking and review platforms. What language are your reviews written in?
- Your neighbors. Which nationality fills the hotel down the street? Which tour buses stop nearby?
- Your staff. Waiters know which language they get asked in most. Ask them today.
A rough rule that holds up across Europe and the Gulf:
| Your situation | Sensible first set |
|---|---|
| Tourist city center (Europe) | Local language + English + one big source market |
| Coastal / resort town | Local + English + German or Dutch (or your dominant visitor) |
| US big-city restaurant | English + Spanish, then Chinese or French by neighborhood |
| Gulf / Middle East | Arabic + English, then Russian or Hindi |
| Business district | Local + English. That's genuinely enough |
| Near a university | Local + English + the biggest international student group |
English isn't optional anywhere with tourists. It's the fallback language visitors use when their own isn't offered. But English alone is a half-measure in a town full of German or French guests — they'll read it, they just won't enjoy it, and enjoyment is what makes people order the dessert.
The rule that fixes most bad menu translations
Here it is, and it's simpler than people expect:
Don't translate the dish name. Translate the description.
"Bacalao al pil pil" should stay "Bacalao al pil pil" in every language on your menu. Underneath it, in the guest's language: salt cod in a warm garlic and olive oil sauce, gently shaken until it thickens.
Three reasons this works better than translating the name:
- The guest can order it out loud. They point, they say it, the waiter understands. A translated name breaks that.
- It keeps the romance. "Old clothes" sells nothing. "Ropa vieja — slow-cooked shredded beef in tomato and peppers" sells beautifully.
- It teaches them something. People love learning a dish name on holiday. They repeat it to friends. That's free marketing.
The same rule applies to your own inventions. If you call it the "Sunday Sinner", it stays the Sunday Sinner in Polish, in Turkish, in Arabic. Only the description changes.
Exception: plain, functional items. "Green salad" doesn't need protecting. Translate it and move on.
Four ways to get it translated, and what each really costs
| Method | Typical cost per language | Speed | Good for | Honest verdict |
|---|---|---|---|---|
| Google Translate alone | $0 | Minutes | Nothing you'd publish | Fine for a draft. Never for a menu |
| AI draft + native review | $50–$150 | 1–2 days | Almost everyone | The 2026 sweet spot |
| Professional food translator | $150–$450 | 3–7 days | Fine dining, tasting menus, wine lists | Worth it where words carry the price |
| A bilingual staff member | A shift's pay | Same day | Everyday menus | Great — if they can also write well |
Professional menu translation typically runs $0.10–$0.25 per word. A 60-dish menu with descriptions is roughly 1,200–1,800 words, so budget $150–$450 per language for a full professional job.
The realistic 2026 workflow for most restaurants is the second row. AI produces a solid draft in seconds. A native speaker spends two hours fixing dish names, tone and mistakes, at $25–$50 an hour. You get 90% of professional quality for a third of the price — as long as a human genuinely reviews it. "AI plus review" where nobody reviews is just Google Translate with extra steps.
One warning about the bilingual staff member: speaking a language and writing menu copy in it are different skills. Your Polish waitress may speak perfect Polish and still write a description that reads flat. Ask for one sample dish first.
And compare all of this to print. Every extra printed language is another print run — around $200–$600 each time you change a price. Our menu printing cost breakdown runs the yearly numbers, and the QR menu vs printed menu comparison shows where the mixed setup wins.
Build a glossary before you translate anything
This is the step everyone skips, and it's the one that saves you the most time on the second language.
Write a one-page list of your terms and how each should be handled. Give it to every translator, human or AI.
Keep in the original language (never translate):
- Your restaurant name and any signature dish names
- Traditional dish names: risotto, tapas, meze, pierogi, börek, bitterballen
- Protected regional names: Prosciutto di Parma, Manchego, Champagne
Always translate, and translate consistently:
- Allergen names — same word every time, every language
- Cooking methods: grilled, fried, steamed, roasted
- Common ingredients: chicken, garlic, cream
- Everything on the "before you order" notice
Decide once and stick to it:
- Portion labels — do you convert "8 oz" to "225 g" or show both?
- Spice level — chili icons, words, or a number?
- Your tone — playful in English usually needs to become warm rather than jokey elsewhere. Humor rarely survives translation intact
Write the glossary once and every future language takes half the time. It's also the thing that keeps your menu sounding like you in six languages instead of like six different restaurants.
Allergens and the law: your local language is the legal one
This is where translation stops being a marketing job.
The rule that holds nearly everywhere: your legally required allergen information must exist in the local official language. Every other language is an addition, never a replacement. Translating your menu into English doesn't discharge a duty written in Spanish law.
Here's how it lands by market:
| Where | What's expected |
|---|---|
| European Union | 14 allergens declared for every dish, available before the guest orders. Regulation 1169/2011 requires mandatory food information in a language easily understood by consumers in the country of sale — and member states can require their own national language |
| Spain | Allergen information in writing, before ordering. Some regions have their own language requirements alongside Spanish |
| Ireland | In writing, clear and legible, without the guest having to ask (FSAI) |
| United Kingdom | Allergen information available for non-prepacked food with a clear notice. The FSA now recommends written information plus a spoken check. Full labelling for pre-packed for direct sale (Natasha's Law) |
| Netherlands / Belgium | Spoken allergen information is accepted where it's backed by a clear notice and a written record staff can consult |
| United States | 9 major allergens named federally (milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, sesame). No federal menu-labelling duty, but the FDA Food Code expects allergen-aware management, and states like Massachusetts, Rhode Island, Illinois and Michigan have their own rules |
| Gulf states (UAE, Qatar, Bahrain, Saudi Arabia) | Municipality food-safety rules generally expect allergen information to be available, and menus are commonly expected in Arabic alongside English. Check your local municipality — requirements differ by emirate and city |
Three things worth burning into the wall:
- A translation error in allergen text is your liability, not the translation tool's. "The app translated it" has never been a defense anywhere.
- A QR menu counts as "in writing" in most places — as long as the guest reaches it before ordering and you keep a backup for people without a phone.
- Your kitchen's written allergen record stays in the local language. That's the version staff and inspectors work from.
For the full list, our guide to the 15 food allergens restaurants must know has every name, and allergen menu requirements across Europe breaks down the country rules.
Why translated allergens sell, not just protect
Owners treat allergens as a legal chore. Guests treat them as a trust signal — and the effect gets stronger the further from home they are.
Think about it from their side. You're in a country where you don't speak the language, and you're allergic to sesame. You will not risk it. You'll eat somewhere safe and boring, probably a chain, probably tonight and tomorrow night.
Now imagine one restaurant on that street shows "contains sesame" in your language. You're not just eating there — you're relieved, you're loyal for the week, and you're telling the group chat. Our piece on what to do when a guest says they have an allergy covers the floor side of that conversation.
Allergy guests almost never eat alone. They pick the venue for the table of six. Translate the allergens and you're not winning a cover — you're winning the booking.
Arabic and right-to-left: translation isn't enough
If you're adding Arabic, know this upfront: it's not just different words. The whole layout flips.
Text runs right to left. So does the reading order of your page — headings, prices, icons, the lot. A menu that just pastes Arabic text into a left-to-right layout looks broken to an Arabic reader in about half a second. That's a trust problem before they've read a single dish.
What to get right:
- Full right-to-left layout, not just right-aligned text
- Modern Standard Arabic, not a regional dialect — it's the register understood from Morocco to Oman
- Numbers and prices placed the way Arabic readers expect
- A font that renders Arabic properly. Many decorative menu fonts simply don't, and letters stop connecting
Same story, in lighter form, for Hebrew. And if your market is Gulf tourists — a huge and growing segment for European coastal cities in 2026 — Arabic isn't a nice extra. It's the difference between being considered and being scrolled past.
Publishing it: one menu, many languages
Getting the words right is half the job. Delivering them is the other half, and it's where printed menus fall apart.
The printed approach: four languages means four stacks of menus, four print runs, and a guest holding the wrong one. Change a price and you reprint everything. Some venues end up handing tourists the "English menu" from 2023 because the new ones only got printed in the local language.
The digital approach: one menu, one QR code, a language switch at the top. Guest picks their language, or the menu reads their phone's setting and opens in it. You change a price once and every language updates instantly.
A few things that make a multilingual digital menu actually work:
- One QR code for all languages. Not one code per language — that's a wall of stickers nobody understands.
- A visible language switch at the very top. Flags are pretty but flawed (which flag is Arabic? which is Spanish?). Use language names written in their own language: English · Español · العربية · Türkçe.
- Auto-detect, but always let them override. A German guest whose phone is in English should be able to pick German.
- Photos, which need no translation at all. A good photo does more for a confused guest than any wording. Menu photos for online ordering covers shooting them cheaply.
If your menu is still a PDF, turning a PDF menu into a digital QR menu is the fastest route across, and how to create a QR code menu for free covers starting from nothing.
For what it's worth: Tabres lets you publish your menu in as many languages as you like — per-language dish names, descriptions, allergens, and header and footer text — with full right-to-left support for Arabic, on one QR code. It's free, and our reasoning for that is public. Use whatever tool suits you; the method here works on any of them.
Test it before you publish it
Twenty minutes of testing catches nearly everything.
- Read it aloud to a native speaker. Not a proofread — a read-aloud. They'll wince at the bad line before they can explain why.
- Check every negation. "No nuts", "gluten-free", "not spicy", "without dairy". These are where machines flip meaning.
- Open it on a real phone. Long German and Finnish words break layouts. Arabic and Russian text runs longer than English. Things overflow.
- Verify every price and number. Decimal commas and points swap between languages, and a translation tool will happily "help".
- Search for leftovers. Untranslated English hiding in a description is the most common bug of all.
- Ask one guest. Genuinely — pick a guest from that country and ask them to look for a minute. They'll tell you the truth for free.
Seven mistakes that cost real money
- Translating dish names literally. Fix: keep the name, translate the description under it.
- Machine-translating allergens. Fix: human translation, second human check, no exceptions.
- Doing nine languages badly. Fix: two done well beat nine done badly. Add languages when the data asks.
- Translating once and never again. Fix: when a dish changes, all languages change. Same day.
- A separate QR code per language. Fix: one code, one switcher, guest chooses.
- Pasting Arabic into a left-to-right layout. Fix: proper right-to-left layout, or don't offer Arabic yet.
- Losing the prices in translation. Fix: check currency, decimal marks and portion units on every version.
Get your second language live this week
You don't need a project plan. You need about three hours spread over a few days.
- Pick one language. The one your waiters get asked about most. Twenty minutes with your team.
- Write the glossary. One page: what never gets translated, what always does. Thirty minutes.
- Run an AI draft of your dish descriptions. Feed it the glossary. Ten minutes.
- Get a native speaker to fix it. Two hours of their time, paid. This is the step that matters.
- Handle the allergens separately. Human translation, checked twice. Thirty minutes.
- Publish and test on a phone. Read it aloud, hunt the leftovers. Twenty minutes.
Then watch what happens to your average ticket from those guests over the next month. If your menu tool shows you which countries scan it, you'll see the shift in the data — and you'll know exactly which language to add second. That's the same menu-data thinking behind menu engineering and pricing for perceived value.
Frequently asked questions
How do I translate my restaurant menu properly? Keep dish names in their original language and translate the descriptions underneath them. Use AI for a first draft, then pay a native speaker two hours to fix tone and mistakes. Translate allergen information separately by hand, and have a second person check it. Publish digitally so one edit updates every language at once.
Is Google Translate good enough for a restaurant menu? For a first draft, yes. For publishing, no. It translates dish names literally, guesses wrong on short phrases with no context, and — most seriously — can flip negation in allergen text, turning "contains no nuts" into the opposite. Use it to save time, never to finish the job.
How much does it cost to translate a restaurant menu? A full professional job typically runs $0.10–$0.25 per word, so roughly $150–$450 per language for a 60-dish menu. The common 2026 route is an AI draft plus two hours of native-speaker review, around $50–$150 per language. Compare that with $200–$600 for each printed run per language.
How many languages should a restaurant menu have? Two or three to start: your local language, English, and your biggest visitor group. Add more only when your data supports it. Two languages done well beat six done badly — a bad translation reads as carelessness about everything, including the food.
Should I translate the names of dishes? No. Keep traditional and signature names in the original language and put a short description underneath in the guest's language. Guests can then order out loud, the dish keeps its character, and you avoid the "old clothes" problem entirely.
Do I legally have to provide a menu in more than one language? In most countries you must provide mandatory information — especially allergens — in the local official language, in a form guests understand. Extra languages are usually optional and commercial. Some markets, such as several Gulf cities, commonly expect Arabic alongside English. Check your local authority, because the rules on method vary.
Can I machine-translate allergen information? No. Negation and near-identical words are exactly where machine translation fails, and the consequences are medical rather than cosmetic. Have allergen text translated by a person and checked by a second person. It's usually under 50 words per language.
How do I show multiple languages on a QR menu? Use one QR code with a language switch at the top of the menu. Let the menu detect the phone's language, but always let guests change it. Avoid one QR code per language — guests scan the wrong sticker, and you multiply your printing.
What about right-to-left languages like Arabic? Arabic needs the whole layout mirrored, not just right-aligned text. Headings, prices, icons and reading order all flip. Use Modern Standard Arabic rather than a regional dialect, and check your font renders Arabic letters connected properly — many decorative fonts don't.
How often should I update my translated menu? Every time the original changes. A price change, a new dish, a swapped ingredient — all languages update the same day. This is the strongest argument for a digital menu: one edit, every language, no reprint and no stale English version from two summers ago.
Here's the honest summary. Menu translation isn't a language project. It's a sales project that happens to involve language.
Keep the dish names. Translate the descriptions. Never let a machine touch your allergens. Do two languages properly instead of six carelessly, and publish it somewhere you can fix in ten seconds.
Do that, and the guest who used to point at the cheapest thing on the menu starts ordering like they're at home. That's the whole return — and it comes from work you do once.
