How to count calories in home-cooked food

Calorie apps were built around packaged food, where a barcode gives one exact answer. Most people, most of the time, eat food that came out of a pot in their own kitchen — and a pot has no barcode, no label, and no single correct calorie count.

This is the guide to doing it properly anyway. It is not harder than logging packaged food. It is front-loaded differently: a little work per recipe, almost none per meal.

Why database entries for home dishes are unreliable

Search "dal" in a large calorie app and you will find dozens of entries with values spanning a factor of four. They are not lying. They are describing different dals.

A dal is lentils plus water plus whatever fat, cream and tempering the cook used. Lentils are cheap in calories. The fat is not. Two cooks making "the same" dal can differ by 500 kcal for the pot, and the database entry someone typed in reflects their kitchen rather than yours.

The bias runs one way: entries tend to assume less oil than home kitchens actually use, which is why home-cooked food logged from a generic entry typically reads 25 to 40 per cent low. Full detail in why two apps give the same roti different calories.

The method: log the pot, not the plate

Four steps, done once per recipe.

1. Count what goes in. Weigh the raw ingredients. Two hundred grams of toor dal, one onion, two tomatoes, three tablespoons of oil, a teaspoon of ghee for the tadka. Spices and salt are nutritionally negligible.

2. Total it from a composition table. Use published reference values for ingredients — this is the one place where the data is genuinely good, because a lentil is a lentil. See IFCT or USDA: which numbers should you trust.

3. Divide by the servings it really made. Not the number the recipe claimed. If it filled six katoris, divide by six.

4. Save the number. "My dal, one katori = 185 kcal." Reuse it forever.

A full worked example is in how to calculate the calories in a recipe you cooked.

The oil is the whole problem

If you take one thing from this article: measure the fat going into the pan.

Oil and ghee carry about 9 kcal per gram — more than twice protein or carbohydrate — and they become invisible the moment they hit the food. A tablespoon is roughly 120 kcal.

Here is what that does to a typical dish.

खाना	मात्रा	कैलोरी	प्रोटीन (ग्राम)	कार्ब्स (ग्राम)	फैट (ग्राम)
Dal, 1 tsp oil	1 katori (150 g)	118	7	18	2
Dal, 2 tbsp oil	1 katori (150 g)	158	7	18	6
Dal, 4 tbsp oil + ghee	1 katori (150 g)	205	7	18	11

स्रोत: Calculated from IFCT 2017 ingredient values

Same lentils, same water, same spices. The gap between the first and third row is 87 kcal per katori, and a household eating two katoris a day would differ by 174 kcal daily — which is most of a typical deficit. How much oil is actually in your curry goes through this dish by dish.

Raw or cooked: pick one and stay there

Rice roughly triples in weight when boiled. Dal does something similar. Meat loses a quarter when roasted.

Weigh raw and log raw wherever you cook it yourself, because raw weight is reproducible and cooked weight depends on your lid and your patience. The conversion factors and the exceptions are in should you weigh food raw or cooked, and what cooking does and does not change is covered in does cooking change the calories in your food.

Household servings beat grams at the table

Nobody weighs dal at dinner, and a method that requires it will be abandoned by the second week.

Spend twenty minutes once. Weigh your katori of dal, your roti, your rice serving, your oil spoon, your curd bowl. Write the grams down permanently. From then on you log in bowls and pieces while the numbers behind them stay honest.

That is what a household serving is, and it is why tracking calories without a food scale is entirely practical once the calibration is done.

Build a library of twenty dishes

Here is what makes this sustainable rather than exhausting.

Most households cook from a repertoire of fifteen to twenty-five dishes. Do one or two a week. After two months, almost everything you eat regularly has a saved per-serving number that came from your own kitchen.

At that point logging dinner is recall: two roti, one katori dal, half a plate of sabzi, curd. Four taps, every number yours. Compare that with searching a database at every meal and choosing between eleven strangers' guesses.

What to do when someone else cooks

At a parent's or a relative's house you have no ingredient list. Ask one question — how much oil went in — because that single answer resolves most of the uncertainty, and people are generally happy to tell you.

Then match it to the closest dish in your own library and add a margin. The approach for shared and family food is in tracking calories when one pot feeds four people, and for the leftovers afterwards, how to log leftovers and second helpings honestly.

The dishes with their own numbers

Some foods come up so often they are worth knowing cold. Each of these has its own article with the ranges and what drives them:

roti, dal, rice, paneer, chicken curry, biryani, dosa and idli, poha and upma, ghee and tadka, snacks, sweets, chai, curd and dairy, and a whole thali.

How accurate is this, honestly

Within about 15 per cent if you count your own ingredients and are honest about the fat. That is roughly as good as a packaged food label, which carries a legal tolerance of about 20 per cent.

It is also enough. A log does not need to be correct; it needs to be consistently wrong in the same direction, so that your weekly weight change supplies the calibration. That is the argument in how accurate are calorie counts, really, and it is why home cooking is a solvable problem rather than a reason to give up on tracking.