Last reviewed on 11 September 2026.
NNWA publishes the name and qualifications of everyone who writes and checks its material. You can see the full teaching team on the faculty page.
What follows explains where the errors creep in and how to use an app so the numbers remain useful rather than misleading.
Do calorie counting apps work for Indian food?
Partly. For packaged foods with a barcode, fruit, eggs, plain milk and measured servings of rice or oats, a good app is accurate enough to be useful. The trouble starts with the cooked dishes that make up most Indian meals, where one name can cover very different recipes. Research comparing self-reported intake with energy use measured by the doubly labelled water method has repeatedly found that people under-report what they eat, and apps do not remove that tendency. What apps do is make logging easier, which helps people notice patterns, and that awareness is where most of the benefit lies.
Why are app entries for Indian dishes so inconsistent?
Because many entries are typed in by users rather than checked by the app's own team. Search for aloo paratha and you may find a long list of versions whose calories differ by a factor of almost two, often with no note of size, filling or fat. Some apps lean heavily on these crowd-sourced entries; others draw on curated laboratory databases, which are more reliable for single ingredients but thin on Indian dishes. When choosing an entry, prefer one that states a weight in grams and gives protein, carbohydrate and fat figures that look plausible, and distrust any entry built from suspiciously round numbers.
Why is home cooking so hard for an app to log?
Because a home dish is a recipe, not an item. A katori of dal might be a thin toor dal with a teaspoon of ghee in the tadka, or a thick dal makhani finished with butter and cream, and both get logged simply as dal. Sabzi changes with the vegetable, the oil and how long it is cooked down. Rotis vary with the atta, the size and whether they are brushed with ghee. The honest workaround is to enter your family recipes once, weighing the raw ingredients and the finished pot, so the app divides a known total instead of guessing from a generic entry.
How much do oil and ghee change the count?
More than most people expect. One teaspoon of oil, about 5 ml, adds roughly 40 to 45 kcal, and a tablespoon adds about 120. Ghee is similar, while butter is a little lower because it contains some water. A sabzi cooked with two tablespoons of oil for a family of four carries around 60 kcal of oil in each share, and restaurant curries often carry far more. Because the fat disappears into the dish, apps rarely capture it well. Many dietitians ask clients to log cooking oil as a separate daily item, measured from the bottle, which is usually more accurate than guessing the fat in each dish.
| What goes into the pan | Roughly what it adds |
|---|---|
| One teaspoon of oil, about 5 ml | 40 to 45 kcal |
| Ghee, spoon for spoon | much the same as oil |
| Butter | a little lower, since it holds some water |
| Two tablespoons in a sabzi for a family of four | about 60 kcal in each share |
Restaurant curries often carry far more. Because the fat vanishes into the dish, logging oil from the bottle as one daily item beats guessing at each dish.
How big is a katori, really?
There is no standard size. Household katoris range from small bowls holding about 100 ml to larger ones of 200 ml or more, and an app's bowl might assume either. Rice served in a heaped katori can weigh nearly twice what a level one does. The fix takes one afternoon: fill your own katoris, serving spoons and ladles with water or cooked food, measure or weigh them, and write the numbers down. After that, one katori in your log means something specific. The Indian food calorie chart gives common portion values to compare against.
Can photo recognition apps identify Indian food?
They can often name the dish, but they cannot see the oil, the ghee or how much food sits under the top layer. Photo logging has improved, and for a plate of idli with chutney it may guess reasonably well. Mixed thalis, gravies and layered dishes such as biryani are harder, and portion estimates from a single picture carry wide errors because depth and bowl size are hard to judge from above. Treat a photo estimate as a starting point that you then correct, particularly for the portion, rather than as a measurement.
Which regional foods do apps tend to miss?
Anything outside the few dozen dishes found on restaurant menus. Northeastern preparations, Konkani and Malabar recipes, millet dishes from tribal and rural kitchens, Bengali everyday food such as shukto or chorchori, and home-style Rajasthani or Odia cooking are often absent or represented by one dubious entry. For these, building the dish from its ingredients is usually more accurate than choosing the nearest named item. Ingredient values from IFCT 2017, the Indian Food Composition Tables published by ICMR-NIN, are the most dependable base for that work.
How do you use a calorie app well?
Weigh your food for a week or two, not forever. A basic kitchen scale teaches you what 150 g of cooked rice or 30 g of nuts looks like on your own plate, and that calibration lasts. Create your regular home recipes as custom entries. Log oil and ghee separately. Choose entries that state a gram weight. Record meals soon after eating rather than at night from memory, and include the tea, biscuits and tastes taken while cooking. Check that protein and fibre are adequate, not only the calorie total.
Using an app so the numbers stay useful
Weigh food for a week or two, not forever
A basic kitchen scale teaches you what 150 g of cooked rice or 30 g of nuts looks like on your own plate, and that calibration stays with you afterwards.
Measure your own katoris once
Fill your bowls, serving spoons and ladles, write the numbers down, and after that one katori in the log means something specific.
Build your regular dishes as custom recipes
Weigh the raw ingredients and the finished pot, so the app divides a known total instead of guessing from a generic entry.
Log oil and ghee separately, from the bottle
It is the biggest uncounted variable in a home kitchen, and the one an app captures worst.
Log soon after eating rather than at night
Include the tea, the biscuits and the tastes taken while cooking, which are the entries memory drops first.
Read the week, not the day
Check that protein and fibre are adequate rather than the calorie total alone, and set the weekly average against your weight trend.
Should you track exact numbers or trends?
Trends. Even careful logging carries an error of a few hundred calories on some days, so agonising over whether you ate 1,640 or 1,710 kcal is wasted effort. What matters is whether your average intake across a week or two is roughly steady, and how it lines up with your weight trend, waist measurement and energy levels. Weigh yourself at the same time of day and look at the weekly average, since daily weight swings with water and salt. If the trend has not moved the way you want after three or four weeks, adjust a little. The post on calorie deficits explains the arithmetic behind that.
When should you stop counting calories?
Once the app has taught you what it can. For many people, a few weeks to a few months of tracking builds a working sense of portions, and after that an occasional check of a typical week is enough. Stop sooner if logging makes you anxious, if you start avoiding family meals because they are hard to record, or if a number on a screen leaves you feeling guilty. The aim is a steady way of eating that no longer needs an app, not permanent surveillance of every mouthful.
Who should not count calories at all?
Anyone with a current or past eating disorder, including anorexia, bulimia and binge eating disorder, should not track calories unless their treatment team specifically advises it. Surveys of young adults have linked tracking apps with more disordered eating symptoms, although such surveys cannot show which came first. Children and teenagers should not be put on calorie counts by their parents. Pregnant women, people with diabetes who take insulin or sulfonylureas, and anyone with kidney disease should agree any calorie or carbohydrate target with their doctor first, since eating less can affect medicine doses and nutrient needs.
What do nutritionists look for in an app?
A large Indian dish library with sensible, gram-based entries. The ability to build recipes and save your own katori sizes. Protein, fibre and a few micronutrients shown alongside calories. Targets that are not set aggressively low, since some apps suggest deficits that few people can sustain. A way to share or export a food log with a practitioner, so a week of real eating can be reviewed together. Clear privacy terms, because food logs and weight data are personal health information. None of these features makes an app right for everyone, and the most useful one is whichever you will fill in honestly.
A quicker option for looking up single foods
If you only want to check a meal now and then rather than log every day, NNWA's free Indian food calorie counter lets you build a plate from about forty everyday Indian foods in household measures such as chapatis, katoris and cups, then totals the estimate. There is no sign-up and no daily diary to keep. It assumes a standard 150 ml katori, which is why the measuring exercise above is worth doing first. It is handy for quick comparisons, such as a single chapati against a paratha, though its figures for cooked dishes assume typical recipes, so allow for the oil used in your own kitchen.
The honest summary
Calorie apps are rough instruments for Indian food, not useless ones. They are most accurate for packaged items and least accurate for home-cooked mixed dishes, where oil, ghee and katori size quietly move the numbers. Weigh a few meals, build your own recipes, log fat separately, watch the weekly trend and stop when the habit has done its job. If tracking feeds anxiety or an eating disorder history, skip it and look for support from a person instead of a phone.