Key takeaways
- A dal, a curry or a biryani is a dish, not a food: its calories depend on the recipe, the fat it was cooked in and the portion, and a database entry fixes all three for somebody else's kitchen.
- Two things carry most of the calories in an Indian meal: the ghee or oil, about 115 kcal a tablespoon, and the weight of rice, dal and bread on the plate.
- The honest record says what the dish was, about how much, and what it was cooked in, and marks the result as an estimate; a packet roti or a paneer block is a label, read as printed.
- A dish cooked in a pot for the family is recorded from its ingredients once, weighed raw, divided by the portions; the assistant does the arithmetic, and the record says whether the figure was yours or reasoned.
- IZeat has no Indian food database and no built-in food database of any kind today: you describe the dish to the assistant you already use, its protocol asks for what a plate cannot show, and IZeat records each item with its source.
Why can a food database get an Indian dish wrong?
Because they store foods, and Indian cooking serves dishes. A database entry for dal is one recipe, one amount of ghee, one portion, typed by someone with their own pot in mind. Your dal was tempered differently and ladled from a shared bowl. The entry is not wrong; it is somebody else's dinner, and picking it records theirs instead of yours.
That is the general complaint about crowd-sourced databases: "Same food, ten results, ten calorie counts" (reviews of MyFitnessPal, read 4 September 2026). It bites harder on a cuisine where the same name covers a dozen recipes, where ghee is added by the spoon at the end, and where rice, dal and bread are served from the middle of the table rather than by the plate. Some apps carry large Indian entries and some people are served well by them; this page is for the person who is not.
What follows is not a better database. It is the other way to get a figure: describe the dish as it was made, answer what a plate cannot show, and record an estimate that says it is one.
What decides the calories of a dal, a curry or a biryani?
The fat and the portion, before anything else. Ghee is about 876 kcal per 100 g in USDA FoodData Central, read 16 September 2026, so a tablespoon, about 13 g, is around 115 kcal, and a bowl of dal tempered with two of them can carry about as many calories in the ghee as in the lentils. Shared out, the arithmetic is worth doing: two tablespoons in a pot for four put roughly 58 kcal of that fat in your own bowl, which is the sum a fixed database entry can never make. Cooked lentils are about 116 kcal per 100 g; cooked rice about 130; a plain naan about 291. One caution with every figure below: the weight of a dish is not the weight of one ingredient. A 200 g bowl of dal is lentils, water, onion and the tempering together, and 300 g of biryani is rice, meat and fat together; the assistant has to apportion them, and that apportioning is an estimate whatever the scale said.
| The dish | What carries the calories | What to say | How it is recorded |
|---|---|---|---|
| Dal | The ghee or oil of the tempering; the size of the bowl | "A bowl, about 200 g, tempered with a tablespoon of ghee" | One estimated item that says so, with the tablespoon taken as the share in your bowl, not the pot's; lentils you weighed dry yourself are a reference value |
| Curry with meat or paneer | The oil or cream in the gravy; how much meat or paneer | "Chicken curry, about a plate, cooked in oil, a ladle of gravy" | Each item estimated after the question on the fat; paneer from a label if you have the pack |
| Biryani | The rice's cooked weight; the ghee; the meat | "About 300 g cooked, with chicken, made with ghee" | One estimated item: the assistant splits the 300 g between rice, chicken and fat, states the split, and the whole is marked estimated |
| Rice, by the cup | The cooked weight a cup holds | "A cup of cooked rice" | About 158 g, converted by the assistant and stored with your words beside it |
| Roti, chapati, paratha | The flour by weight; the ghee brushed or folded in | "Two homemade rotis, about 40 g of flour each, brushed with ghee" or "two from the packet" | Homemade from the flour and the ghee; a packet roti from its label |
| Rice | The cooked weight, or the raw weight before cooking | "150 g cooked" or "a cup cooked" | From the table, cooked or raw as you said; cooked weighs two to three times more than raw |
Bottom line: say the fat and the amount and the dish is an honest estimate; leave them out and no entry can supply them.
The rest usually matters less: which lentil, which rice, whether the onions were browned or not. Worth a word if you know them and a shrug if you do not. When the pot feeds more than one and each of you keeps a record, two accounts in one kitchen is the same arithmetic said twice. The fat and the amount are worth a question, and that is the question the assistant is asked to put to you before any number is recorded.
What do you say to record an Indian meal honestly?
Three things, the same three as any restaurant plate: what the dish was, about how much of it, and what it was cooked in. Add a fourth for rice and dal, whether the weight is cooked or raw, since it changes the figure by two to three times. Say them and the assistant has what it needs; leave one open and IZeat's protocol has it ask, once, before recording anything.
A packaged food is different: a block of paneer, a packet of rotis, a pot of yoghurt carry a nutrition label per 100 g, and the label is read back to you and recorded as such, scaled to what you ate. A plain food you weighed, rice, lentils, chicken, is valued from a composition table and recorded as a reference value. Everything cooked into a dish nobody weighed is an estimate, and the record says so beside the weighed lines.
The point of the source on every item is that a week later you know which figures were read from a label, which were weighed and which were reasoned from "about a bowl". A tracker that stores your dal beside a weighed roti without saying which is which makes the week look more certain than it was.
How do you record a dish cooked in one pot for the whole family?
From the ingredients, once, and then by the portion. Weigh what goes into the pot raw, lentils, oil or ghee, onions, tomatoes, and say the total to your assistant with how many portions the pot made. It does the arithmetic and gives you the figure per portion; the record carries that figure with the source the assistant declares, yours if you gave it, an estimate if it reasoned it, and either way it says which.
Two honest limits. IZeat has no recipe store today, so the pot's figure lives in the conversation and in the meals it was recorded into, not in a saved recipe you can call up next month; say the ingredients again or keep your own note. And a figure per portion assumes the portions were equal, which they rarely are: a bigger ladle is a bigger portion, and "about a portion and a half" is what to say.
The reward is a figure that is yours rather than a stranger's: your ghee, your lentils, your pot. For the dishes you cook every week, that is a number no entry typed for another kitchen can hold, and it is the number IZeat keeps.
How can you keep the diary when dinner is dal, rice and roti?
IZeat is the calorie tracker inside ChatGPT, Claude or any other assistant. Tell the assistant you already use what you ate instead of searching for foods and entering them one by one. It is designed to make the diary easier to keep on a cuisine where a search box returns someone else's recipe, while you work toward your goal, less weight or more muscle.
Tuesday evening: "Dinner was dal, about a bowl, with rice and two rotis." Following IZeat's protocol, the assistant asks, in one message, what a plate cannot show: the bowl, about 200 g or a ladle count; how much ghee went into the dal; the rice, a cup cooked or a weight; the rotis, homemade or from a packet. You answer: about 200 g, a tablespoon in the whole pot of which you ate about half, about 150 g cooked, homemade with a little ghee. IZeat records the rice from the table by weight, the dal as an estimate that says so, its 200 g split between lentils and the rest and half the tablespoon counted as yours, the rotis likewise, and returns the receipt with the day so far and, once you have set a target, what is left. On Wednesday at lunch you ask what would fit tonight; the assistant reads the day from IZeat and proposes; you decide, and IZeat records what you ate.
- You describe the dish in your own words, whatever the cuisine. Dal, sambar, biryani, a thali: there is no entry to find and no entry to pick; the assistant is asked, by IZeat's protocol, for the fat and the amount, and IZeat records each item with its source.
- The fat is a question in IZeat's protocol, never a guess from a picture. Ghee added by the spoon is the item a photo cannot show and a database entry silently fixes; here it is its own line, in your quantity.
- You know what is left before the next meal. Once you have chosen a target, every meal receipt carries the day so far and what is left against it, so the evening's rice is decided with the figure in view.
The limit, plainly: IZeat holds no Indian food database and no database of any kind; what your assistant knows about a dish is its own knowledge, and what it records is an estimate marked as one, unless you weighed the ingredients or read a label. If a database of Indian dishes with fixed figures is what you want, another app has one; if a record of what you actually ate, cooked the way you cook it, is what you want, this is it.
Frequently asked questions
Short answers to the questions people type, each one sourced above.
Is there a calorie counter app with an Indian food database?
Several apps carry Indian entries, and some people are served well by them; this page does not claim they fail. What an entry cannot do is know your recipe, your ghee and your portion: it fixes all three for someone else's kitchen. IZeat has no built-in food database. You describe the dish to the assistant you already use, it asks about the fat and the amount, and each item is recorded with its source, an estimate marked as one where it is one.
How many calories are in a bowl of dal?
There is no fixed figure, which is the point. Cooked lentils are about 116 kcal per 100 g in USDA FoodData Central, read 16 September 2026, so a 200 g bowl of dal, lentils with water and onion, is somewhat under 230 kcal before the tempering; ghee is about 876 kcal per 100 g, so one tablespoon adds around 115 and two add 230. The bowl can be worth twice as much depending on the spoon, and on whether it went into your bowl or a pot for four, so the assistant asks about the ghee and your share first.
How do I count calories in roti or chapati?
By the flour, and by what was brushed on. A homemade roti is its flour by weight plus the ghee or oil, if any; say "two rotis, about 40 g of flour each, brushed with ghee" and the assistant values the flour from a table and the ghee as its own item. A packet roti or naan carries a label per 100 g, read back to you and scaled to the piece; a plain naan is about 291 kcal per 100 g in the USDA table.
How do I track biryani?
Three things: the cooked weight of what was on your plate, or a cue like a bowl or a plate; whether it was made with ghee or oil, and roughly how much; and the meat or paneer in it. Say them and the assistant splits the plate's weight between rice, meat and fat, states the split, and the whole is recorded as one estimate; 300 g of biryani is not 300 g of rice. A photo names the dish; it cannot show the ghee or the weight, so IZeat's protocol has those asked first.
Does IZeat know Indian dishes?
IZeat holds no dish figures of its own; it records items with their grams, calories, macros and source. What knows dal, sambar or a Kerala fish curry is the assistant you already use, from its own knowledge, following IZeat's protocol: ask what the plate cannot show, then estimate and say it is an estimate. The reasoning is the assistant's; the record and the source on each item are IZeat's.
Can I log a thali?
Item by item, in one sentence: the rice, the dal, the sabzi, the roti, the curd, the pickle, each with a rough amount and the fat where it matters. The assistant is asked to gather what you left open in one message, and IZeat records the items together as one meal, each with its own source. A thali is many small estimates; the record says so, and the meal total is only as firm as its vaguest bowl.
What about restaurant curries with cream or coconut?
Say the gravy. Cream, coconut milk and oil are where a restaurant curry's calories sit, and none of them shows on the plate, so IZeat's protocol has the assistant ask what the gravy was made with and about how much of it you had, then record an estimate marked as one. Order with the day in view: ask what is left before the menu comes, and the assistant reads it from IZeat.
Does it work for South Indian food, dosa, idli, sambar?
The same way, with the same questions. An idli is steamed and carries little fat; a dosa carries the oil or ghee on the pan, which is what to say; sambar is a dal with vegetables, so the bowl and the tempering matter. Say the number of pieces and the fat, and each item is recorded as an estimate that says so; a packet batter has a label, read as printed.