Food Scale Mastery: Raw vs Cooked Weight Differences in Meats, Grains, and Vegetables

Should you weigh food raw or cooked for macros? Raw (or dry) is the more reliable default, provided you log it against a raw or dry entry. Cooking mostly changes how much water the food holds, and that varies from pot to pot. The protein, carbs and fat barely move.

The real mistake is mixing the two states. This guide is part of our high-protein foods and meal prep guide, and it gives you the conversion logic, a few rough tables and a batch cooking workflow so you can stop second-guessing your scale.

(If you are still deciding between a scale and measuring cups, read food logging precision: digital scales vs measuring cups first.)

Why does raw vs cooked weight matter at all?

Because water is heavy and has zero calories.

When you cook chicken, water leaves the meat, so the piece weighs less. When you cook rice, water goes in, so the pot weighs more. The food’s macros are mostly unchanged. The weight is what moves.

That is why “100 g of chicken” and “100 g of rice” mean very different things depending on whether the scale reading came before or after the stove. A raw 100 g chicken breast and a cooked 100 g chicken breast are not the same amount of meat. A dry 100 g of rice and a cooked 100 g of rice are not even in the same ballpark.

Is raw weight really the gold standard?

It is the most practical one, and here is the reasoning.

Cooking yield is not a constant. Research on cooked meat shows that yield and nutrient retention shift with the cut, the animal’s age and the cooking method. One South African study of lamb and mutton found that cooking yields and moisture retention differed by cut (lower for lamb loin, higher for lamb leg), and that retention of several nutrients differed between lamb and mutton and between moist and dry heat (van Heerden et al., 2017). That was sheep, not chicken breast, so do not read the numbers across. But it makes the point: the cooked weight of the “same” food is a moving target.

Raw (or dry) weight avoids that. You weigh the food as it came out of the packet, before the pan, the cooker or the pressure whistle changes anything.

There is also reassuring evidence that this does not wreck accuracy. A household survey analysis in Kenya compared two ways of calculating nutrient intake: using raw-food nutrient values, or applying cooking yield and retention factors to get values for food as eaten. For dietary energy, protein, fat and carbohydrate, the two approaches gave statistically equivalent average intakes. Some vitamins, such as vitamin C and some B vitamins, did differ (Moltedo et al., 2021). This was a population-level survey, not a lifter’s food diary, so treat it as support for the principle rather than proof for any one meal. The principle is that macros mostly survive cooking.

Do you lose protein when you cook chicken?

Not enough to matter for tracking.

Here is the part that confuses people. Cooked chicken shows a higher protein number per 100 g than raw chicken. That is not extra protein. It is the same protein in less water.

Take 100 g of raw chicken breast. If it loses about a quarter of its weight in cooking, you end up with roughly 75 g on the plate. The protein in that piece is about the same as before. The cooked piece is just denser, so each gram of it carries more.

A caveat on the “same protein” idea. Some nutrients can leach into cooking liquid, especially when you boil in a lot of water and discard it. In a lab study on boiled beef, cooking time, how the meat was cut and the type of boiling water all changed how much phosphorus was lost, while the authors concluded that protein content was largely preserved (Ando et al., 2015). That study was designed for kidney-diet needs and I would not use it to estimate your chicken curry. For everyday pan cooking, baking or pressure cooking where you eat the gravy, the protein in the dish stays in the dish.

What are typical raw to cooked conversion numbers?

Treat these as starting points, not laws. Your stove, your pan and your timing change them. I would rather you weigh your own food raw and cooked twice and write your own multiplier on the fridge.

Food (100 g raw or dry)	Typical cooked weight	Rough multiplier	What drives the range
Chicken breast	about 70-80 g	0.7-0.8x	Cooking time, heat, cut thickness
Chicken thigh (boneless)	about 65-80 g	0.65-0.8x	Fat content, how long it cooks
Fish fillet	about 75-85 g	0.75-0.85x	Method (steamed vs pan-fried)
White rice	about 250-300 g	2.5-3x	Water ratio, variety, softness
Pasta	about 200-250 g	2-2.5x	Cooking time, shape
Whole dal (dry lentils)	about 250-300 g	2.5-3x	How soupy you make it
Spinach or leafy greens	well under half	0.1-0.3x	Water content, cooking time
Soya chunks (dry)	about 250-300 g after soaking	2.5-3x	Soaking time, squeezing

These are rule-of-thumb ranges from everyday cooking, not figures from a single study. The shape of the pattern is the useful bit. Meat and veg shrink. Grains, lentils and soya swell.

How do you convert raw weight to cooked weight?

Two simple formulas cover almost everything.

To convert raw to cooked: raw weight x your multiplier = expected cooked weight.

To convert cooked to raw: cooked weight / your multiplier = estimated raw weight.

Example, chicken. You cooked chicken and the plate reads 150 g. If your multiplier is about 0.75, the raw weight was around 200 g. If you know 100 g raw is about 23 g protein (check your database entry), that serving is roughly 46 g protein.

Example, rice. You have 300 g of cooked rice. With a multiplier of 2.75, that is about 110 g dry. Now you can look up carbs per 100 g of dry rice and scale from there.

Be honest about the margin. If your multiplier is off by 10%, your estimate is off by 10%. For a single meal that is small. For a daily total across rice, dal, roti and oil, it adds up, which is why weighing raw is the cleaner option.

What is the best way to weigh food for batch cooking?

This is the method I recommend for anyone who preps in bulk. It works for dal, rajma, chicken curry, khichdi and biryani alike. If you are planning a full prep session, pair it with the 3-hour weekly batch meal prep blueprint.

1. Put an empty pot on the scale and zero it.
2. Weigh each raw ingredient into the pot (chicken, dry rice, dry dal, oil, onion). Log them.
3. Cook the batch.
4. Weigh the whole cooked pot. Subtract the pot’s weight.
5. Divide your total macros by the total cooked weight to get macros per gram.
6. Weigh each portion cooked, and multiply by the per-gram value.

You get the best of both worlds. The raw weights fix the macro total, and the cooked weights let you serve fair portions without any maths in the moment. Water gains and losses stop mattering, because they are baked into the final pot weight.

Why do the rice and dal packets confuse everyone?

Because the label often does not tell you which state it is describing.

Most packets list nutrition per 100 g of the product as sold, which is usually dry. But some brands, ready-to-eat pouches and apps list values “as prepared” or “cooked”. Check the column heading before you trust a number. Words to look for are “as sold”, “dry”, “uncooked” and “as prepared”.

Apps add another layer. Many databases carry both a raw and a cooked entry for the same food, and user-submitted entries are not always labelled clearly. Pick one entry, label it in your own words (“rice, dry, white”) and keep using it.

For the Indian staples, the same logic applies to dals and pulses. Weigh the dry dal. Cooked dal is a mixture of lentils and however much water you added that day.

What about oil, ghee and everything else in the pan?

Weighing the chicken raw does not weigh the oil you fried it in. Oil and ghee need their own line in your log. They are dense in calories, and a casual glug into the kadhai can be more than you think. We cover this in hidden calorie traps in Indian cooking.

A simple habit: put the pan on the scale, zero it, pour in the oil and log the actual grams. It takes five seconds.

Raw vs cooked for vegetables, paneer, eggs and roti

Different foods behave differently, so here is a quick guide.

• Vegetables: weigh raw. They are low in calories, so even a loose estimate is fine. Greens like spinach shrink dramatically, so a cooked cup of palak holds a lot more spinach than it looks.
• Paneer: weigh it raw, as it comes out of the pack. Pan-frying changes the weight a little, but the macros are mostly set by the block you started with. Add the oil separately.
• Eggs: log by number or by weight of the shelled raw egg. Boiled and scrambled eggs have almost the same macros.
• Roti: weigh the dough ball or the atta before cooking, or count rotis if you always make them the same size. Cooked roti weight changes with how long it sits on the tawa.
• Soya chunks: weigh them dry, before soaking. They swell several times over.

Does weighing really improve results?

Probably, though the evidence is more modest than the gym internet suggests.

A systematic review of 22 studies on self-monitoring (15 of them on diet) found that self-monitoring was consistently associated with weight loss, but the authors rated the evidence as weak because of methodological limits such as samples that were mostly white and female, and heavy reliance on self-report (Burke et al., 2011). So tracking seems to help, but we do not know exactly how precise it has to be.

The other half of the picture is that people misreport. A review comparing self-reported intake against doubly labelled water, an objective measure of energy use, concluded that no self-report method was clearly more accurate, and that participants’ own characteristics shaped the underreporting (Trabulsi et al., 2001). Portion-size error is one piece of that. A review of portion estimation tools found that image-based aids tended to be more accurate than food models or household utensils, though few validation studies were high quality (Amoutzopoulos et al., 2020).

None of this says scales are required. It says eyeballing is noisy, and a scale removes one of the noisiest steps for the foods that carry most of your calories.

A practical raw vs cooked routine

Keep it simple and you will keep doing it.

• Default to raw or dry weights for chicken, rice, dal, pasta, soya, paneer and oil.
• Choose a “raw” or “dry” database entry and save it as a favourite.
• For batch meals, use the pot method above.
• For restaurant and family meals, log a cooked entry and move on. Do not let a perfect log get in the way of a good week.
• Check the trend. If your scale weight does not move the way your log predicts over two or three weeks, adjust calories by a small step rather than chasing a decimal.

Want daily targets to log against? Use our macro calculator and protein calculator, or start from the free diet plan. If you are building meals around poultry and fish, chicken breast and fish in India: sourcing, cooking and cost covers the buying side, and the lean non-vegetarian foods ranking shows which cuts earn their place.

When to talk to a professional

Careful weighing is a tool, not a requirement for everyone. If tracking food makes you anxious, leads you to skip meals, or starts to feel compulsive, step back and speak to a doctor or a registered dietitian. The same goes if you have a medical condition, such as kidney disease, diabetes or a history of disordered eating, that needs specific dietary advice. Food tracking is not a good fit for everyone, and that is okay.

The bottom line

Weigh food raw or dry, log it against a raw or dry entry, and keep your oil on its own line. When you cannot weigh raw, use a cooked entry and accept a wider margin. For bulk cooking, weigh the dry ingredients into the pot, weigh the finished batch, and portion by cooked weight.

Water shifts the weight. It does not shift the macros. Match the state to the entry, and the scale does the rest.