Calculating Nutrition Facts From a Recipe: Yield, Moisture Loss, and Database Lookup

Turning a kitchen recipe into a Nutrition Facts panel starts with a deceptively simple idea: look up each ingredient, multiply by the amount used, divide by servings. In practice, the calculation breaks down at three points that most guides skip—yield factors, moisture loss during cooking, and choosing the right database entry. Get these wrong and your declared values will drift outside FDA compliance tolerances.

This walkthrough covers the full calculation pipeline from raw ingredients to label-ready values, with the adjustments that separate a rough estimate from a defensible nutrition analysis.

The Base Calculation: Ingredient-Level Nutrition Summation

Every recipe nutrition calculation follows the same core formula:

Nutrient per serving = Σ(ingredient nutrient per 100g × ingredient weight in grams ÷ 100) ÷ number of servings

This means you need three things for each ingredient:

A reliable nutrient composition value—typically per 100 grams of the ingredient as purchased
The exact weight in grams used in the recipe (not volume measures)
The serving count for the finished product, based on the RACC-determined serving size

Volume-to-weight conversion is the first place errors creep in. A “cup of flour” can weigh anywhere from 120g to 160g depending on how it was measured. For any product destined for a Nutrition Facts panel, weigh every ingredient on a gram scale.

Choosing the Right Database Entry

The USDA FoodData Central database contains nutrient data for over 300,000 foods. It consolidates several legacy databases:

Foundation Foods: Analytically determined nutrient values for minimally processed foods. Highest accuracy. Use these when available.
SR Legacy (Standard Reference): The historical USDA dataset, now folded into FoodData Central. Still the most commonly referenced source in labeling software.
Branded Foods: Nutrient data from manufacturer labels. Useful for processed ingredients where the generic SR entry does not match your specific supplier.
Survey Foods (FNDDS): Designed for dietary intake surveys. These often include mixed dishes and may not map cleanly to individual ingredients.

Matching Ingredients to Database Entries

The most consequential decision in recipe nutrition analysis is selecting the correct database entry for each ingredient. Common pitfalls:

Raw vs. cooked entries: If you add chicken breast to a recipe raw and then cook it, use the raw entry and apply yield/retention factors (covered below). Do not use a “cooked” entry with the raw weight.
Drained vs. undrained: Canned beans, tuna, and vegetables have different nutrient profiles depending on whether the liquid is included. Match the database entry to how you actually use the ingredient.
Brand-specific ingredients: A generic “soybean oil” entry may differ from your specific supplier’s product. If your supplier provides a spec sheet with nutrient data, use that—it is more accurate than a generic database entry for your formulation.
Fortified vs. unfortified: Flour, milk, cereals, and other staples exist in both fortified and unfortified forms. Using the wrong entry can significantly skew vitamin and mineral declarations.

Yield Factors: Accounting for Weight Change During Cooking

When you cook a recipe, the finished weight rarely equals the sum of raw ingredient weights. Moisture evaporates, fat renders out, and some product is lost to the pan or equipment. The yield factor accounts for this:

Yield factor = finished weight ÷ raw ingredient weight total

Why this matters for nutrition: nutrients that are not lost during cooking (minerals, most macronutrients) become more concentrated in the finished product. If 1,000g of raw ingredients yield 750g of finished product, and those ingredients contributed 50g of protein total, the protein concentration per gram of finished product is higher—because the protein is now distributed across less mass.

How to Calculate Yield

Weigh all raw ingredients combined (or sum individual weights): this is your raw weight
Cook the recipe according to your standard process
Weigh the finished product: this is your cooked weight
Calculate: yield % = (cooked weight ÷ raw weight) × 100

Example: A soup recipe uses 1,200g of raw ingredients and yields 950g after simmering. Yield = 79.2%. The 250g difference is primarily water evaporation. Since water contributes no nutrients, the nutrient density per gram of finished soup is higher than per gram of raw ingredients.

Applying Yield to Per-Serving Calculations

Once you know the yield weight, determine servings per container by dividing the finished weight by the RACC-based serving size. Then divide total recipe nutrients by the number of servings.

Do not calculate servings from raw weight. A recipe that starts at 1,200g raw but yields 950g cooked produces fewer servings than the raw weight would suggest.

Moisture Loss: The Silent Accuracy Killer

Moisture loss is the single largest source of calculation error in cooked products. Water has zero nutrient value, so when it evaporates during cooking, every remaining nutrient becomes more concentrated per gram of finished product.

The practical impact varies by product type:

Product Type	Typical Moisture Loss	Impact on Nutrient Density
Baked goods (bread, muffins)	10–15%	Moderate concentration increase
Roasted meats	20–40%	Significant concentration increase
Soups and stews	5–20%	Mild to moderate
Dehydrated/dried products	60–90%	Dramatic concentration increase
Fried foods	Variable (fat absorption offsets water loss)	Complex—fat gain partially compensates water loss

For fried foods, fat absorption complicates the calculation further. The finished product may weigh close to the raw weight, but the composition has shifted: water left, fat entered. You need to account for both the moisture loss and the fat gain separately.

Nutrient Retention Factors: What Cooking Destroys

While macronutrients (protein, fat, carbohydrates) and minerals survive cooking largely intact, vitamins degrade at different rates depending on the cooking method, temperature, and duration. The USDA Table of Nutrient Retention Factors (Release 6) provides retention percentages for 16 vitamins, 8 minerals, and alcohol across approximately 290 food items and cooking methods.

Key retention patterns:

Vitamin C: Highly heat-sensitive. Retention ranges from 50–80% for most cooking methods. Boiling causes additional loss through leaching.
Thiamin (B1): Moderate heat sensitivity. Retention typically 60–90% depending on cooking method and pH.
Folate: Heat and water sensitive. Retention 50–80% for most cooking methods.
Fat-soluble vitamins (A, D, E, K): Generally stable during cooking. Retention 80–100% for most methods.
Minerals (iron, calcium, sodium, potassium): Not destroyed by heat, but can be lost through leaching into cooking water that is discarded.

When Retention Factors Matter for Label Compliance

For most macronutrient-focused labels (calories, fat, protein, carbs, sodium), retention factors have minimal impact—these nutrients are stable through cooking. Retention factors become critical when:

Your product makes a nutrient content claim involving a vitamin (e.g., “excellent source of Vitamin C”)
You are declaring voluntary vitamins on the Nutrition Facts panel
Your product is a fortified food where vitamin declarations are mandatory

If you are only declaring the mandatory nutrients (calories, fat, saturated fat, trans fat, cholesterol, sodium, total carb, dietary fiber, total sugars, added sugars, protein, Vitamin D, calcium, iron, potassium), retention factors primarily affect Vitamin D. The other mandatory nutrients are macronutrients or minerals that survive cooking.

Multi-Level Recipes: Sub-Recipes Within Recipes

Real manufacturing formulations are rarely flat ingredient lists. A frozen meal contains a sauce, which contains a spice blend. Each sub-recipe has its own yield factor, and the nutrition calculation must cascade correctly:

Calculate nutrition for the innermost sub-recipe (the spice blend), including its yield
Treat that finished sub-recipe as a single ingredient in the next level up (the sauce)
Calculate the sauce nutrition including its own yield
Treat the finished sauce as a single ingredient in the final product (the frozen meal)
Calculate final product nutrition with the finished product yield

Each level must use the cooked/finished nutrient profile from the level below, not the raw ingredient sum. This is where spreadsheet-based calculations typically fail—maintaining cascading yield factors across three or more recipe levels without errors requires careful version control of each sub-recipe.

Database Analysis vs. Lab Testing: When Each Makes Sense

Database-calculated nutrition analysis is sufficient for most formulation iterations and is accepted by the FDA for labeling purposes. However, the FDA enforces compliance using laboratory analysis, and labels must fall within compliance tolerances:

Nutrients to limit (fat, saturated fat, cholesterol, sodium, sugars): Declared value must not be exceeded by more than 20% on lab analysis
Nutrients to encourage (fiber, protein, vitamins, minerals): Lab analysis must not fall below 80% of declared value
Calories: Lab analysis must not exceed declared value by more than 20%

Database analysis works well when you use high-quality database entries that match your actual ingredients. It becomes risky when your recipe contains ingredients with high natural variability (seasonal produce, artisan cheeses, wild-caught seafood) or when your cooking process introduces significant and variable nutrient changes.

Lab testing ($500–$1,500 per product) is worth the cost for final label validation before a production run, especially for products making nutrient content claims or products with high ingredient variability.

The practical workflow: iterate with database analysis during formulation, validate with lab testing once the recipe is finalized, and re-test when ingredients or processes change significantly.