Guide~4 MIN
Cooked or raw: the biggest hidden error in calorie counting
Dry pasta is 371 kcal per 100 g; cooked pasta is 157. Logging the wrong state can more than double a meal's count — here's how to get it right.
The short answer
Dry pasta is 371 kcal per 100 g; boiled pasta is 157. Same food, more than double the difference, because boiling only adds water. Grains and pasta absorb water and get less caloric per gram; meat loses it in the pan and gets more. Weigh whichever state is convenient - but record which one it was. The silence is the bug, not the choice.
Here is a question that quietly ruins more food logs than any other: when you write "100 g of pasta", do you mean the dry pasta you poured from the package, or the cooked pasta on your plate? Because those are two very different numbers — 371 kcal versus 157 kcal in the USDA database. Same food. More than double the difference. And most tracking apps never ask which one you meant.
Water is the whole story
Nothing magical happens to pasta in the pot. The starch, protein and trace fat that were in the dry noodles are still there after boiling — cooking pasta neither creates nor destroys meaningful calories. What changes is water: dry pasta absorbs roughly 1.4 times its weight in it. So 100 g of dry spaghetti becomes about 240 g of cooked spaghetti, and every 100 g of the cooked stuff is now mostly-water noodles carrying only 157 kcal.
The same physics applies across the kitchen, in both directions:
| Food | Raw/dry, per 100 g | Cooked, per 100 g |
|---|---|---|
| Pasta (dry vs boiled) | 371 kcal | 157 kcal |
| White rice (dry vs boiled) | 365 kcal | 130 kcal |
| Chicken breast (raw vs roasted) | 120 kcal | 165 kcal |
Notice the chicken row runs the other way. Grains and pasta absorb water and get *less* caloric per gram; meat loses water in the pan and gets *more* caloric per gram. A raw 200 g chicken breast (240 kcal) cooks down to roughly 145 g — and if you then weigh it and apply the raw value of 120 kcal/100 g, you'd log 174 kcal for a piece of meat that actually carries 240.
How big can the error get?
Take a normal dinner: a plate with 250 g of cooked rice and 150 g of roasted chicken breast.
- Logged correctly: 250 g cooked rice at 130 = 325 kcal, plus 150 g roasted chicken at 165 = 248 kcal. Total: about 573 kcal.
- Rice logged with the dry value: 250 g at 365 = 913 kcal for the rice alone. Total: about 1,161 kcal.
That single mislabeled ingredient doubled the meal. Run that error the other way — logging dry-weight portions with cooked values — and you'll *under*-count just as badly, wonder why the scale disagrees with your log, and conclude that calorie counting "doesn't work". It works fine. The state field was wrong.
The rules for logging it right
- Weigh whichever state is convenient, but say which one it is. Both are fine; silence is the bug.
- Packages speak dry. The nutrition label on pasta, rice and oats refers to the uncooked product. If you portioned from the package, use dry values.
- Plates speak cooked. If you're weighing food that's already been cooked — at home, in a canteen, leftovers — use cooked values.
- Meat shrinks, grains swell. As a rough rule, meat loses 20–30% of its weight in cooking; pasta and rice gain 140–180%.
- When in doubt, prefer weighing raw. Raw weights are more consistent — how much water cooked rice holds depends on how long it simmered.
How calorie.one handles it
We made the cooked/raw state a first-class field in the analysis rather than a footnote in a help article. When you log "100 g of pasta with tomato sauce", the AI doesn't just identify pasta — it decides whether that amount refers to the pre-cooking or cooked state from context, marks it, and the USDA lookup respects the mark. "A bowl of spaghetti" matches the cooked row at 157 kcal/100 g; "I cooked 125 g of spaghetti" matches the dry row at 371, because you weighed from the package.
And because the guess can still be wrong, the meal's line-by-line breakdown shows exactly which database row was used for every ingredient. If you see "Pasta, dry" where you meant a cooked plate, you fix that line and the totals recompute. You'll find the full pipeline on the methodology page — or just try it on your own dinner.
FAQ
Should I weigh food raw or cooked?
Either — but record which one you used, because the same 100 g means two different numbers. Packages speak dry: the label on pasta, rice and oats refers to the uncooked product. Plates speak cooked. Where you have the choice, raw weights are the more consistent measurement.
Is 100 g of pasta dry or cooked?
It depends who is saying it, which is exactly the problem. Dry pasta is 371 kcal per 100 g and boiled pasta is 157 — more than double. 100 g of dry spaghetti becomes roughly 240 g on the plate.
Does cooking add calories?
No. Boiling adds water and roasting drives it off; neither creates nor destroys meaningful energy. What changes is how many grams the same calories are spread across, which is why the per-100 g figure moves in opposite directions for pasta and for meat.
How much weight does chicken lose when cooked?
Roughly 20–30%. A raw 200 g breast carrying 240 kcal cooks down to about 145 g carrying the same 240 kcal, which is why the cooked row reads 165 kcal per 100 g against 120 raw.
How much does rice weigh after cooking?
Rice and pasta gain roughly 140–180% of their dry weight. 100 g of dry white rice at 365 kcal becomes about 280–300 g cooked at 130 kcal per 100 g — the same calories, nearly three times the weight.
The USDA rows behind this article
Every serving size USDA lists, per record, with the FDC ID so you can check the number at the source.
Related reading
Count with real numbers
Calorie.one looks every ingredient up in the USDA database — and shows you the lines so you can check.
Start tracking free