Recipes in any language

What gets translated

Translation runs on every import path that has text or audio:

• Captions on TikTok, Instagram Reels, Facebook, and YouTube — in any language the original creator typed in.
• Spoken audio in cooking videos. We transcribe and translate in the same pass.
• Article body on a non-English food blog.
• Photos with non-English text — we OCR and translate together.
• Recipes you paste into the app, in whatever language you paste.

What we do with the title

Idiomatic titles get rewritten to describe the dish rather than transliterate word-for-word. A Japanese title like "わさびのツーンが最高！笠原流【豚わさ】" becomes "Kasahara-Style Pork with Wasabi." The result reads cleanly in your library and means something to anyone you share it with.

What stays put

• The original source URL. Stored alongside the translated recipe — tap it any time to see the original in its native language.
• Original units. A Japanese recipe's measurements stay as authored (Japanese cups are 200 ml, not 240 ml — we don't silently rescale). Use the units toggle to convert to grams or US cups.
• Original ingredient names when there's no clean English equivalent. Shiso stays shiso, gochujang stays gochujang.

What might surprise you

• It only happens at import. Recipes you've already saved don't retroactively translate. Recipes you typed in by hand stay as you wrote them.
• Spice levels are translated literally. A Thai recipe's "prik kee noo" becomes "bird's-eye chili" — we don't soften or amplify the heat for non-Thai palates.
• Cultural unit assumptions are preserved. A Japanese "1 sheet of nori" stays as "1 sheet" — we don't expand to "about 18 × 20 cm" because the cultural shorthand is itself information.

Limits

If a language we can't translate slips through (very rare — Gemini handles ~100), the import retries automatically. If it still doesn't land cleanly, the recipe arrives with the original text and a non-English-content notice so you can copy it across by hand.