Do calories change when you cook food?

The energy content of the food itself barely changes. What changes is the weight — boiling adds water, roasting removes it — and how much of that energy you can actually absorb, which rises because cooking makes starch and protein easier to digest.

Does boiling rice reduce its calories?

No. A hundred grams of raw rice has the same energy after boiling; it simply weighs two and a half to three times more because it absorbed water. Logging 100 g of cooked rice against a raw entry roughly triples the figure.

Does draining pasta or rice water remove calories?

A small amount of starch leaches into the water, typically a few per cent of the total. It is real but minor, and it is far smaller than the error from mismatching raw and cooked entries.

Does cooking vegetables reduce their calories?

No, though it does reduce their weight and some water-soluble vitamins. The calorie change that matters with vegetables is what they are cooked in: a fist of vegetables is 40 kcal plain and 150 kcal fried in a tablespoon of oil.

Does cooking change the calories in your food?

Cooking does not destroy calories, but it changes weight, digestibility and how much energy you absorb. What shifts, by how much, and what it means for logging.

By Gajendra Singh RathorePublished October 2, 20265 min read

The short answer

Cooking barely changes the energy in a food; it changes the weight, mostly by adding or removing water, which is why raw and cooked entries differ so much.
Cooking does increase how much energy you absorb from starches and proteins, because heat makes them easier to digest.
Frying adds calories by adding oil, sometimes 100 to 200 kcal per serving, and that is a genuine increase rather than a measurement artefact.
Log raw where you cook it yourself and cooked where you did not, and never mix the two states in one entry.

This question is usually asked in the hope that cooking destroys calories. It does not. But the honest answer is more interesting than a flat no, because three separate things change during cooking and only one of them is an illusion.

What does not change: the energy in the food

Heat does not remove energy from protein, carbohydrate or fat. A hundred grams of raw chicken and the same chicken grilled contain the same energy, minus whatever fat dripped out.

So when a database tells you cooked rice has 130 kcal per 100 g and raw rice has 360, it is not describing a loss. It is describing the same rice weighing more because it soaked up water.

What does change: the weight

This is the source of nearly every raw-versus-cooked error.

Rice: roughly 2.5 to 3 times heavier cooked
Dried lentils and beans: roughly 2.5 to 3 times heavier
Pasta: roughly 2.2 to 2.5 times heavier
Meat and fish: roughly 0.65 to 0.8 times — lighter, from water loss
Leafy greens: dramatically lighter as they collapse
Root vegetables: close to unchanged

These ratios are yield factors, and they vary with method, duration and how much water you used. Yours will not exactly match a published table, which is why measuring your own once is worth doing — the method is in should you weigh food raw or cooked.

What genuinely changes: how much you absorb

Here is the part that is real rather than an artefact.

Cooking gelatinises starch and denatures protein, which makes both substantially easier for digestive enzymes to reach. Raw starch from an uncooked potato is poorly digested; the same potato boiled is almost completely digested. Cooked meat gives up more of its protein than raw.

The effect is not trivial. Studies on cooked versus raw diets consistently show more energy extracted from cooked food, and it is one of the reasons cooking mattered so much to human history.

Processing works the same way. Ground grain yields more than whole grain. Nut butter yields more than whole nuts, whose intact cell walls resist digestion — which is why whole almonds deliver measurably less metabolisable energy than their analysed fat content predicts.

And the big one: what you cooked it in

The largest calorie change from cooking has nothing to do with chemistry. It is the oil.

Deep-fried food absorbs anywhere from 5 to 15 per cent of its weight in oil. A 100 g potato fried takes on 8 to 15 g of oil, which is 70 to 135 kcal added to something that started at 75.

Shallow frying and tempering are smaller but still dominant in home cooking. A tablespoon of oil in a sabzi is 120 kcal on a dish whose vegetables might total 80. Details in how much oil is actually in your curry and calories in ghee, butter and the tadka on top.

Does draining water remove calories?

Slightly, for starchy foods. Some starch leaches into the cooking water and is poured away with it. The commonly cited figures are a few per cent.

There is a longer-running claim about cooling rice to form resistant starch and thereby reducing its usable energy. There is real chemistry behind it — cooled starch does become partly resistant to digestion — but the magnitude in practice is modest, and it is not a mechanism worth building a diet around.

Both effects are smaller than the error from picking the wrong database entry, which puts them firmly in the category of true but unimportant.

The practical rules

Weigh raw, log raw, whenever you cook it yourself. Raw weight is reproducible; cooked weight depends on your lid and your patience.

Weigh cooked, log cooked, when someone else cooked it. Just make sure the entry explicitly says cooked.

Never mix. Weighing cooked rice against a raw entry is a threefold overcount; logging cooked meat as raw undercounts it by a quarter.

Count the cooking fat separately, always. It is the one thing cooking genuinely adds and the one thing no yield factor captures.

Why database entries disagree about this

If you have ever searched a food and found entries ranging from 110 to 360 kcal per 100 g, this is usually why. Some are raw, some are cooked, some do not say, and some were typed in by a person who did not know the difference.

An entry that names its state and its source is worth more than one that sounds specific. It is one of the main reasons two apps disagree about the same plate, covered in why two apps give the same roti different calories.

The short version

Cooking does not burn calories off your food. It moves water in or out, which changes the weight; it makes energy easier to absorb, which slightly increases what you get; and it frequently adds oil, which increases it a lot.

Log the state you measured, count the fat, and none of this needs thinking about again.

Questions people ask

Do calories change when you cook food?: The energy content of the food itself barely changes. What changes is the weight — boiling adds water, roasting removes it — and how much of that energy you can actually absorb, which rises because cooking makes starch and protein easier to digest.
Does boiling rice reduce its calories?: No. A hundred grams of raw rice has the same energy after boiling; it simply weighs two and a half to three times more because it absorbed water. Logging 100 g of cooked rice against a raw entry roughly triples the figure.
Does draining pasta or rice water remove calories?: A small amount of starch leaches into the water, typically a few per cent of the total. It is real but minor, and it is far smaller than the error from mismatching raw and cooked entries.
Does cooking vegetables reduce their calories?: No, though it does reduce their weight and some water-soluble vitamins. The calorie change that matters with vegetables is what they are cooked in: a fist of vegetables is 40 kcal plain and 150 kcal fried in a tablespoon of oil.

Sources

1.Food energy: methods of analysis and conversion factors — Food and Agriculture Organization of the United Nations
2.FoodData Central — USDA Agricultural Research Service

Should you weigh food raw or cooked?
Raw weight is reproducible and matches most database entries. Cooked weight is what you can actually measure. The conversion factors and when each one is right.
How accurate are calorie counts, really?
Labels carry a legal tolerance, databases disagree and absorption varies. How wrong calorie counts really are, and why it changes little about tracking.
How to count calories in home-cooked food
Home cooking has no barcode and no single right answer. The pot method, the oil problem, household servings, and reusable numbers for the food you eat.
Why two apps give the same roti different calories
Different databases, source types, raw versus cooked states and user-submitted entries. Why calorie apps disagree, and which number you should actually use.