Raw vs cooked food weight: which should you log for calories?

Match the weighing state before choosing a number

Write down whether you weighed the food raw, dry, cooked or drained. Then look for the same description on its package or nutrition reference. The important decision is the match between the amount and the reference, rather than a rule that every ingredient must always be weighed before cooking.

For example, 150 g of raw chicken and 150 g of roasted chicken describe two portions at different stages. A search result titled simply chicken may leave too much unspecified. Read the preparation, cut, skin and other qualifiers before deciding that the entry represents what you ate. USDA FoodData Central documents several different types of food data, including branded label information and analytical food data.

Sources: [1]

Understand what the change in weight can mean

Water can enter or leave food during cooking, while fat may also be added or lost. A lighter finished food therefore does not automatically have fewer total calories than the starting portion. Equally, a heavier cooked starch is not necessarily a larger quantity of dry starch. Weight alone cannot tell you everything that happened.

The USDA cooking-yield tables track both moisture and fat changes for specified cuts and cooking methods. That is why a single percentage taken from an unrelated meal is a poor shortcut. A food that is boiled, grilled, roasted or fried can require a different reference even when the name of the starting ingredient is identical.

Sources: [2]

Divide a known batch without switching reference states

Hypothetical example: 200 g of a dry ingredient provides 700 kcal according to its matching label. After cooking in plain water, the batch weighs 600 g. If you serve 150 g of that evenly mixed batch, your share is 150 divided by 600, or one quarter. Allocate one quarter of the starting energy, which is 175 kcal.

This is an allocation method for the invented batch, not a claim that all foods retain every nutrient during cooking. It assumes the food and energy being allocated remain in the dish. If cooking liquid or rendered fat is discarded, or ingredients are added, document that difference and use an appropriate cooked reference when available.

Choose one coherent workflow for each ingredient

If you know the original ingredients, record the raw or dry quantities with their matching labels and calculate the completed dish outside the app. If you only have a prepared serving, use its cooked weight with a suitable cooked reference. Both workflows can be useful. Mixing the amount from one with the nutrition from the other creates the avoidable error.

Keep side dishes and additions visible in the calculation. A cooked rice reference usually cannot tell you whether your own pan also contains oil, butter or stock ingredients. Check whether an existing prepared-dish entry already includes these items before adding them again. Naming the preparation in the final entry makes that review easier next time.

1. Identify the food and preparation.
2. Record when the amount was weighed.
3. Choose nutrition information for that same state.
4. Include known additions once.
5. Review the portion and final nutrition together.

Handle an unknown conversion without inventing precision

If you forgot the dry weight, you do not have to reverse-engineer it with a fixed three-times or one-quarter rule. Look for an appropriate cooked-food reference and describe the serving you actually have. Keep uncertainty visible when the recipe, preparation or amount is estimated. A plausible-looking decimal is not evidence that the conversion was measured.

For repeat cooking, note the dry ingredient amount and finished edible batch weight once for that batch. Repeat the measurement when the ingredients or cooking method change. Do not assume yesterday's yield still applies after adding more water, changing the pasta shape or allowing a dish to reduce for longer.

Make the state clear in your CalQuest entry

In CalQuest, use manual entry when you have already calculated the portion. Give it a name such as rice, cooked, 150 g, or roast chicken, edible portion. Review calories and macros at the same serving basis. A photo can also provide an editable estimate, with an optional note explaining the preparation and known amounts.

A meal photo does not weigh the food or determine its starting raw weight. Review its result against information you actually know, and avoid saving both the ingredient calculation and the whole-meal estimate for the same food. Free photo scan energy is limited; CalQuest has ads and optional PRO. Recent or Favourites entries still need a serving check when reused.

Frequently asked questions

Is it wrong to weigh food after cooking?

No. A cooked weight is useful when the nutrition reference describes the matching cooked food. The mismatch between states is the issue.

Can I convert every raw weight to cooked weight with one ratio?

No. Water, fat, food type and cooking method affect yield. Measure the specific batch or use a matching prepared-food reference.

Does water lost during cooking mean calories were lost?

Not by itself. Water loss changes weight, while discarded fat or other food can change the energy retained. Treat those as separate questions.

Can an AI photo tell me the original dry quantity?

A photo cannot establish the original dry weight. It can provide a portion estimate to review, supported by a note and any measured quantities.

Keep exploring

• Dry vs cooked rice calories: how to log your bowl correctly
• Should you weigh meat before or after cooking for calories?
• Calculate a homemade recipe and your share
• Understand why calorie entries disagree
• Enter known nutrition manually