How much does rice weigh after cooking?

White rice ends up roughly 2.8 times its dry weight. USDA lists long-grain white rice at 365 calories per 100g dry and 130 per 100g cooked, which works out to about 280g cooked for every 100g dry. Your pot will vary with how much water the rice takes on, so weigh it dry.

How much does pasta weigh after cooking?

Enriched pasta ends up about 2.3 to 2.4 times its dry weight. The USDA entries (371 calories per 100g dry, 158 per 100g cooked) work out to roughly 235g cooked for every 100g dry. Cook time changes it, which is why dry weight is the reliable number to log.

How much weight does meat lose when cooked?

Usually a quarter to a third. USDA's cooking-yield table has roasted chicken breast with skin keeping 72% of its raw weight (range 61–82%), lean ground beef crumbles keeping 69%, and pan-broiled lean beef patties keeping 77%. The lost weight is mostly water plus some rendered fat; nearly all the protein stays in the meat.

Are nutrition labels for raw or cooked food?

Nutrition labels describe the food as packaged or sold. Federal labeling rules (21 CFR 101.9(b)(9)) put the panel on that basis, so the panel on a bag of dry pasta or rice describes it dry, not cooked. Some brands add an optional 'as prepared' column, so check which one you log.

Should You Weigh Food Raw or Cooked? (Meat, Rice, Pasta & Oats)

You can weigh food raw or cooked. The entry you log has to match the state you weighed, because mixing the two is the real error: 100g of dry pasta logged against a cooked entry records 158 calories for food that holds 371. For rice, pasta and oats, weigh dry. For meat, pick raw or cooked and never switch.

Is it better to weigh food raw or cooked?

Raw (or dry) is the more consistent reference, but cooked is fine as long as the entry matches. Raw weight doesn't care how long you cooked the food or how much water the pot took on, so it's the steadier number.

There are two separate errors here, and they are not the same size. The first is a mismatch: you weigh food in one state and log it against the entry for the other. For carbs that soak up water, the numbers below work out to an error of 2 to 5 times. For meat it's around 38%. Raw chicken breast is 22.5g of protein per 100g (USDA FDC 171077) and roasted is 31.0g (USDA FDC 171477), so by my math, raw grams logged as cooked overstate your protein by that much.

The second is doneness drift: your chicken cooked a little longer or shorter than the chicken in the database, so even the correct entry is slightly off. That one is smaller: across USDA's range for roasted chicken, roughly 10 to 20% either way. Fix the mismatch first. It's the one big enough to erase a deficit.

Do you weigh meat raw or cooked?

Either, as long as you never switch. Meat loses about a quarter to a third of its weight in the pan, mostly water, and nearly all of the protein stays behind. Same protein, less weight, so cooked meat reads higher per 100g.

The USDA entries show the gap. Chicken breast (meat only) is 22.5g protein and 120 calories per 100g raw, and 31.0g and 165 calories roasted. 93% lean ground beef is 20.8g and 152 calories raw (USDA FDC 173110), and 28.9g and 209 calories as pan-browned crumbles (USDA FDC 174755).

Here's the mismatch in real grams. Weigh 150g of raw 93% beef, log it against the crumbles entry, and by my math the app records about 314 calories and 43g of protein. What you actually ate was about 228 calories and 31g. The calorie error lands on the safe side for a cut. The protein error doesn't: your log says you hit your number and you're 12g short.

How you cook it moves the number too. The USDA Table of Cooking Yields for Meat and Poultry (Release 2, 2014) has lean ground beef (under 12% fat) keeping 69% of its raw weight as pan-fried crumbles, 73% as a grilled patty and 77% as a pan-broiled patty. Same beef, different pan, an 8-point spread.

Roasted chicken breast with skin keeps 72% on average, but the samples run from 61% to 82%. Apply that range to raw breast meat and cooked chicken could land anywhere from about 27g to 37g of protein per 100g, against the 31g in the entry. That's my arithmetic, and it's illustrative only, since the yield row includes skin. That spread is the doneness drift: real, but a fraction of the mismatch.

My rule for chicken: weigh it cooked, log it cooked, every time. Raw reads about 23g per 100g and it loses about 25% of its weight as water, so one consistent state keeps the numbers honest. If chicken carries your protein, here's how much protein is in chicken breast per serving.

Do you weigh rice and pasta dry or cooked?

Weigh them dry. The label on the bag describes dry food: federal labeling rules put the panel "on the basis of food as packaged or purchased" (21 CFR 101.9(b)(9)). Dry weight never changes. Cooked weight depends on how much water the pot took on, how long it sat, and whether you drained it.

The swing is big. USDA lists long-grain white rice at 365 calories per 100g raw (USDA FDC 168877) and 130 cooked (USDA FDC 168878). That works out to rice ending up about 2.8 times heavier. Enriched pasta is 371 per 100g dry (USDA FDC 169736) and 158 cooked (USDA FDC 169737), about 2.3 to 2.4 times.

The mismatch cuts both ways. By my math from those entries:

100g of dry pasta logged as cooked: the app says 158 calories. You ate 371. That's 213 calories you never counted.
100g of dry rice logged as cooked: 130 logged, 365 eaten, 235 missing.
280g of cooked rice logged against the dry entry: the app records about 1,020 calories for rice that holds about 364. Now you're over-counted by roughly 660, and you'll eat less than you planned without knowing why.

The under-count is the one that stalls a cut. Log 100g of dry pasta as cooked once a day and that's about 1,500 calories a week, over 40% of a 500-a-day deficit gone.

What about oats and potatoes?

Oats swell the most of anything here, so always weigh them dry. Potatoes go the other direction and matter much less.

Oats: weigh dry, every time

USDA lists dry oats at 379 calories per 100g (USDA FDC 173904) and oatmeal cooked with water at 71 (USDA FDC 173905), a ratio of about 5 to 1 by my math. But that's USDA's pot, not yours. Make your oatmeal thick or soupy and the cooked weight changes while the calories don't. So 50g of dry oats logged as 50g of cooked oatmeal records about 36 calories for a bowl that holds about 190. Weigh the oats before the water goes in.

Potatoes: the one that shrinks

Potatoes lose water in the oven instead of gaining it. Raw potato, flesh and skin, is 77 calories per 100g (USDA FDC 170026); baked is 93 (USDA FDC 170093). That works out to a baked potato keeping about 83% of its raw weight. A mismatch here costs you roughly 17 to 21%, not 2 to 5 times. Weigh it raw, or weigh it baked and use the baked entry.

How do you weigh food when you batch cook?

Use a ratio. Weigh the whole batch raw, cook it, weigh the whole batch cooked, and divide cooked by raw. That's your yield. When you serve a portion, weigh it cooked and divide by the yield. The answer is the raw grams to log against the raw entry.

These two examples only show the math. Your batch will give a different yield, so weigh your own.

Chicken

1,000g of raw chicken breast cooks down to 720g. Yield: 720 ÷ 1,000 = 0.72.
Your portion weighs 180g cooked.
180 ÷ 0.72 = 250g raw.
Log 250g against the raw entry: about 56g of protein and 300 calories.

Log that same 180g against the cooked entry and you get about 56g and 297 calories. When your yield is close to the database's, both methods agree. When it isn't, the ratio wins, because it uses your pot and not USDA's.

Rice

300g of dry rice cooks up to 840g. Yield: 840 ÷ 300 = 2.8.
Your portion weighs 210g cooked.
210 ÷ 2.8 = 75g dry.
Log 75g against the dry entry: about 274 calories.

How much does the wrong entry actually cost you?

More than it looks, because it repeats every day. I found this out with apples, not pasta. I was eating around 300 calories a day more than I thought, because the apples I bought weighed far more than the "standard apple" my tracking app assumed. Same failure as everything above: the weight in the log didn't match the food in my hand. I only caught it because I weigh my food.

By my math, 300 a day is 2,100 calories a week. That's 60% of a 500-a-day deficit, gone to fruit.

I weigh in every morning and log every macro, with no estimates. Momentum is measured, not felt, and a log with the wrong entry measures the wrong thing. I judge only the 7-day average, and a wrong entry you repeat every day won't show up there as a spike. It shows up as a trend that won't move. If yours won't move and you're sure you're in a deficit, check your entries before you cut calories. The full checklist is in not losing weight in a calorie deficit.

If you want the daily routine this fits into, The Momentum Method is free: four numbers tracked daily (bodyweight, steps, macros and your workout) on a one-screen scorecard.

Pick a state for each food, match the entry to it, and never switch. Dry for rice, pasta and oats. Raw or cooked for meat, as long as it's the same one every time.