Chain restaurants in some countries have to print calories on the menu. Almost nowhere else does, and the food most people actually eat out — the local place, the thali joint, the neighbourhood Chinese, the wedding — publishes nothing at all.
Searching a food database for "butter chicken" returns a dozen entries with a 400-calorie spread and no way to tell which one resembles your plate. That is not information. So here is how to estimate properly instead, and how to be wrong in a direction that does not hurt you.
Start with the three assumptions
Before any specific dish, internalise these. They do more work than any lookup.
1. There is more fat than you would use. Restaurant food tastes better largely because of butter, cream and oil. A home cook uses a spoon of oil in a sabzi; a restaurant kitchen uses three or four, plus cream to finish. Assume roughly double your own hand.
2. The portion is bigger than a serving. Restaurant rice is typically two to three cups, not one. A curry portion is two katoris. A plate of pasta is often two of what a packet calls a serving.
3. You will underestimate. Everybody does, consistently, and studies of self-reported restaurant intake find errors skewed heavily in one direction. If your estimate feels generous, it is probably about right.
Those three alone get most people closer than a database lookup does.
Break the plate into components
Do not try to price "chicken biryani" as one object. Price its parts, which you can see.
Biryani = rice (2 cups, 400–500) + chicken (a palm, 150–200) + cooking fat (generous, 150–250) + raita (80–120)
>
Working estimate: 800–1,050
That range is wide and it is honest. It is also far more useful than a database entry confidently claiming 620, because you can see which part of the range your plate sits in — if there was visible ghee pooling, take the top.
Components you can nearly always identify:
- The starch. Rice, roti, naan, bread, noodles, chips. Usually the largest single number and the easiest to count.
- The protein. A palm of chicken, paneer or fish. Reasonably predictable.
- The fat. The one you cannot see and must assume. This is where the estimate lives or dies.
- The extras. Raita, chutney, sauce, dressing, the butter on the naan.
Rough anchors for common restaurant items
Ranges, because these vary enormously between kitchens.
| Item | Typical restaurant serving | Calories |
|---|---|---|
| Butter naan | 1 | 300–400 |
| Tandoori roti | 1 | 120–170 |
| Plain rice | 1 restaurant portion | 350–500 |
| Biryani | 1 plate | 700–1,100 |
| Butter chicken / paneer makhani | 1 portion | 450–700 |
| Dal makhani | 1 portion | 350–500 |
| Dal tadka | 1 portion | 200–300 |
| Mixed veg sabzi | 1 portion | 250–400 |
| Paneer tikka, dry | 6–8 pieces | 300–450 |
| Masala dosa | 1 | 350–500 |
| Samosa | 1 | 250–320 |
| Veg thali | 1 full | 800–1,200 |
| Fried rice or hakka noodles | 1 plate | 600–900 |
| Lassi, sweet | 1 glass | 250–400 |
More detail on the everyday items lives in the Indian food calorie chart and the street food guide.
The dishes that cost most and hide it
Some restaurant food is far more calorie-dense than it looks. These are the ones worth knowing by name.
Anything "makhani", "malai", "korma" or "shahi". The name is telling you there is cream and butter in it. A makhani gravy can carry 200 calories of dairy fat before you count anything else.
Butter naan and laccha paratha. A butter naan can equal three rotis. This is frequently the largest number on the table and nobody thinks of bread as the problem.
Restaurant dal. Home dal is 120–180 a katori. Dal makhani is cream, butter and a long finish — two to three times that.
Anything deep-fried. Oil absorption is genuinely unpredictable, and always higher than it looks.
Drinks. A sweet lassi, a soft drink or two beers can be a third of a day, consumed without registering as food at all.
What to do when you truly cannot tell
Three fallbacks, in order.
Find the closest thing you can price. A chain with published figures selling something similar is a reasonable proxy. It will not be exact; it will be the right order of magnitude, which is what you need.
Log the range and take the middle. "Somewhere between 700 and 1,000" recorded is worth more than a precise number not recorded. If the day matters, take the top of the range.
Log the meal, not the number. Write down what you ate even if you cannot price it. A log with one uncosted entry is still a log. A log you abandoned because one meal was hard is not — this is precisely how tracking falls apart.
Log a meal the way you would write it down. BetterCal turns a plain sentence — spoken or typed — into calories and macros. Free to start.
Download BetterCal on the App Store · Get BetterCal on Google Play
Say what you saw
If you are logging by sentence rather than searching a database, the estimate follows what you tell it. The word "restaurant" alone repositions the whole meal, because it changes the fat assumption.
"Restaurant butter chicken, one butter naan, about a cup of rice, and a sweet lassi"
Fifteen words, all of them things you observed. That gets you a defensible number without a database entry existing for the specific kitchen you were sitting in. Describing a meal accurately covers which details actually move the estimate.
Deciding before you order
Estimation after the fact is damage assessment. If you want the meal to fit the day, the decision happens at the menu.
- Tandoori and grilled beats gravy. No cream, far less oil, same protein.
- Roti beats naan. Usually saves 200 calories for the same job.
- Dry beats makhani. Paneer tikka against paneer makhani is a 300-calorie choice.
- Order the rice for the table, not per person. The default portion is two servings.
- Drink the calories deliberately or not at all. A lassi is a dessert.
- Let the day absorb it. A lighter breakfast and lunch on a day you know ends in a restaurant is much easier than trying to eat a small dinner out. The week is the unit, not the meal.
None of this requires ordering sadly. It requires knowing which three items on the table carry most of the calories, which after a fortnight of estimating you will.
Frequently asked questions
How do you estimate calories at a restaurant with no nutrition information?
Break the plate into components — starch, protein, cooking fat, extras — price each from a known anchor, and add a generous allowance for oil and cream. Log the result as a range rather than a single figure, and lean towards the higher end.
How accurate are posted restaurant calorie counts?
They describe a standard build made to spec, not the plate in front of you. Real servings routinely run over the published figure, and independent testing has found meaningful discrepancies. Treat a posted number as the lower bound of a range.
How many calories are in a restaurant thali?
Usually 800–1,200 for a vegetarian thali, more if the rotis come buttered or the rice is refilled. The dal, the sabzi gravies and the ghee do most of it — the variety on the plate disguises how much cooking fat is spread across it.
Should I just skip logging when I eat out?
No — that is where the largest and most variable numbers are, and a log missing exactly those meals will not explain a stall. Log a wide range instead. An imprecise entry keeps the week's data usable; a missing one does not.
Is one restaurant meal enough to undo a week?
Rarely. A 1,000-calorie excess against a 500-a-day deficit costs you two days, not the week. The damage comes from the meal becoming a reason to stop logging — see eating out without losing the plot.
Related: tracking calories when eating out · Indian street food calories · tracking without weighing food
