DataFood
Educational only, and not medical advice. The figures on this site are estimates from population equations, not measurements of any individual. If you are pregnant, under 18, managing a medical condition, or have any history of disordered eating, speak to a clinician rather than a calculator.

Cooked vs Raw Weight: Why the Number Changes

Cooked vs raw weight changes the calorie count you look up. Learn the conversions for rice, chicken, and pasta, and one rule for everything else.

A cup of cooked rice is not a cup of raw rice. The database entry you look up almost certainly refers to the raw weight, and the scale in front of you is showing the cooked weight. The gap between those two numbers is not a rounding error. For rice it is a factor of roughly three. For chicken it runs the other way, by about a quarter. This page is about where those factors come from, what they depend on, and how to recover the number you actually want.

What the number on the label refers to

Nutrition data is generated from a specific physical sample. The USDA FoodData Central entry for white rice, long-grain, regular, raw, enriched lists 365 kcal per 100 g. The entry for the same rice, cooked, enriched, lists 130 kcal per 100 g. Both are correct. They describe different objects. The raw entry describes dry grains. The cooked entry describes grains that have absorbed water.

The Atwater factors are the arithmetic underneath most of these numbers. Protein and carbohydrate are assigned 4 kcal per gram, fat 9 kcal per gram, alcohol 7 kcal per gram. These are averages derived from bomb calorimetry and metabolism experiments, and they carry a standard error of roughly 5% for mixed diets. A food label in the United States may be off by up to 20% for most nutrients under FDA rounding rules, and by more for vitamins and minerals. A label may print zero grams of fat if the food contains less than 0.5 g per serving. A label may print zero calories if the food contains fewer than 5 kcal per serving. The number is a legal statement about a sample, not a measurement of the item in your hand.

Why cooking changes the weight, not the calories

Cooking adds or removes water. It does not add or remove macronutrients. A 100 g raw chicken breast contains about 22 g protein and 2.5 g fat, which the Atwater factors convert to roughly 120 kcal. Cook it, and the same breast weighs about 75 g because water has evaporated. The protein and fat are still there. The density has changed.

Rice goes the other way. A 100 g portion of dry white rice absorbs roughly 200 g of water during cooking, ending at about 300 g. The 365 kcal are now spread across three times the mass. If you weigh 300 g of cooked rice and log it against the raw entry, you record 1,095 kcal instead of 365 kcal. That is a threefold error, and it is one of the largest single errors available in a food log.

FoodRaw weightCooked weightWater changeCondition that changes the ratio
White rice, long-grain100 g~300 g+200 gSoaking before cooking reduces absorption; brown rice absorbs slightly less
Chicken breast, skinless100 g~75 g-25 gCooking method: poaching retains more water than roasting; brining adds water
Pasta, dry100 g~240 g+140 gAl dente retains less water than soft-cooked; whole wheat absorbs more
Oats, rolled100 g~250 g+150 gStovetop vs. microwave; standing time after cooking
Ground beef, 90% lean100 g~75 g-25 gFat content: higher fat loses more weight and more calories in the drippings
Lentils, dry100 g~250 g+150 gSoaking time; altitude affects boiling point and absorption

The arithmetic, worked in the open

The conversion is a ratio. If you know the cooked weight and the raw-to-cooked ratio, you can recover the raw weight, and then look up the raw entry.

Step 1. Weigh the cooked portion. Example: 240 g cooked white rice.
Step 2. Find the raw-to-cooked ratio for that food. White rice: 1 : 3.
Step 3. Divide cooked weight by the cooked side of the ratio.
        240 g / 3 = 80 g raw equivalent.
Step 4. Look up the raw entry. White rice, raw: 365 kcal per 100 g.
Step 5. Multiply. 80 g x (365 / 100) = 292 kcal.
Step 6. Check against the cooked entry. Cooked rice: 130 kcal per 100 g.
        240 g x (130 / 100) = 312 kcal.
Step 7. The two figures differ by 20 kcal, or about 6%. That gap is the
        difference between the specific samples in the two database entries.
        Either is acceptable. The error you avoided was 1,095 kcal.

The same arithmetic works for chicken in reverse.

Step 1. Weigh the cooked portion. Example: 150 g cooked chicken breast.
Step 2. Find the cooked-to-raw ratio. Chicken breast: 0.75 cooked per 1 raw.
Step 3. Divide cooked weight by 0.75.
        150 g / 0.75 = 200 g raw equivalent.
Step 4. Look up the raw entry. Chicken breast, raw: 120 kcal per 100 g.
Step 5. Multiply. 200 g x (120 / 100) = 240 kcal.
Step 6. Check against the cooked entry. Chicken breast, cooked: 165 kcal per 100 g.
        150 g x (165 / 100) = 248 kcal.
Step 7. The two figures differ by 8 kcal, or about 3%. The error you avoided
        was logging 150 g against the raw entry: 180 kcal, an undercount of 60 kcal.

One rule for everything else

Weigh the food in the state the database entry describes. If the entry says raw, weigh raw. If it says cooked, weigh cooked. The USDA and most commercial databases label the state explicitly. When the state is not stated, assume raw for grains, pasta, legumes, and raw meats. Assume cooked for dishes, restaurant items, and anything that has already been prepared.

The practical rule is simpler: weigh before cooking when you can, because the raw weight is stable and the cooked weight depends on how long the food sat in the pan. A chicken breast roasted for 25 minutes and one roasted for 35 minutes differ in weight by 10 to 15 g. The raw weight is the same. If you must weigh cooked, use the ratio for that specific food and accept a band of roughly 10% around the result.

What people get wrong, and why the mistake is natural

The mistake is not carelessness. It is a reasonable inference from incomplete data. A person buys a chicken breast, cooks it, puts it on a plate, and weighs it. The scale reads 150 g. The person opens a food app, types “chicken breast,” and the first result is often the raw entry, because raw is the default in many databases. The person logs 150 g against a number that describes a different object. The arithmetic is correct. The input is wrong.

The second natural mistake is assuming that cooking destroys calories. It does not. Cooking can reduce the available energy of some foods by a small amount, mostly through protein denaturation and starch gelatinization, but the effect is on the order of 5% for most foods and is already baked into the cooked entries. The larger effect is water. Water has zero calories and substantial weight. When water leaves, the calorie density of the remaining food rises. When water enters, the density falls. The total calories in the portion do not change.

The third mistake is treating the ratio as a constant. It is not. The raw-to-cooked ratio for rice depends on the variety, the soaking time, the cooking method, and the amount of water used. A 1 : 3 ratio is a reasonable average for long-grain white rice. A 1 : 2.5 ratio is common for firmer rice. A 1 : 4 ratio appears when the rice is cooked soft. The ratio is a range, not a fixed number, and the range is wide enough to matter.

What to do differently

Weigh the food in the state the database entry describes, and when the state is ambiguous, weigh raw. The raw weight is the stable input. The cooked weight is the output of a process that varies. If you are tracking intake and the numbers are not matching your expectations, check the state of the entry before you check anything else. The error is usually there, and it is usually a factor of two or three, not a rounding error.

This page is not medical advice. It is arithmetic about food data. If you are managing a clinical condition, a medication, or a history of disordered eating, the numbers on this page are not a plan. In the United States, the National Eating Disorders Association helpline is available at 1-800-931-2237. In the United Kingdom, Beat’s helpline is 0808 801 0677. In Australia, the Butterfly Foundation helpline is 1800 33 4673. These are free, confidential routes to a person who can help with the part that arithmetic cannot reach.

Common questions

Do you weigh food cooked or raw?

Weigh it in the state the database entry describes. If the entry says raw, weigh raw. If it says cooked, weigh cooked. When the state is not stated, assume raw for grains, pasta, legumes, and raw meats, and cooked for prepared dishes. The raw weight is more stable because it does not depend on cooking time.

Is rice calories cooked or raw?

Both entries exist and both are correct. Raw white rice is about 365 kcal per 100 g. Cooked white rice is about 130 kcal per 100 g. The difference is water. A 100 g portion of dry rice becomes roughly 300 g cooked, so the same calories are spread across three times the weight.

Is chicken cooked vs raw calories different?

The calories per gram are higher in cooked chicken because water has evaporated. Raw chicken breast is about 120 kcal per 100 g. Cooked chicken breast is about 165 kcal per 100 g. A 100 g raw breast weighs about 75 g cooked, and the total calories are roughly the same.

How do I convert cooked weight to raw weight?

Divide the cooked weight by the cooked side of the raw-to-cooked ratio. For rice, the ratio is about 1 : 3, so 240 g cooked is 80 g raw. For chicken, the ratio is about 1 : 0.75, so 150 g cooked is 200 g raw. Then look up the raw entry and multiply.

Why does my food scale show a different number than the app?

The app is probably showing a raw entry and the scale is showing cooked weight, or the reverse. Check the state of the entry first. If the state matches, the remaining gap is the difference between the specific sample in the database and the food in front of you, which is usually within 10% for whole foods.

Read next