The difference between raw and cooked weight

What changes is water, not calories

The energy in a food comes from the carbohydrate, protein and fat it contains. Boiling and cooking largely preserve those components; what really changes is the water content. Rice and pasta absorb water as they cook and roughly double or triple in weight. Meat loses water and can shed around a quarter of its weight. Because the energy stays the same while the weight changes, the calories per gram appear to change too.

The same rice, two different numbers

Take an example: 100 g of raw rice is around 350 kcal. Cooked, that rice reaches about 250–300 g; the total energy is still the same, but 100 g of cooked rice now corresponds to about 120–130 kcal. Both numbers are correct; they simply describe different states. The confusion comes from applying the raw figure to a cooked amount, or the other way round, and it can throw an estimate out by two or three times.

Which state do labels and databases use?

The packet labels of dry foods such as rice, pasta, bulgur and lentils usually give values for the raw or dry state. Food composition databases and apps often hold both a raw and a cooked entry for the same food, so it is worth checking which one you have selected. Entries for prepared dishes such as pilaf also include added ingredients like oil, which produces a different figure from plainly boiled rice. For general habits around labels, the food label guide will help.

Which state should you weigh in practice?

Both approaches work; what matters is consistency:

• Weighing raw: the most accurate method, because cooking time and the amount of water do not affect the result. You weigh before the pot and use the raw figure.
• Weighing cooked: practical for ready meals and for eating out; in that case you must select the cooked or boiled entry in the database.

If you are serving from a family pot, a rough method is this: work out the raw ingredients of the whole recipe once and count how many portions it makes; the value of one portion is the total divided by the number of portions.

Approximate conversions for common foods

Exact ratios vary with the cooking method, but for everyday use the approximate conversions can be summarised as follows:

There is no need to memorise the table. Measuring once in your own kitchen, to see how many grams 100 g of raw rice reaches in your own pilaf recipe, gives you a conversion factor specific to your recipe and more accurate than any table. The same factor holds as long as you cook the same way.

How much precision is really needed?

There is no need to weigh every mouthful in daily life, and for most people it would not be sustainable. The real value of knowing the raw and cooked difference is that it prevents large errors: deviations of two or three times mislead far more than small estimation errors. All calorie calculations work with estimated ranges anyway; for the whole picture, see why calorie counts are never exact. If tracking causes you anxiety or strain, agreeing a more flexible method with a dietitian is a good option.

In short: decide which state you are weighing, choose the entry for that state in the database, and measure your own standard vessels, such as a ladle, a glass and a tablespoon, once so that you can use them as a reference. These three habits remove the large errors that come from raw and cooked confusion, and they make tracking sustainable in everyday life.

Frequently asked questions

This guide draws on the general logic of raw and cooked entries in food composition databases and on water content data in food science sources.