How to translate recipes without changing quantities

Recipe translation is safer when text translation, quantity preservation, unit display, and unit conversion are treated as separate operations. This guide explains that contract and reports CookbookSocial's dated structural and naturalness evidence without presenting automated checks as proof of perfect meaning.

By CookbookSocial · Published · Updated

Disclosure: This page is published by CookbookSocial. CookbookSocial is included where relevant, and product claims are limited to documented, repeatable tests.

A safe recipe translation workflow

First keep the original recipe and its source. Translate the title, description, ingredient names, section names, and cooking steps into one explicit target language. Match every translated ingredient, step, and sub-recipe back to the same source position so the structure cannot silently grow or shrink.

Preserve numeric quantities and canonical unit codes during translation. Localized labels such as tablespoon abbreviations and metric-to-imperial conversion belong to the display layer and user preferences, not to the translation output. Finally, compare the translated recipe with the original for culinary meaning, ambiguous ingredient names, temperatures, timings, and culturally specific techniques.

What CookbookSocial translates and what it preserves

CookbookSocial stores a full translation separately from the base recipe. The display view can switch between the translated text and the original without a second AI call. Author, source URL, time, category, numeric quantities, and canonical units continue to come from the base recipe; translated text does not replace provenance.

The current offline eval corpus contains 32 curated recipes across all 20 supported base languages and four source types: manual, short video, YouTube, and multi-component recipes. The paid June 14, 2026 campaign predates the latest corpus expansion and covered 35 recipe-language pairs: all 35 position-merged outputs passed structural parity, quantity and unit preservation, non-empty-field, and translated-text checks. That result validates the merge contract, not complete semantic correctness.

Recipe fields in the translation contract

Recipe fields in the translation contract
FieldTranslation behaviorRequired review
Title and descriptionTranslated into the selected target languageCheck dish identity, tone, and culturally specific terms
Ingredient names and section namesTranslated in the same positions as the sourceCheck ambiguous ingredients, cuts, varieties, and preparation notes
Cooking stepsTranslated one for one; step counts must remain unchangedCheck action, order, negation, temperature, timing, and doneness cues
Numeric quantitiesCopied from the source position and blocked from changingConfirm that the source quantity itself was correct before translation
Canonical unitsPreserved as language-neutral codes such as g, ml, tbsp, tsp, cup, or pcsDo not confuse localized unit labels with a translated ingredient
Metric or imperial conversionHandled separately by display preferences, not by translationReview rounding and cooking-sensitive measurements after conversion
Author and source URLRetained from the base recipe instead of generated by the translationOpen the source when a phrase or technique remains uncertain

CookbookSocial translation evidence rechecked October 15, 2026

CookbookSocial translation evidence rechecked October 15, 2026
EvidenceScopeObserved resultWhat it does not prove
Current offline eval corpus32 recipes; 20 base languages; manual, short-video, YouTube, and multi-component sourcesFixture shape, language coverage, canonical quantities and units, and deterministic source hashes pass offline validationNo AI translation is run by this offline test
Paid structural eval from June 14, 202635 recipe-language pairs using Google Gemini 2.5 Flash35/35 merged outputs passed; 0 failed, 0 errored, and no not-translated result remainedThe current 32-recipe corpus was expanded after this campaign and was not fully rerun as a paid campaign
Raw-output comparisonThe same 35 pairs before position mergeThe model sometimes changed quantities, units, or structure; position merge restored the source contract before persistenceA clean merged structure does not guarantee every translated phrase is semantically perfect
Manual naturalness spot-checkReal Ukrainian, Japanese, and Chinese recipes translated to EnglishReview found culinary, idiomatic English without transliteration and faithful source meaningThree language directions are a spot-check, not exhaustive linguistic certification
Dev display smoke from October 5, 2026One existing Ukrainian recipe with a ready Czech translationTitle, first ingredient, and first step switched between Czech and the Ukrainian original without console or page errorsThis checked display and toggle behavior, not full linguistic quality

Automatic safeguards and remaining human checks

Automatic safeguards and remaining human checks
SafeguardAutomatic protectionRemaining limitation
Structural parityIngredient, step, and sub-recipe counts must matchA wrong phrase can still occupy the correct position
Quantity and unit preservationNumeric quantities and canonical units must equal the source after mergeThe system does not prove that the original source quantity was sensible
Empty or untranslated outputRequired fields cannot be empty and most user-facing fields must differ from the source languageShared words, names, and culinary loanwords still need context
Semantic fidelityPrompt rules prohibit added actions, temperatures, ingredients, and adviceThere is no automatic semantic judge; review is still required before cooking
StalenessA source fingerprint prevents an old translation from being treated as current after the recipe changesA changed source needs a fresh translation
AttributionAuthor and source remain base-recipe fieldsTranslation cannot recover attribution that was missing during import

Translate the words, preserve the recipe contract

A reliable recipe translation changes the reader-facing language while keeping the recipe's quantities, canonical units, structure, author, and source anchored to the original. Converting cups to grams or changing serving size is a separate operation and should never be counted as translation quality.

Automated structural checks reduce silent damage, but they cannot certify every culinary phrase. Review the original beside the translation before cooking, especially for allergens, preservation methods, temperatures, timings, regional ingredient names, and unfamiliar techniques.