🥗 Meal Nutrition Calculator
Meal Nutrition Calculator
A home-cooked meal has no label — this builds one
A packaged food carries its nutrition on the wrapper. A plate you cooked yourself carries nothing: no calories, no protein, no sodium — just the food. This calculator builds the missing label. You list what actually went into the meal, food by food, with the amount of each in grams, and it adds up the meal's calories, protein, carbohydrates, fat, fibre, sugar and sodium — for the whole meal and for each serving — using reference values from USDA FoodData Central, the public food-composition database maintained by the US Department of Agriculture.
That one capability answers the questions home cooking actually raises. What does this thali, plate or bowl really come to? Which ingredient is doing the damage — the rice, or the oil it was finished with? If the pot feeds four, what is on one plate? And how close is tonight's dinner to the calorie target your day is built around? None of those questions can be answered by looking at the food. They can be answered, closely enough to act on, by weighing it and doing this arithmetic — which is all the calculator does, quickly and without a spreadsheet.
How to read the result
The headline figure is calories per serving: the meal's total energy divided by the servings number you set. Underneath it, the result shows the whole-meal totals as well — useful for a recipe, where the pot matters more than the plate — and the meal's total weight in grams, which is the quickest sanity check that you entered the amounts you meant to.
Below the calories sit the per-serving nutrients. Protein, carbohydrates and fat are the energy-bearing three; fibre, sugar and sodium ride along because they are the three people most often need to watch in the other direction. The macro share line — "Calories from: Protein 34% · Carbs 47% · Fat 19%" — converts those grams into each macro's share of the meal's energy, at the standard factors of 4 kcal per gram of protein, 4 per gram of carbohydrate and 9 per gram of fat. Shares and grams answer different questions. Grams tell you whether you hit a protein target; shares tell you the shape of the meal — whether it is built mostly on carbohydrate, balanced, or quietly dominated by fat. A meal can have modest fat grams and still draw a third of its calories from fat, because each gram carries more than twice the energy. Finally, the per-ingredient table shows each food's own contribution, which is where the insight usually lives: nine times out of ten, one or two rows explain the whole total.
Why everything is per 100 grams
Every value behind this calculator is stated per 100 g of food. That is how food-composition databases work, and it is worth understanding rather than just trusting. A laboratory cannot analyse "a portion" — portions differ. It analyses a standard weight, and 100 g is the convention because the scaling is then trivial: the amount you ate, divided by 100, times the per-100 g figure.
So 150 g of cooked chicken breast, at 165 kcal per 100 g, contributes 150 ÷ 100 × 165 = 247.5 kcal — displayed as 248. Two hundred grams of cooked white rice at 130 kcal per 100 g contributes exactly 260. The calculator performs that one multiplication for every nutrient of every ingredient and adds the columns up. There is no hidden model and no estimation of your appetite: weigh the food, and the arithmetic is exact. Everything approximate about the result — and the accuracy section below is honest about it — lives in the reference values and in your weighing, never in the maths.
Worked example: a chicken, rice and dal plate
This is the meal the calculator opens with. A grilled chicken plate with rice, dal and broccoli, finished with a spoon of oil:
| Ingredient | Amount | kcal | Protein g | Carbs g | Fat g |
|---|---|---|---|---|---|
| Chicken breast, cooked | 150 g | 248 | 46.5 | 0.0 | 5.4 |
| Rice, white, cooked | 200 g | 260 | 5.4 | 56.4 | 0.6 |
| Lentils, boiled (dal) | 150 g | 174 | 13.5 | 30.2 | 0.6 |
| Broccoli, cooked | 100 g | 35 | 2.4 | 7.2 | 0.4 |
| Olive oil | 10 g | 88 | 0.0 | 0.0 | 10.0 |
| Whole meal (610 g) | 805 | 67.8 | 93.7 | 16.9 |
The meal also carries 16.0 g of fibre — nearly all of it from the dal — just 4.2 g of sugar, and 157 mg of sodium, low because nothing on the plate is processed. Its macro shares are Protein 34% · Carbs 47% · Fat 19%: a protein-forward plate, exactly what its builder intended.
Read the ingredient column the way the calculator's breakdown shows it. The chicken and rice together are 508 of the 805 kcal — the meal is those two foods, with everything else as supporting cast. And notice the smallest row: 10 g of olive oil, a single tablespoon, contributes 88 kcal — 11% of the entire plate's energy from 1.6% of its weight. That is the most useful lesson this tool teaches, and it teaches it on almost every meal: the fat you cook with is an ingredient, not a detail.
The servings split. Cooked as a double batch for two people, the same list with Servings set to 2 shows 402 kcal per serving, with 33.9 g protein, 46.9 g carbs, 8.4 g fat, 8.0 g fibre, 2.1 g sugar and 79 mg sodium. The whole-meal block still reads 805 kcal — nothing about the pot changed; only the division did.
Worked example: a breakfast bowl
A smaller build, to show a sweet meal's very different shape: 40 g of dry rolled oats, 200 g of whole milk, a 100 g banana and 20 g of peanut butter.
| Ingredient | Amount | kcal | Protein g | Carbs g | Fat g |
|---|---|---|---|---|---|
| Oats, rolled, dry | 40 g | 152 | 5.3 | 27.1 | 2.6 |
| Milk, whole | 200 g | 122 | 6.3 | 9.6 | 6.5 |
| Banana | 100 g | 89 | 1.1 | 22.8 | 0.3 |
| Peanut butter | 20 g | 120 | 4.4 | 4.5 | 10.3 |
| Whole meal (360 g) | 482 | 17.1 | 63.9 | 19.7 |
Fibre is 7.6 g, sugar 24.8 g — the banana and the milk's natural lactose doing most of that — and sodium just 93 mg. The macro shares flip compared with the chicken plate: Protein 14% · Carbs 51% · Fat 35%. Same calculator, same method; the shape of the meal is completely different, and the shares make that visible at a glance. (Sharp-eyed readers will notice the four kcal lines add to 483, not 482. That is the rounding rule at work, explained in the mistakes section — the total is computed from unrounded values and is the correct figure.)
How accurate is a food database, honestly?
Accurate enough to steer by, never exact — and it helps to know where the slack is. A database entry is the average of analysed samples of that food: one breed of chicken, one harvest of lentils, prepared one standard way. Your chicken was a different bird; your dal simmered longer; your rice is a different variety. Real portions of the same dish, cooked in two homes, can honestly differ by 10–20% in energy. Packaged foods are no better: regulators allow label values a tolerance (in the US, calories on a label may be off by up to about 20% and still comply), because the food inside the packet varies too.
Three consequences follow. First, treat every total as the centre of a range, not a point: 805 kcal means "about 800", which is all a calorie target ever needs. Second, the calculator's precision is still worth having — an estimate within 10% is a completely different tool from a guess, which for a home-cooked plate is routinely off by half. Third, your effort should go where the error is: weighing. A kitchen scale removes the largest error source (portion guessing) in seconds, and it matters most for the dense foods — oils, butter, peanut butter, rice, pasta — where a casual "about a spoon" can be off by 100 kcal. Nobody needs to weigh lettuce.
Raw or cooked? The water problem
The most common way to get a wildly wrong answer from any nutrition calculator is to mix up raw and cooked weights, and the reason is water. Foods change weight as they cook, in both directions:
- Rice, pasta, oats and lentils absorb water. Dry rice roughly triples in weight as it cooks. The water adds grams but no calories, so the cooked food is far less dense: cooked white rice is 130 kcal per 100 g, a figure that looks impossibly low if you were expecting the dry grain's density. Enter the weight of what is on your plate — the cooked food — against the cooked entries in this list (the list's rice, pasta, quinoa and lentil entries are all cooked values).
- Meat and fish lose water. A chicken breast shrinks as it roasts, concentrating its calories per gram. The list's meat entries are cooked values too, so weigh the cooked meat you serve, not the raw piece you bought.
- Oats in this list are the exception that proves the rule: the entry is for dry rolled oats (379 kcal per 100 g), because that is how porridge oats are measured out — dry, before the water and milk go in. The milk is then its own row, as in the breakfast example.
The rule that keeps you safe: enter the weight in the same state as the entry you chose. Cooked entry, cooked weight. The names in the list say which is which.
Common mistakes
Forgetting the cooking fat. The oil in the pan, the butter on the toast, the ghee in the tadka — if it ends up eaten, it is an ingredient. The worked plate's single tablespoon of olive oil was 88 kcal, more than the broccoli and a third of the chicken. Restaurant and takeaway food hides far more; that is a large part of why it out-calories the same dish cooked at home.
Entering a cooked weight against a dry entry, or the reverse. Covered above, and worth repeating because it produces the biggest errors available: a factor of two or three, silently. Check the entry's name before the number.
Guessing portions of dense foods. "A spoon of peanut butter" heaped is 30 g, level is 16 g — a 100 kcal difference in a food people add precisely because they are tracking carefully. Weigh the dense rows; estimate the salad.
Trusting the displayed lines to sum to the total. They may differ by a unit or so, by design: every line is rounded for display, while the total is calculated from the unrounded values and rounded once. The breakfast example's lines show 483 kcal against a true total of 482. The total is the right number; the lines are for reading, not for re-adding.
Double-counting what stays in the pan. A marinade mostly left behind, or oil that remains in the dish, was not eaten. Enter what you actually consume; if half the tadka oil stays in the serving bowl's bottom, enter half.
Reading the macro shares as a health score. Shares describe the meal's energy shape, nothing more. A 100 g row of olive oil is 100% fat and still a normal ingredient in a balanced plate; a meal at 50% carbohydrate can be lentils and vegetables or sugar and white bread. The ingredient table, not the shares, is where quality shows.
Using this calculator, step by step
The calculator opens with the chicken, rice and dal plate already built and totalled, so you can see a complete result before touching anything. To build your own meal: remove the rows you do not need, or start fresh with the Add ingredient button. For each food, pick it from the list — start typing to filter — and enter its amount in grams, in the state named (cooked or raw). Set Servings to the number of portions the whole list represents: 1 for a single plate, 4 for a family pot. Press Calculate. The result shows calories per serving, the whole-meal totals, the macro shares and each ingredient's contribution. Nothing changes while you type or while you add and remove rows — the figures update only when Calculate is pressed, so you can edit freely without a number you are reading shifting under you. Reset restores the example plate and clears the result. If a row is left without an amount, or no ingredient has an amount above zero, the result area shows a message naming what to fix.
Key terms
- Per-100 g value: the database convention — a food's nutrients stated for 100 grams of it, which the calculator scales to your amount.
- Macro shares: the percentage of a meal's energy coming from protein, carbohydrate and fat, at 4, 4 and 9 kcal per gram respectively.
- Serving: whatever you declare it to be — the whole list of ingredients divided by the servings number. The calculator cannot know your portions; it divides honestly by the number you give it.
- Reference value: a laboratory average for a food, from USDA FoodData Central — a reliable centre figure, not a measurement of the specific food on your plate.
- Cooked weight: the weight of a food after cooking, water gained or lost included. Most entries in the list expect this.
Related calculators
- Calorie Calculator — how many calories your whole day should hold, from your age, build and activity.
- Macro Calculator — split a calorie target into daily protein, carb and fat goals to compare your meal against.
- Protein Calculator — your daily protein requirement, so a meal's protein grams have a yardstick.
- Fat Intake Calculator — the daily fat range behind the shares this page shows.
- BMI Calculator — where your current weight sits for your height.
Frequently asked questions
What does the Meal Nutrition Calculator do?
It adds up the nutrition of a meal you build yourself. Choose each food in your meal, enter how many grams of it you used or ate, set the number of servings, and press Calculate: the calculator totals the calories, protein, carbohydrates, fat, fibre, sugar and sodium for the whole meal and per serving, using reference values per 100 g from USDA FoodData Central.
Where do the nutrition values come from?
Every food in the list carries values from USDA FoodData Central — the US Department of Agriculture's public food-composition database — stated per 100 g of the food. The calculator scales each value to the grams you enter (grams ÷ 100 × the per-100 g figure) and adds the results together.
Should I weigh my food raw or cooked?
In the same state as the entry you pick. Most entries here are for the food as eaten — cooked rice, cooked pasta, boiled lentils — so weigh the cooked food on your plate. Rice and pasta absorb water as they cook, which is why cooked white rice is 130 kcal per 100 g while the dry grain is far denser; entering a cooked weight against a dry entry, or the reverse, is the single biggest error in meal tracking.
How do I work out a whole recipe, not just one plate?
Enter every ingredient in the full recipe at the amount you put in the pot, then set Servings to the number of portions the recipe makes. The calculator totals the whole recipe and divides by the servings: the chicken, rice and dal plate in the guide totals 805 kcal, so cooked as a double batch with servings set to 2, each serving shows 402 kcal.
Does the cooking oil really make that much difference?
Yes. Olive oil is 884 kcal per 100 g, so a single tablespoon of about 10 g adds 88 kcal — in the guide's worked plate, that oil is 11% of the meal's calories from 10 g of ingredient. Butter, ghee and other cooking fats behave the same way. If it went into the pan and ends up eaten, it belongs in the list.
Why don't the numbers on screen add up exactly?
Because of rounding. Each ingredient line is rounded for display — calories to whole numbers, macros to one decimal — but the totals are calculated from the unrounded values and rounded only at the end. Displayed lines can therefore differ from the total by a unit: in the breakfast example the lines show 483 kcal while the exact total is 482.
How accurate is the result?
Treat it as a well-founded estimate, not a laboratory measurement. Database values are averages for each food; your variety, recipe and cooking will differ a little, and packaged-food labels carry their own tolerances. Weighing the ingredients — especially oils, rice and pasta — removes most of the error; guessing portions by eye is where the big misses happen.







































