How to Translate Foreign Recipes (and Get the Units Right)

The best carbonara tutorial on the internet is in Italian. The bread technique you want is explained by a Japanese baker; the stew that stopped your scroll is captioned in Turkish. Great cooking has never been more global — and the recipes worth cooking are very often not in your language, or not in your units. Both barriers are more solvable than they look.

The two barriers: words and units

Language is the obvious one — you cannot cook from instructions you cannot read. The subtler one is measurement culture: an American recipe speaks in cups and sticks, a European one in grams and milliliters, and a home recipe from anywhere might say “one glass” or “a packet.” Translating the words without translating the measurements gets you halfway to dinner.

Manual translation: what works and where it breaks

The free toolkit is genuinely decent:

• Browser page translation (built into Chrome and Safari) handles food-blog prose well enough to follow along.
• Translation apps with camera mode can read a printed foreign cookbook page.
• Copy-pasting a caption into a translator works for social posts.

But recipe language is a specialist domain, and general translators stumble in predictable places:

• Ingredient false friends. Culinary vocabulary is full of near-misses — words for specific cuts, dairy products, or flour types that get flattened into a generic (and wrong) equivalent. A translation that renders three different fresh cheeses as just “cheese” will quietly change the dish.
• Technique verbs. Cooking verbs are precise — fold, cream, deglaze — and machine translation of casual speech often loses exactly that precision.
• Cultural shorthand. “A packet of vanilla sugar” or “one glass of milk” assumes you know the local packet and the local glass.

The practical rule: machine translation gets you 90% of the way, and the remaining 10% is concentrated in ingredient names and quantities — which is precisely the part you cannot afford to get wrong.

Converting the units: cups to grams

For the measurement barrier, remember one thing: cups measure volume, grams measure weight, so every ingredient converts differently. A cup of flour and a cup of sugar do not weigh the same. Standard conversions for the most common baking ingredients:

Ingredient	1 US cup ≈
All-purpose flour	120–125 g
Granulated sugar	200 g
Brown sugar (packed)	220 g
Butter	227 g (two sticks = 1 cup)
Rolled oats	90 g
Water, milk, liquids	240 ml

Two habits make conversions painless: use a kitchen scale (weight is more accurate than volume anyway, especially for flour), and when a recipe matters, convert everything before you start cooking, not mid-recipe with battered hands.

The one-step version: auto-translation at import

Here is where the workflow gets dramatically shorter. In Rețetele Mele — the app we build, in Romania, precisely because so much great content reaches us in other languages — translation is folded into the import itself:

1. Paste the link — a YouTube video, a TikTok, an Instagram post, or a blog page, in any language.
2. AI extracts the recipe from the text: ingredients with quantities, and the steps in order. How that extraction works under the hood is its own story — see how AI recipe extraction works.
3. The recipe is auto-translated as part of the process, so what lands in your collection is already readable — no separate translator, no copy-paste round trips.
4. Review the ingredient names once. The same 10% rule applies to any machine translation: skim the ingredients, and if one looks unusual, check the source. Every field is editable, so a correction takes seconds.

This changes what you can cook from. A German grandmother’s YouTube channel, an Italian pasta account, a Korean home-cooking blog — all become one paste away, in a form you can search, plan, and shop from. For video sources specifically, the extraction path matters (description first, transcript as fallback), which we cover in getting the recipe from a YouTube video.

Small print worth respecting

Two honest notes from experience. First, translation does not convert culture: an ingredient may translate perfectly and still be hard to find in your local store — keep an eye out for reasonable substitutes, which good recipes often mention. Second, keep the source link with the recipe. When a step feels ambiguous in translation, thirty seconds of watching the original video resolves what no dictionary can.

FAQ

Is AI translation of recipes accurate enough to cook from?

Yes, with the ingredient-check habit. Steps and quantities translate reliably; the risk concentrates in specialized ingredient names. A ten-second skim of the ingredient list — the same review you should give any AI extraction — catches nearly all of it.

Do I still need to convert cups to grams myself?

Treat conversion as part of your review. Keep the table above (or a kitchen scale with a units button) handy, and rewrite the quantities in the saved recipe once — after that, your stored version is permanently in your units.

What languages does this work with?

The import works with links and recipes from any language — the point of AI-based extraction is that it reads text the way a multilingual human would, rather than relying on per-language rules.

Should I keep the original-language version too?

Keeping the source link achieves this: your collection holds the translated, cookable version, and the link preserves the original for reference, technique videos included.