Calories in Recipe
Estimate total and per-serving calories from a list of ingredients with protein, carbs and fat macro breakdown
Ingredients
Nutrition Summary
Total Calories
331
Per Serving
166
Calorie estimates are based on standard food values. Use USDA database for precise nutrition info.
How Many Calories a Recipe Actually Contains
Add each ingredient with its weight and the tool sums total kcal then divides by the number of servings. The built-in food database covers 15 common ingredients with kcal-per-100g values: chicken breast is 165 kcal/100g, olive oil is 884, butter 717, rice 130, pasta 371, cheese 402, almonds 579. So a 4-serving recipe with 600g chicken (990 kcal), 30ml olive oil (265 kcal) and 200g rice (260 kcal) totals 1,515 kcal, or 379 kcal per serving.
These numbers are estimates, accurate to within about 10% of true values. Real-world variation in cuts of meat, oil quality and how much fat trims off in cooking means a precise count to the calorie isn't possible at home. For ballpark calorie tracking - macros at the meal level, weekly intake budgeting - this is fine. For medical-grade tracking (gestational diabetes, post-bariatric surgery, competitive bodybuilding), use the USDA FoodData Central database directly with a kitchen scale.
Why Per-Serving Beats Per-Recipe
Knowing a lasagne contains 4,200 kcal isn't useful. Knowing each of 6 servings is 700 kcal is useful, especially next to your daily intake target (typically 1,800-2,500 for adults depending on size and activity). Always set the servings field to the realistic eating portion, not the technical division. A bolognese that "serves 4" usually serves 3 in a hungry household, so set it to 3.
If you're meal-prepping, divide the recipe by the number of containers you actually portion it into. A pot of chilli portioned into 6 lunch boxes serves 6, even if the recipe says 4. The per-serving figure scales with the divisor, so being honest with the number gives honest calorie counts. The [meal planner](/meal-planner) handles weekly calorie totals across multiple recipes.
What the Tool Captures and What It Doesn't
The tool counts the calories in raw ingredients. It does not subtract calories from fat that drains off (a roast loses 5-15% of its starting fat to the pan), and it does not add calories from cooking medium that gets absorbed (chips absorb about 8% of their cook oil). For most home cooking these effects roughly cancel, but for very fatty meats or deep-fried food the actual eaten calories will be lower (drained fat) or higher (absorbed oil) than the calculation.
Macro tracking (protein, carbs, fat) needs a more detailed database than this tool's 15 staples. If you're tracking macros for fitness, log into a dedicated app like MyFitnessPal or Cronometer, which has hundreds of thousands of foods with full macro splits. For everyday "is this recipe roughly 500 or 800 kcal per serving" questions, this tool answers in 30 seconds. Pair it with the [BBQ planner](/bbq-planner) when planning party food where total intake matters.
Cutting Calories Without Ruining the Dish
The fastest calorie cuts in most home recipes: replace half the oil with stock or water (saves around 80 kcal per tablespoon), use Greek yoghurt instead of cream in pasta sauces and curries (saves around 250 kcal per 100ml), swap rice for cauliflower rice in stir-fries (saves around 100 kcal per 100g cooked). None of these change the dish enough to notice if you do them quietly.
The slow calorie additions worth watching: oil in salad dressings, cheese sprinkled at the table, butter on bread alongside soup. These don't show up in the recipe calorie count but easily add 200-400 kcal to a 'healthy' meal. If you're tracking, weigh and log them too. The [substitute ingredient finder](/substitute-ingredient-finder) suggests lower-calorie swaps for specific ingredients if you want to lighten a recipe without rewriting it.
Frequently Asked Questions
How accurate is this calorie estimate?
Within about 10% for common ingredients. The tool's database uses standard kcal-per-100g values from public nutrition databases. Real variation comes from how lean the meat actually is, how much oil clings vs absorbs, and how heavily a hand of cheese is sprinkled. For day-to-day calorie awareness this is plenty; for clinical accuracy use a verified nutrition database with a 0.1g kitchen scale.
Should I count cooking oil that ends up in the pan?
Yes, count what you put in. Most home cooking uses 1-2 tablespoons of oil (15-30ml, 130-270 kcal), and most of it stays in the food rather than draining off. The exception is searing fatty meat or deep-frying, where significant fat moves. For everyday tracking, count the oil you start with.
Why isn't [ingredient] in the dropdown?
The built-in database covers 15 staples that hit most home recipes. For anything else, look up its kcal-per-100g on the USDA FoodData Central or the British Nutrition Foundation's database, then enter that value manually in the calories field. Common gaps: salmon (208 kcal/100g), beef mince 5% fat (137 kcal/100g), avocado (160 kcal/100g).
Does cooking change the calorie count?
Slightly, in either direction. Boiling pasta absorbs water (the cooked weight goes up but kcal stays the same as the dry weight), so always log dry pasta weight. Roasting meat loses water and some fat (cooked weight goes down but kcal also drops slightly). Use raw weights for everything, which is what the tool assumes.