Account

What new tool do you want?

Cooking & Food

Recipe Nutrition Calculator (Calories & Macros per Serving)

Paste a recipe's ingredients and get calories, protein, fat, carbs, fiber, sugar and sodium for the whole recipe and per serving — using USDA nutrition data for 7,700+ foods, with cups and spoons converted by each food's real weight.

How to use

  1. 1Paste ingredients one per line, e.g. “2 cups all-purpose flour” or “150 g chicken breast”.
  2. 2Check each matched food and pick a better match from the list if needed.
  3. 3Enter the number of servings to see nutrition per serving.

Frequently asked questions

Where does the data come from?

USDA FoodData Central (SR Legacy), the standard US reference database. Values are for the food as described (raw or cooked) — choose the matching form for accuracy.

How are cups converted to grams?

Using USDA's measured portion weights for that food (a cup of flour weighs about 125 g, a cup of sugar about 200 g). If a food has no cup weight, we assume the density of water and show a warning.

Does cooking change the numbers?

Calories mostly don't change, but weight does (water loss), and some vitamins drop. Use raw ingredients for raw weights, or cooked entries if you weigh after cooking.

Sources

Why confirming the matched food matters more than it seems

Typing '2 cups flour' requires the tool to decide which specific food entry in a 7,700+ item USDA database 'flour' actually refers to — all-purpose, whole wheat, bread flour and self-rising flour all have meaningfully different nutrition profiles, especially fiber and protein content. The howTo's instruction to check each matched food and pick a better match if needed exists exactly because an automatic match on an ambiguous ingredient name can silently pick the wrong specific food, which would make every downstream nutrition number for that ingredient wrong even though the rest of the calculation ran correctly.

Worked example: Recipe Nutrition Calculator

Entering '150 g chicken breast' matches directly to a USDA entry by weight — no conversion needed since the amount is already in grams. Entering '2 cups all-purpose flour' instead requires converting a volume measurement to weight using USDA's own measured portion data for that specific food (about 125 g per cup for flour), which is a different and more involved calculation than the direct-weight chicken example — and this per-food conversion is exactly why the FAQ specifically calls out using each food's real measured weight rather than a single generic cups-to-grams assumption.

Why a missing cup-weight triggers a warning instead of a silent guess

When a specific food in the database has no recorded cup-weight measurement, the calculator falls back to assuming the density of plain water (1 cup ≈ 236.6 g) rather than silently proceeding as if that estimate were as reliable as an actual measured value — and it surfaces a warning specifically so you know that particular ingredient's quantity is a rougher approximation than the others in the same recipe, worth double-checking or re-entering by weight instead of volume if precision matters for that ingredient.

Why raw versus cooked entries aren't interchangeable for the same ingredient

The FAQ's guidance to match the ingredient's actual state (raw or cooked) to the matching database entry reflects a real measurement problem: cooking changes an ingredient's weight substantially through water loss, so 100g of raw chicken breast and 100g of cooked chicken breast represent different amounts of actual chicken, with different concentrations of calories and protein per gram even though calories from the food overall mostly don't change during cooking. Weighing a cooked ingredient but matching it against a raw-food database entry — or vice versa — introduces exactly the kind of systematic error that makes final per-serving numbers meaningfully inaccurate without any single step having an obvious mistake in it.

Related tools

More: Cooking & Food