Cooked vs Raw Calorie Count
tanyamum
Posts: 39 Member
Hi guys and gals. Just wondering if anyone could tell me if the calorie amounts listed are for raw or cooked please?
0
Replies
-
Use entries that specify one or the other. Generally, weighing raw is going to be more accurate.2
-
I weigh raw whenever possible unless other wise specified.
cooking can dramatically change weight once cooked.
If it’s a packaged food at it says let’s say 5 pieces for x amount of calories, I weigh out 5 peices (raw) and log by weight in grams if possible.0 -
If your entry doesn't list raw or cooked, it is a user-created entry rather than an entry that MFP pulled from the USDA Database, which always lists raw or cooked when that would be a thing.
Unfortunately, the "verified" green check marks in the MFP database are used for both user-created entries and admin-created entries that MFP pulled from the USDA database. To find admin entries for whole foods, I get the syntax from the USDA database and paste that into MFP.
For packaged foods, I verify the label against what I find in MFP.
1 -
Hi guys and gals. Just wondering if anyone could tell me if the calorie amounts listed are for raw or cooked please?
Some foods will have both in the database. It is more accurate to use raw or dried entries because cooking methods can make a big deference, especially with things like rice, beans, pasta, etc.1 -
Sometimes you weigh it raw, sometimes cooked.
Bacon can leave half its calories in the skillet. Same for a hamburger. Weight them cookked and go to USDA for the "cooked" calorie count.
Rice can be cooked weighing much more due to more or less water depending on the way you prefer it.
All of these make raw weight highly inaccurate.0 -
wilson10102018 wrote: »Sometimes you weigh it raw, sometimes cooked.
Bacon can leave half its calories in the skillet. Same for a hamburger. Weight them cookked and go to USDA for the "cooked" calorie count.
Rice can be cooked weighing much more due to more or less water depending on the way you prefer it.
All of these make raw weight highly inaccurate.
If you cook fat out, "cooked" may or may not be accurate.
If you cook water in, "raw" or dried" is the only possible way to be accurate.0 -
wilson10102018 wrote: »Sometimes you weigh it raw, sometimes cooked.
Bacon can leave half its calories in the skillet. Same for a hamburger. Weight them cookked and go to USDA for the "cooked" calorie count.
Rice can be cooked weighing much more due to more or less water depending on the way you prefer it.
All of these make raw weight highly inaccurate.
If you cook fat out, "cooked" may or may not be accurate.
If you cook water in, "raw" or dried" is the only possible way to be accurate.
Yes, I inserted the sentence before I added the rice. Rice must be weighed raw.
But, anything with rendered fat should be weighed cooked. If you "cook fat out" that is rendered fat and unless you put the fat in your recipe, cooked weight is accurate and the only way. I like bacon crisp and have weighed and rated it before and after and for me it loses about one-half the calories to the skillet.
For my part, I ignore rendered fish oil and weigh the fish raw even though there is often quite a bit of rendered fat from salmon.
0
This discussion has been closed.
Categories
- All Categories
- 1.4M Health, Wellness and Goals
- 393.6K Introduce Yourself
- 43.8K Getting Started
- 260.3K Health and Weight Loss
- 176K Food and Nutrition
- 47.5K Recipes
- 232.6K Fitness and Exercise
- 431 Sleep, Mindfulness and Overall Wellness
- 6.5K Goal: Maintaining Weight
- 8.6K 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.8K MyFitnessPal Information
- 24 News and Announcements
- 1.1K Feature Suggestions and Ideas
- 2.6K MyFitnessPal Tech Support Questions