When counting calories, you should use whichever weight matches the entry you selected in your food tracker. If you pick “chicken breast, raw” from the database, weigh it raw. If you pick “chicken breast, cooked,” weigh it cooked. The calorie values are different for each because cooking changes the weight of food, and mixing up the two is one of the most common tracking mistakes people make.
Why Raw and Cooked Weights Differ
Cooking drives moisture out of food. Meat, poultry, and fish shrink roughly 25 percent during cooking, meaning 4 ounces of raw chicken breast becomes about 3 ounces once cooked. USDA data on beef cuts shows moisture retention rates ranging from about 63 percent for a roasted ribeye roast to 72 percent for a grilled ribeye steak. The longer and hotter you cook something, the more water leaves.
This matters because calories don’t evaporate with the water. A 4-ounce raw chicken breast has about 134 calories. Cook it down to 3 ounces and those same calories are now packed into a smaller, lighter piece of meat. That’s why 100 grams of cooked chicken breast has more calories per gram than 100 grams of raw chicken breast. The calories didn’t increase; they just got concentrated into less weight.
Which Approach Is More Accurate
Weighing raw is generally more consistent and reliable. A raw chicken breast weighs the same whether you plan to grill, bake, or poach it. Once cooked, that same breast could weigh anywhere from 70 to 80 percent of its original weight depending on your cooking method, temperature, and time. Two people cooking the same cut of beef can end up with meaningfully different cooked weights.
Raw entries in food databases like the USDA’s FoodData Central also tend to be more standardized. Cooked entries often specify a cooking method (grilled, roasted, pan-fried), and if your method doesn’t match, the nutrient profile won’t be quite right. When you weigh raw, you remove that variable entirely.
That said, weighing cooked works perfectly well as long as you’re consistent. If you meal prep a large batch and portion it out after cooking, weighing cooked and selecting a cooked database entry is the practical choice. The key rule: the state of the food on your scale must match the state described in the database entry.
How Cooking Affects Different Foods
Not all foods behave the same way when heated. Meat loses water and fat, making it lighter. Rice and pasta absorb water, making them heavier. A cup of dry rice roughly triples in weight after cooking, which means 100 grams of cooked rice has far fewer calories than 100 grams of dry rice. If you accidentally log cooked rice using a raw entry, you’ll massively overcount.
Vegetables lose water too, though the amount varies. Spinach wilts down dramatically, losing most of its volume, while roasted broccoli loses a moderate amount of moisture. For most vegetables the calorie difference is small enough that it won’t derail your tracking, but for calorie-dense foods like meat, grains, and pasta, the distinction matters a lot.
Cooking also changes how many calories your body actually extracts from food. Research from Harvard found that cooking increases the net energy your body absorbs from proteins, carbohydrates, and fats. In nuts and seeds, heat breaks down the cell walls and protective protein layers that normally shield fats from your digestive enzymes. The result is that cooked food delivers slightly more usable energy than the same food eaten raw, though standard calorie databases already account for this in their cooked entries.
A Simple Conversion When You Need One
If you cooked your meat before weighing it but only have a raw database entry (or vice versa), the 25 percent shrinkage rule gives you a workable estimate. Multiply your cooked weight by 1.33 to approximate the raw weight, or multiply your raw weight by 0.75 to estimate cooked weight. So 6 ounces of cooked chicken breast started as roughly 8 ounces raw.
This is an average. Fattier cuts lose more weight because they render out fat along with moisture. Leaner cuts and those cooked quickly (like a thin steak seared rare) lose less. But for everyday tracking, the 25 percent rule keeps you close enough.
The Practical Approach
Pick one method and stick with it. If you cook individual portions, weighing raw before it hits the pan is simplest. If you batch cook, weigh the total raw amount, log the full calories, then divide by the number of portions you serve out after cooking. This way each portion carries a proportional share of the total calories regardless of how much water cooked off.
For packaged foods like frozen chicken or ground beef, the nutrition label almost always refers to the raw weight. Check the label for language like “serving size 4 oz (112g)” and whether it says “raw” or “as packaged.” If it doesn’t specify, assume raw, since that’s the industry standard for meat and poultry labeling.
The difference between getting this right and getting it wrong can be significant. If you weigh 6 ounces of cooked chicken breast but log it as 6 ounces raw, you’re undercounting by roughly 25 percent of the actual calories in that portion. Over multiple meals a day, that kind of error adds up fast.