How accurate is this?
Short answer: the calories per serving are typically within about 10–15% for a normal home recipe, and the ranking of two recipes against each other is far more reliable than either absolute number.
That is genuinely useful for “is this a 400 or an 800 calorie dinner” and for “does swapping to whole wheat actually add much fibre”. It is not precise enough to count grams against a medical target without checking the specifics.
Here is what moves the numbers, roughly in order of impact.
One worked example, with real numbers
An abstract “10–15%” is hard to argue with and hard to use, so here is a real one. A plain cake: 200 g flour, 100 g butter, 100 g sugar, 2 eggs. Run through this calculator it comes to 1,975 kcal for the whole thing.
Now the three ways that becomes a wrong per-serving number:
- Divided by 4: 494 kcal a slice. Divided by 8: 247. Neither is wrong — they are the same cake — but the serving count is the whole difference, and it is a setting rather than a fact. This is the biggest error on the page and the one entirely in your hands.
- The flour by volume. A cup of plain flour is 125 g levelled and about 150 g if you scoop it straight from the bag and pack it. That is 455 kcal against 546 — a 20% error on that one ingredient, before anything else happens. Weighing it removes the error completely.
- The wrong tin. 400 g of fresh tomatoes is 72 kcal and 20 mg of sodium; 400 g of canned is 128 kcal and 744 mg. Same weight, same word on the page, thirty-seven times the sodium. This is why the selected ingredient on each row is worth a glance — it is the line every number came from.
None of those three is a flaw in the arithmetic. They are the reasons the arithmetic is being given the wrong input, and all three are visible and correctable on the results page.
1. How you divide it — up to 100% error
This is by far the biggest one, and it is the only one entirely in your hands. A lasagne written for six that two people finish over a weekend is a three-serving lasagne. Every number on the page doubles.
Recipe authors are also optimistic. “Serves 4–6” usually means four adults or six people who are also eating something else. When the recipe states a range, this calculator takes the lower number, which never understates a portion.
Fix: weigh the finished dish once, then divide by what you actually plate up.
2. Cooking losses and gains — 0 to 30%
Nutrient data is for the ingredient as listed, usually raw. Cooking changes the weight, and sometimes the nutrition:
- Water loss. A 150 g raw chicken breast is about 110 g cooked. The calories are the same; the calories per gram rise by a third.
- Fat loss. Grilling or draining mince removes a meaningful part of its fat. Browning 500 g of 15%-fat mince and draining it can remove 20–30 g of fat — about 200 kcal off the recipe.
- Fat gain. Deep frying adds oil that no ingredient list mentions. Batter can absorb 10% of its weight.
- Discarded liquid. Pasta water, blanching water and brine take some minerals and water-soluble vitamins with them.
- Marinades. Most of a marinade goes in the bin, but the whole thing is in the ingredient list.
Fix: delete or reduce ingredients that do not end up on the plate. If you drain the fat off mince, switch to a leaner mince entry to approximate it.
3. Volume-to-weight conversion — 5 to 25% on that ingredient
Cups measure space, not mass, and how a food packs varies a lot. A cup of flour is 120 g scooped lightly and 150 g if you pack the cup — a 25% swing on the single biggest ingredient in most baking.
Volume conversions here use per-ingredient weights (flour 125 g/cup, sugar 200 g/cup, honey 339 g/cup) rather than a single density, which removes most of the error. What is left is how you fill a cup.
Fix: if the recipe gives grams, use grams. Where a volume or a count could not be converted honestly — an unknown unit, an informal measure like “a glug”, a food with no per-item weight on record — the row is tagged est. weight and says what the guess was based on. A cup of flour is not tagged, because 125 g to the cup is a real figure for that food rather than a guess about it.
4. Ingredient variation — 5 to 20%
“Chicken breast” is a range, not a value. So is an onion, an apple, and especially anything branded. Bread, stock cubes, sauces and plant milks vary enormously between products — sodium in particular can differ threefold between two brands of the same thing.
USDA figures are averages across samples, which is the right choice for a generic recipe but will not match a specific packet.
Fix: for anything where the brand really matters — protein bars, sauces, plant milk, stock — read the label and enter the numbers you actually have. Scanning the panel reads it off a photograph, so you do not have to type fifteen numbers; and how it works sets out where every figure on this site comes from.
If you would rather see the machinery than take our word for any of this, how it works goes through the parsing, the matching and the unit conversion in order, and the guides cover reading a nutrition breakdown and which swaps actually change the numbers.
What this gets right
- Comparisons. Both versions of a recipe carry the same assumptions, so the difference between them is much more accurate than either total.
- Ratios. The macro split, and the share of calories from saturated fat, barely move with weight errors.
- Ranking contributors. “Most of the salt is the soy sauce” is reliable even when the absolute figure is not.
What it does not do
- Model cooking losses automatically.
- Know brand-specific values without you entering them.
- Account for glycaemic response, bioavailability, or how a food actually affects you.
- Constitute medical or dietary advice. If you are managing a condition, use this to explore and take the specifics to a professional.