Count calories when the food is raw or cooked?
viraurelianus
Posts: 13
i suppose this question has been asked a lot of times, but i'd like an answer from someone who knows the answer for real.
should i consider the raw weight of a food or the cooked one? because with foods like lentils and rice it changes a lot. i suppose it should be counted when raw, because the cooked version has just some extra water, but this is just a supposition and i want a real answer.
should i consider the raw weight of a food or the cooked one? because with foods like lentils and rice it changes a lot. i suppose it should be counted when raw, because the cooked version has just some extra water, but this is just a supposition and i want a real answer.
0
Replies
-
Raw will be more accurate (unless the food's label gives the cooked weight - for instance: bacon). You can weigh food after cooking and get pretty close to accurate if you make sure to use the appropriate and accurate entry in the database (ie don't use a boiled entry if you grilled it, etc)0
-
Stick to one or the other and be consistent with it. I weigh cooked on all meats unless the back packaging states otherwise. Also, I freeze my meat which in turns adds ice which adds more weight.
0 -
martyqueen52 wrote: »Stick to one or the other and be consistent with it. I weigh cooked on all meats unless the back packaging states otherwise. Also, I freeze my meat which in turns adds ice which adds more weight.
I believe the ice comes from water which was in the food before u froze it. No weight is added.......
0 -
It's all about consistency. I try to log raw just because that's my preference and it's easier to find in the database sometimes. But there's nothing wrong with cooking and then weighing, you just have to find accurate entries or make sure the food label tells you portion size for cooked.
Sometimes, especially if you're cooking for more than one person, you have to log cooked and that's no big deal.0 -
I log raw unless the packaging says to weigh it cooked. Just pick a method and stick with it. Consistency is key.0
-
I try to stick to measuring raw when I'm eating the food raw and measuring cooked when I'm eating the food cooked. Calorie counts actually change when cooking food because you're burning off some of the calories during the cooking process. In other words, cooked foods usually have less calories than their raw version. Meats, especially, change calories because a lot of the fat drains off while it cooks. The only exception to this is when I'm cooking a bunch of foods together in a casserole or soup.0
-
There is no "real" answer. The most important part of this is finding an appropriate entry in the database. Don't log cooked as raw or vice versa. That said, raw can be a bit more accurate as the length of time spent cooking something affects the amount of water weight in the cooked product. Generally the difference is small enough to be considered random variation, so it's not something to be overly concerned about.
I personally prefer to log raw whenever possible, especially with items that absorb water like pasta, lentils, etc.0
Categories
- All Categories
- 1.4M Health, Wellness and Goals
- 393.4K Introduce Yourself
- 43.8K Getting Started
- 260.2K Health and Weight Loss
- 175.9K Food and Nutrition
- 47.4K Recipes
- 232.5K Fitness and Exercise
- 424 Sleep, Mindfulness and Overall Wellness
- 6.5K Goal: Maintaining Weight
- 8.5K Goal: Gaining Weight and Body Building
- 153K Motivation and Support
- 8K Challenges
- 1.3K Debate Club
- 96.3K Chit-Chat
- 2.5K Fun and Games
- 3.7K MyFitnessPal Information
- 24 News and Announcements
- 1.1K Feature Suggestions and Ideas
- 2.6K MyFitnessPal Tech Support Questions