🔧 Tools & Reviews

Raw vs Cooked: How to Weigh Food Accurately

The single biggest hidden source of calorie-tracking error. Here's the rule.

Updated April 26, 2026 · by the CalorieBliss editors

The Core Concept

Food contains water. When you cook food, some water leaves (proteins, vegetables) or some water enters (rice, pasta). The food itself — the proteins, fats, carbs — stays the same. So the calories stay the same, but the weight changes.

This is why nutrition databases publish both “raw” and “cooked” entries for foods. They have the same calories — they’re just labeled at a different point in the cooking process.

The Common Mistake

Here’s the typical scenario:

1. You weigh 6 oz of raw chicken breast.
2. You cook it. It’s now ~4.5 oz.
3. You eat it.
4. You log “6 oz cooked chicken breast” in your tracker.

Cooked chicken breast at 6 oz is ~365 kcal. Raw chicken breast at 6 oz is ~280 kcal.

By logging “6 oz cooked” but actually eating raw-weight 6 oz (which became cooked 4.5 oz), you over-counted by ~85 kcal.

Or vice versa: weigh after cooking (4.5 oz), log “4.5 oz raw chicken” (~210 kcal). Now you under-count by ~70 kcal — which sounds better, but it means your “1,500 kcal day” is actually more like 1,570.

The Rule

Whichever weight you measure, log the matching entry.

• Weighed raw → log “raw chicken breast” in your tracker
• Weighed cooked → log “cooked chicken breast” in your tracker

Most major tracker databases have both entries. Look for “raw” or “uncooked” in the entry name.

Which to Use: Raw or Cooked?

Both work. Each has tradeoffs.

Raw weighing pros:

• More accurate (water content is consistent in raw protein)
• Easier to weigh in batches (weigh once before cooking)
• Standard for most recipe portions
• Tracker entries are more reliable for raw

Raw weighing cons:

• You have to remember to weigh before cooking
• Not always practical (frozen meals, restaurant food)

Cooked weighing pros:

• You can weigh “what’s actually on your plate”
• Useful for leftovers
• Useful when you didn’t cook the food yourself

Cooked weighing cons:

• Cooked weight varies more (depending on cooking method, time)
• Tracker entries are slightly less consistent
• A chicken breast cooked dry vs juicy will have different weights

Recommended for consistency: weigh raw when you can, weigh cooked when you can’t, always match the entry to what you weighed.

Conversion Factors (Approximate)

The biggest swings are in proteins (lose ~25%) and grains (gain 200%+). These are also the foods most worth weighing accurately.

Foods Where It Matters Most

The 80/20 of food weighing — the foods where raw vs cooked confusion creates the biggest calorie errors:

1. Chicken, beef, fish, shrimp. ~25% weight loss; meaningful kcal swing.
2. Rice, pasta, quinoa, oats. Triple in weight; logging “cooked” as “dry” is a 3× over-count.
3. Bread. Doesn’t really change cooked vs uncooked at the consumer level (you eat it as it comes).
4. Vegetables. Mostly change in volume but small change in calories per gram. Less critical.
5. Pre-cooked foods (deli meat, rotisserie chicken). Already cooked; use cooked entry.

A Worked Example

You’re meal prepping and cook 4 chicken breasts. Total raw weight: 24 oz. Cooked weight: 18 oz.

Method A (weigh raw, divide):

• 24 oz raw / 4 portions = 6 oz raw per portion
• Each portion logged as “6 oz raw chicken breast” = 280 kcal

Method B (weigh cooked, divide):

• 18 oz cooked / 4 portions = 4.5 oz cooked per portion
• Each portion logged as “4.5 oz cooked chicken breast” = ~280 kcal

Both methods give the same answer because both methods match the weight to the entry. The error happens when you mix them.

The Vegetables Exception

For most vegetables, raw vs cooked logging is essentially fine — the calorie content per gram doesn’t change much, and even when volumes change dramatically (spinach, mushrooms), the calorie totals are small enough that error rounds to noise.

Don’t bother weighing vegetables raw vs cooked unless you’re tracking obsessively. “1 cup of cooked spinach” and “3 cups of raw spinach” are the same food at the same calorie count, just different visual volumes.

The Cooking Oil Problem

A separate but related issue: cooking method can add calories not captured in the food’s weight.

Pan-fried chicken absorbs ~50–120 kcal of oil per portion. The chicken itself didn’t gain weight (it lost weight), but the meal has those oil calories.

Always log cooking oils separately from the food they cooked.

Common Logging Mistakes

Mismatching raw and cooked. ~25% error.

Forgetting cooking oil. Add 100+ kcal per pan-fried portion.

Eyeballing portion sizes after cooking. Cooked food packs differently. Weigh.

Logging “1 chicken breast” without specifying weight or state. Defaults vary.

Assuming “boneless skinless” matches your actual portion. Boneless skinless tends to be standardized; weigh to confirm.

What to Take Away

• Cooking changes weight, not calories.
• Match weight to entry. Raw weight to raw entry; cooked to cooked.
• Weigh raw when you can. Cooked weighing is fine when you can’t.
• Most tracker databases have both — pick the one that matches.
• The biggest errors are in proteins and grains. These are also the foods worth weighing.

For the kitchen scale recommendations, see best kitchen scales for calorie counting. For label-reading once weighing is sorted, see how to read a nutrition label.