How to count calories in homemade food

The method, in four steps#

Log every ingredient raw, by weight, as you put it in.
Weigh the finished dish — pan and all, then subtract the empty pan. Or weigh it into a container you have already weighed.
Weigh your own serving.
Your share is your serving ÷ the finished weight. Multiply the totals by that fraction.

That is the whole thing. Six portions of a stew is a guess; 340 g out of a 1710 g pot is a measurement.

Why weigh the dish rather than count portions#

Because portions are not equal and nobody serves them equally. “Serves four” is a number written by someone who has not met your household, and the person who plated it did not use a scale.

Weighing the finished dish also handles the thing that makes recipes hard: water leaves during cooking. A stew reduces. Rice and pasta absorb. Vegetables shed liquid. The calories do not change — water carries none — but the weight does, so any “per 100 g cooked” figure depends on how long you cooked it. Working from the finished weight of your pot sidesteps the problem entirely.

Raw or cooked?#

Log ingredients raw wherever you can, because raw weights are stable and label data is usually per raw 100 g. 100 g of dry pasta is always 100 g of dry pasta; 100 g of cooked pasta depends on the cook.

If you only have the cooked item — someone else made it, or you forgot to weigh first — use a cooked database entry and accept the wider error. It is better than not logging.

The things that catch people out#

Cooking oil. The most commonly omitted ingredient in home cooking and one of the densest. A tablespoon is around 120 kcal. Two tablespoons in a pan that feeds four is 60 kcal a head that nobody logs. Weigh the bottle before and after if you are pouring by eye.

Marinades and coatings that stay behind. If half the marinade is left in the dish, you did not eat half the marinade. Log what went in and accept a small overcount, or weigh the leftovers.

Sauces reduced separately. Same logic — weigh the finished sauce, not the ingredients you started with, if you are serving a portion of it.

Baking. Weight loss during baking is substantial and varies by oven. Weigh the finished loaf or tray and divide.

Saving the result#

Once you have worked out a dish, keep it. In SmartCrunch that is My Recipes: select the ingredients you just logged, give the dish a name, and it is saved with each ingredient’s per-100 g figures rather than one frozen calorie total.

That last detail is what makes it worth doing, because it does step 4 of the method for you. When you log the dish again you type the weight of your serving, and every ingredient rescales by the same fraction — which is exactly “your serving ÷ the finished weight”, done as arithmetic instead of by hand. A stew that came out at 2,140 g on Sunday and 1,890 g on Thursday is the same saved dish at a different weight, not a recount.

Saving and re-logging cost nothing and never call the AI: the numbers are already there, and the app multiplies them. Dishes can be renamed, corrected ingredient by ingredient, or deleted. A dish you have not saved still comes back in Recent and Frequent, and starring it puts it in Favourites — but those repeat a portion you once logged, whereas a saved dish rescales to whatever you served today.

Worth knowing: a meal you typed in yourself carries calories and macros and nothing else. There is no fibre, sodium or saturated fat figure attached, because you did not enter one and the app does not invent them. It reports those as unknown rather than zero, and shows how much of the day the totals were actually computed from — so a week of home cooking will honestly show low coverage on the micronutrients rather than a flattering zero.

When the accuracy is not worth it#

A dish you eat once, at someone else’s house, from a recipe you did not see, is not worth reverse-engineering. Log a reasonable database equivalent and move on. The purpose of the diary is a usable weekly average, and one approximated meal does not damage that. Ten abandoned days do.

Common questions

How do you calculate the calories in homemade food?

Log every ingredient raw, by weight, as it goes in. Weigh the finished dish, then weigh your own serving. Your share is your serving divided by the finished weight, and you multiply the recipe totals by that fraction. Counting portions instead is where the error comes from: six servings out of one pot is a guess, while 340 g out of a 1710 g pot is a measurement.

How do you calculate the nutrition facts for a recipe, not just the calories?

The same arithmetic gives you every figure the ingredients carried — add them across the recipe and scale by your share of the finished weight. The catch is what the ingredients carry in the first place. A barcode or a database entry brings fibre, sodium and saturated fat with it; an ingredient you typed in yourself has calories and macros and nothing else, so a dish built entirely from typed entries has no nutrition facts to calculate beyond those.

How do you figure out the calories in a dish someone else cooked?

You estimate it and accept the wider error. Pick the closest database entry for the cooked dish, weigh or estimate your serving, and log that. Reverse-engineering a recipe you never saw is not worth it for one meal: the diary exists to produce a usable weekly average, and one approximated meal does not damage that. Ten abandoned days do.

Should ingredients be weighed raw or cooked?

Raw wherever you can. Raw weights are stable and label figures are usually per raw 100 g, whereas cooked weight depends on how long it cooked — water leaves a stew and is absorbed by rice and pasta, moving the weight without moving the calories. If you only have the cooked item, use a cooked database entry rather than not logging.