General information, not medical or dietetic advice. The protein figures below are worked examples built from raw-ingredient values; real dishes vary with recipe, portion and preparation. Consult a qualified professional before changing how you eat.
Ask someone who trains in Mumbai or Bengaluru how much protein they ate yesterday and you will usually get one of two answers: a confident number, or a shrug. The confident number is often wrong, and not because the person is careless. It is wrong because Indian home food is a macro black box.
Here is the problem in one sentence: the foods that dominate an Indian plate are among the hardest to measure. A packaged diet is built from labelled, portioned units: a chicken breast weighs what the pack says, a slice of bread is a slice of bread. An Indian meal is built from preparations. Dal is water, lentils, oil and a tadka in a ratio that changes from kitchen to kitchen. A roti's weight depends on how the dough was rolled. Sabzi hides paneer, oil and cashew paste inside a single ladle. None of it arrives with a number on it. So when a fitness app asks you to "log your meal", the honest answer is that most people are estimating, and protein is the number that is easiest to overestimate.
Why the dal-and-roti plate looks richer than it is
Protein is the macro people who train care about most, and it is the one most easily inflated in the head. A katori of everyday dal is often mentally filed as "loads of protein". The raw lentils are genuinely protein-dense: the Indian Food Composition Tables 2017 list raw red gram (toor) dal at about 21.7 g of protein per 100 g. But a home katori is mostly water, and the lentils in it may be only a modest share of what you serve.
A worked example, clearly illustrative: if one katori is cooked from about 30 g of raw toor dal, it carries roughly 6.5 g of protein. Two rotis made from about 40 g of atta (listed at about 10.6 g of protein per 100 g in the same tables) add roughly 4 g more. That is around 10 g for a plate many people would describe as protein-rich. Your own numbers will differ, which is exactly the point: without weighing the raw dal once, you cannot know.
The foods that tend to move the total are the ones people under-serve. The IFCT lists paneer at about 18.9 g of protein per 100 g and a whole boiled egg at about 13.4 g per 100 g; soybean, curd, rajma and chana are other everyday options. Add a plate up honestly and a "high-protein" thali can land well under what its eater believed. The gap stays invisible precisely because nothing on the plate was ever weighed. For a wider list, see our guide to protein per 100 g in Indian foods.
None of this is an argument to abandon Indian food for boiled chicken and oats. It is an argument to measure it. The fix is not exotic. It is a method, and it takes only a little attention to build the habit.
A four-step method to count it
1. Learn five portions, not fifty foods
You do not need to memorise a database. You need reference weights for the handful of things you eat constantly: your katori of dal (and how much raw dal goes into the pot), your usual roti, one standard serving of rice, a serving of paneer, one egg. Weigh them once on a kitchen scale. After that, estimating the rest becomes far easier. If you have no scale, the hand-portion method for Indian plates is a reasonable starting point, and it is worth knowing why "2 rotis" is not one number.
2. Anchor to a real reference, not vibes
India has a public, credible source: the Indian Food Composition Tables, published by ICMR's National Institute of Nutrition in Hyderabad. The 2017 edition covers 528 key foods, analysed from samples averaged across six regions of the country, and the full PDF is free to download. One detail matters for home cooks: apart from eggs, its values are for foods in the raw form. It tells you what is in 100 g of raw dal or atta, not in a cooked katori or a restaurant curry. So the reliable way to use it is to work from your recipe: weigh the raw ingredients going into the pot, then divide by the portions you serve. When an app or a website disagrees sharply with the tables for a plain ingredient, trust the tables. For mixed and restaurant dishes, accept that any number is an estimate and round conservatively.
3. Track the macro that hides, then close the gap deliberately
Once you can see your real protein intake, the fix is usually one or two swaps, not a diet overhaul: a bowl of curd after lunch, paneer instead of a second helping of sabzi, eggs at breakfast, soya in the evening meal. Small, specific, repeatable. How much you need depends on your body weight and goals; our piece on how much protein per day to build muscle covers that question.
4. Adjust weekly, not daily
A single day tells you very little: travel, a wedding or a skipped meal all distort it. A week of honest logging gives you a far more useful picture. Look at the weekly average, make one change, and check again the following week.
Where NYUS fits
I have a stake in this problem, so let me be plain about it: I build NYUS, an AI fitness and nutrition coach designed for Indian food, and this gap is the reason it exists. NYUS has macros for 9,000+ Indian and global dishes, so that "a katori of dal" resolves to a number rather than a guess, and meals can be logged by photo, barcode or search. The coach reads your logged data each week before it adapts the next week's plan, which is the same weekly-average logic described above, automated. NYUS is currently in early access.
But you do not need our app, or any app, to start. A kitchen scale, five reference portions and the IFCT will get you most of the way. The point is not the tool. The point is that you cannot coach what you cannot count, and for Indian eaters, counting has always been the hard part.
The black box is only black because nobody opens it. Open it once, and your protein stops being a mystery.