Logging Food Raw vs Cooked: The Mistake Quietly Wrecking Your Tracking

This is the most common reason people are accidentally over their calorie target without realizing it. Food shrinks when you cook it. Water evaporates, fat renders out, fibers compress. The same physical piece of chicken weighs less after it's cooked than it did before, but it still has roughly the same calories. So if you weigh it after cooking and log it as if it were raw, you're undercounting.

A typical chicken breast might weigh 200 grams raw. Cook it, and it's down to maybe 150 grams. Both pieces have around 330 calories. But if you punch in "150g chicken breast" using the raw value (165 cal per 100g), you'll log 248 calories instead of 330. That's an 80-calorie miss on a single meal. Do it three times a week and you've quietly added 250 calories to your weekly intake without changing what you ate.

Rice and pasta go the other direction. Dry pasta is around 370 cal per 100g. Cooked, it absorbs water and drops to roughly 130 cal per 100g. Same calories, more weight. If you weigh 100 grams of cooked pasta and log it as dry, you've tripled your real intake on the page.

The simple rule

Decide whether you log raw or cooked, and stay consistent for that ingredient. Most people pick whichever is easier to weigh in their kitchen. If you usually buy a package of chicken breasts and weigh them before they hit the pan, log raw. If you usually portion out cooked rice from a meal-prep batch, log cooked. Either is fine as long as you're using the matching database entry.

When you tell your Threwline coach "had 150 grams of cooked chicken breast," it knows to use the cooked entry from USDA, not the raw one. The trick is being explicit about which form you're talking about. "150g chicken" is ambiguous. "150g chicken cooked" or "150g raw chicken" is not.

Where it bites people the most

The biggest offenders are foods that change weight dramatically with cooking:

Chicken, beef, pork, and fish all lose roughly 20 to 30 percent of their weight when cooked. If you're tracking by post-cook weight and using raw values, you're missing real calories.

Rice and pasta absorb water and double or triple in weight. If you're tracking by dry weight and pouring out cooked portions, you're either way over or way under depending on which database entry you used.

Bacon and ground beef drop a lot of weight as fat renders out. The fat is gone but the database entry assumed it was still there.

Vegetables shrink when sautéed or roasted but the calorie change is so small it doesn't matter for tracking.

The Threwline workflow

If you're not sure, just tell your coach what state the food was in when you weighed it. "200g raw ground beef cooked into a stir-fry" or "180g cooked rice from the rice cooker." The coach handles the lookup correctly. If you forget to specify, the coach will usually ask before logging — which is the right call, because the difference between raw and cooked logs is the difference between losing weight and not.

Start your free Threwline trial and your coach will catch these for you so you don't have to think about it.