Should You Weigh Food Raw or Cooked? The Matching Rule

Neither raw nor cooked is universally correct. The reliable rule is to weigh food in the same state named by the nutrition entry: use a raw, uncooked or dry entry for food before cooking, and a cooked entry for food after cooking. Cooking can add or remove water, while fat may be rendered out or added through oil and sauces. That means 100 g raw and 100 g cooked are not automatically equivalent. For batch cooking, record the raw ingredients, weigh the finished batch and portion it using the cooked yield.

The answer: match the food entry

Choosing raw or cooked is less important than matching the scale reading to the wording of the food entry. A cooked weight logged against a raw entry can make the portion appear different from what the database describes, even when you weighed it carefully.

The Australian Food Composition Database provides nutrient information for foods commonly available in Australia and distinguishes preparation states. When checking an entry, look for wording such as raw, uncooked, dry, cooked or drained rather than assuming every version of a food is interchangeable.

Raw or uncooked entry: weigh the food before cooking.
Dry entry: weigh dry rice, pasta or another dry ingredient before water is added.
Cooked entry: weigh the food after cooking, once it is in the state described.
Drained entry: drain it in the way the entry specifies before weighing, where that information is available.

Why cooking changes the number on the scale

Boiling rice and pasta usually adds water, increasing their weight. Meat and poultry can lose moisture during cooking. Fat can render out, and oil or sauce can be added or remain in the finished meal. The direction and size of the change therefore depend on the food and the method used.

FSANZ guidance describes weight changes as potentially positive or negative and affected by factors including cooking time, temperature, surface area, equipment and whether a lid is used. This is why a single raw-to-cooked multiplier should not be treated as a universal rule.

Water also changes how much food is represented by each 100 g. So it is not sound to assume that cooking never changes the nutrition represented by a weighed portion: water concentration can change, and fat may be lost or added. The practical answer is to match the preparation state or measure your own batch yield.

A three-step check before you log

Use this quick process whenever a food has both raw and cooked versions in a database.

First, weigh the food in the state that is easiest and most repeatable for your meal. Second, read the full food-entry wording instead of stopping at the food name. Third, log the entry that describes the same state as the item on your scales.

If you have only a mismatched entry, avoid applying a generic conversion without checking how the food was prepared. For meal prep, measuring the actual raw ingredients and finished yield is usually more useful than trying to make a standard conversion fit your saucepan, frying pan or oven.

Weigh the actual food state: raw, dry, cooked or drained.
Check the entry wording, not just the food name.
Save the matching entry and keep your batch method consistent where practical.

Worked example: chicken and poultry

An Australian Dietary Guidelines example uses approximately 100 g raw poultry becoming 80 g cooked. This is a useful illustration of why the same food can have different weights before and after cooking, but it is not a universal conversion for every cut, appliance or cooking method.

If a particular batch followed that ratio, 160 g cooked would correspond to approximately 200 g raw because 160 ÷ 0.8 = 200. The reverse calculation gives the same result: 200 g raw × 0.8 = 160 g cooked.

Use that arithmetic only as an illustration. If you are preparing several serves, your own raw and cooked weights are more relevant. Weigh the raw poultry, cook it, weigh the finished batch and use that measured yield for the portions you serve.

Worked example: dry rice and cooked rice

FSANZ gives an indicative plus 170% weight-change factor for boiled rice. In arithmetic terms, that means the cooked weight is 270% of the dry weight, or 2.7 times as much, under that example factor.

For 100 g dry rice: 100 g × 2.7 = 270 g cooked rice. Working backwards, 135 g cooked rice ÷ 2.7 = 50 g dry-rice equivalent.

These are illustrative calculations, not a promise about the result from every rice variety, water level, cooking time or covered pot. If the amount matters for your meal record, weigh the dry rice before cooking or weigh the actual cooked batch and divide it into serves using that batch’s result.

The most reliable batch-cooking workflow

Batch cooking is where a measured cooked yield is most useful. Start by weighing each raw ingredient and recording it, including cooking oil or sauces that form part of the recipe. Cook the meal, then weigh the complete finished batch before serving it.

For example, imagine the cooked batch weighs 800 g and your serve weighs 200 g. The portion fraction is 200 ÷ 800 = 0.25, or 25%. On this simple proportional method, that serve represents 25% of the batch’s recorded ingredients. This is a portion calculation, not a nutrient result.

For a mixed casserole, curry or pasta dish, distribute the ingredients as evenly as practical before portioning. If the meal contains separate components, such as chicken pieces alongside rice, weighing the components separately may give you a clearer record. Keep cooking oil and sauces in the recipe record rather than treating them as invisible extras.

For more detail on recording oils, dressings and sauces, see the related Snap n Eat guide listed with this article.

Record raw ingredients before cooking.
Weigh the finished batch after cooking.
Divide each serve’s cooked weight by the finished batch weight.
Use the resulting fraction to represent the recorded recipe.

How Snap n Eat fits this workflow

Snap n Eat supports a practical two-speed approach. Its website says the app can analyse a meal photo to estimate calories, protein, carbohydrates and fat, then lets you review the estimate before saving. That gives you a convenient starting point when you want to record an ordinary meal without typing every ingredient.

The app also supports searching for a food by name or brand and logging it manually. That is useful when you have weighed dry rice, cooked chicken or another ingredient and want to look for an entry whose wording matches the state on your scales. Snap n Eat does not remove the need to check whether an entry is raw or cooked; the matching decision still belongs in your workflow.

A sensible sequence is to take a photo, review the estimate, check the ingredients and portion against what you know, and then save the meal. If the photo cannot settle the exact amount of rice, the oil in a sauce or the cooked-versus-raw state, switch to food search rather than treating the photo estimate as an exact measurement.

Meal history and progress views can keep your records together, while water logging is available as another part of the app. These features support the diary around your weighing method; they do not turn a photo into a measured raw-to-cooked conversion.

Use a photo for a convenient first estimate.
Review the calories and macronutrient estimate before saving.
Use food search by name or brand when a weighed ingredient needs a more deliberate entry.
Keep the raw-versus-cooked wording in mind for every manual log.

Common mistakes to avoid

The most common problem is not weighing badly; it is pairing a correct weight with the wrong entry. A few habits can prevent that mismatch.

Logging cooked chicken against a raw poultry entry, or raw chicken against a cooked entry.
Treating dry rice and cooked rice as interchangeable because they have the same food name.
Applying the rice or poultry example to every cooking method without checking your own batch yield.
Leaving cooking oil, dressings or sauces out of the recipe record when they are part of the meal.
Assuming a food photo can identify hidden ingredients or an exact portion. Snap n Eat describes photo nutrition values as estimates, and ingredients and portion size can affect the result.

A practical next step with Snap n Eat

Download Snap n Eat from the official website using its iPhone or Android link. For your next meal, take a photo, review the estimate before saving, and use food search when you have weighed an ingredient and need to match a raw, dry or cooked entry more carefully.

For a batch meal, do the weighing separately: record the raw ingredients, weigh the cooked batch and calculate each serve as a share of that finished weight. Snap n Eat can hold the meal record, while your measured yield keeps the raw-versus-cooked decision clear.