Examples
Examples
Try the starting example
- Ingredients [name,grams,kcal/100g,protein g/100g,carbohydrate g/100g,fat g/100g]; enter JSON
- [["Oats",100,380,13,68,7],["Milk",200,60,3,5,3]]
- Portions (count)
- 4
- Measured finished recipe yield (grams)
- 280
- Total [kcal,protein g,carbohydrate g,fat g] (JSON)
- [500,19,78,13]
- Nutrients per portion (JSON)
- [125,4.75,19.5,3.25]
- Nutrients per 100g finished recipe (JSON)
- [178.571428571,6.78571428571,27.8571428571,4.64285714286]
Try another scenario
- Ingredients [name,grams,kcal/100g,protein g/100g,carbohydrate g/100g,fat g/100g]; enter JSON
- [["Oats",150,380,13,68,7],["Milk",250,60,3,5,3]]
- Portions (count)
- 5
- Measured finished recipe yield (grams)
- 360
- Total [kcal,protein g,carbohydrate g,fat g] (JSON)
- [720,27,114.5,18]
- Nutrients per portion (JSON)
- [144,5.4,22.9,3.6]
- Nutrients per 100g finished recipe (JSON)
- [200,7.5,31.8055555556,5]
Calculation method
Calculation method
Total [kcal,protein g,carbohydrate g,fat g] (JSON)
For each nutrient sum ingredient grams×label per100g/100.
Nutrients per portion (JSON)
Divide each recipe nutrient total by portion count.
Nutrients per 100g finished recipe (JSON)
Each nutrient total×100/measured finished yield.
Symbols and units
- a
- Ingredients [name,grams,kcal/100g,protein g/100g,carbohydrate g/100g,fat g/100g]; enter JSON
- b
- Portions (count)
- c
- Measured finished recipe yield (grams)
Use the units shown. A list keeps the order in which you enter its values. The symbol ^ means “raised to the power of”.
Assumptions & limits
Assumptions & limits
- Label-value recipe arithmetic with no processing nutrient-retention inference or official nutrition-label compliance. Supported limits: All numeric inputs and computed intermediates must remain finite. Supported numeric input magnitude is zero or 1e-12 through 1e12 in absolute value; reject values outside this bounded range. All lists/JSON record tables are limited to 100 records unless a stricter bound is stated; reject malformed record arity and wrong member types. All numeric values must be finite. Lists contain at most 100 records; required lists must be nonempty. Rates, probabilities and fractions are entered as fractions, not percentages; fractions must be between 0 and 1. Use a single consistent user-selected currency for all amounts; no exchange-rate conversion.
Are these inputs private?
These calculations run in your browser. A shared link contains the values you choose to share. Only questions submitted to the separate AI finder are sent to OpenAI.