Raw vs Cooked Nutrition is the main hub for understanding why nutrition facts can change when food is boiled, baked, steamed, roasted, drained, or otherwise prepared. Preparation often changes water weight and serving weight, which can change values per 100g. A cooked food can look more calorie-dense per 100g after water loss, while foods that absorb water can look lower per 100g. Use this guide to understand raw/cooked record pairs, water-weight changes, drained or cooked weights, and the best way to match a nutrition value to the form of food being compared.
Why raw and cooked nutrition facts can differ
Contents
- 1 Why raw and cooked nutrition facts can differ
- 2 Who this raw vs cooked guide is for
- 3 The comparison basis comes first
- 4 What a raw-vs-cooked article should show readers
- 5 Why water change matters
- 6 How this hub connects to food profiles
- 7 Using preparation data carefully
- 8 Browse the main sections
- 9 Key topics to explore next
- 10 Tools that can help you check the numbers
- 11 How eNutritionFacts handles sources
- 12 Raw and cooked record pairs
- 13 Weight change and tracking basis
- 14 Preparation methods covered
- 15 How to compare pages in this hub
- 16 How to read uncertainty in nutrition data
- 17 How source notes help readers trust the page
- 18 How this hub connects with methodology and review policies
- 19 How this hub stays useful as the site grows
- 20 Frequently asked questions
- 21 Why water weight changes the numbers
- 22 How to match the record to the food form
- 23 How this hub connects preparation articles
- 24 When preparation data needs extra caution
- 25 Editorial trust for this hub
Preparation can change the weight of a food by removing or adding water. That change can make the same food look different per 100g even when the ingredient itself has not become a different food. This is why raw and cooked records need to be compared carefully.
A useful raw-vs-cooked page identifies both source records, the preparation method, the comparison basis, and any weight-change context. That helps readers understand the data without turning cooking differences into broad health claims.
Who this raw vs cooked guide is for
This guide is for readers who want to understand why the same food can show different nutrition values before and after preparation. It is especially useful for foods that change water weight, such as vegetables, grains, potatoes, legumes, meat, seafood, and cooked greens.
The goal is to explain the comparison basis clearly. A raw-vs-cooked page does not turn preparation differences into broad health claims. It should show which source records are being compared, what preparation method is used, and why the numbers may look different per 100g or per serving.
The comparison basis comes first
A raw value and a cooked value can only be compared responsibly when the food form is clear. Raw broccoli should not be compared with a cooked broccoli record unless the article says which cooked method is used. Boiled, steamed, roasted, drained, baked, air-fried, and microwaved foods can show different values because the final weight and water content may differ.
Per-100g comparisons are useful, but they can be misunderstood when water changes. A food that loses water may look more concentrated per 100g. A food that absorbs water may look less concentrated per 100g. The article needs to explain that before readers interpret the table.
What a raw-vs-cooked article should show readers
A strong preparation-impact page should show the raw source record, the cooked source record, the data type, the method, the comparison basis, and a short weight-change note. When a record is not a perfect match, the page should explain the limitation rather than presenting the comparison as exact.
The most useful pages also tell readers which form to use when logging or comparing foods. A cautious general rule is to match the record to the form being measured: raw record for raw weight, cooked record for cooked weight, and a preparation method that is as close as possible to the food being eaten.
Why water change matters
Water can move in several directions during preparation. Rice, oats, and some grains absorb water. Many vegetables lose or gain water depending on the method. Roasting can concentrate food by removing moisture. Boiling can add water to some foods while also creating drained portions. These changes affect per-100g values.
This is why a cooked food can look different even when the ingredient is the same. The change may come from weight and water balance rather than from a simple gain or loss of nutrients. A good preparation-impact article makes that distinction visible.
How this hub connects to food profiles
Food profiles give the nutrition facts for a selected record. Preparation-impact pages explain why a second record for the same food may not match. When a food has common raw and cooked forms, the profile can link readers to the relevant raw-vs-cooked comparison for deeper context.
This connection is especially useful for spinach, broccoli, carrots, rice, potatoes, chicken, salmon, oats, and other foods where preparation changes the comparison basis. The hub gives readers one place to understand the method before opening the individual comparisons.
Using preparation data carefully
Preparation data are best used with care because the exact method, time, added ingredients, drained liquid, and portion size can change the result. A boiled potato and a baked potato are not the same record. A plain cooked chicken breast and a seasoned prepared chicken product are not the same comparison.
For that reason, preparation-impact pages should stay practical and transparent. The article can explain patterns and source differences, but it should avoid broad promises or personal recommendations. The reader should leave with a clearer method for reading the data, not a one-size-fits-all rule.
Browse the main sections
This hub groups related pages by reader intent. Use the table below to choose the right starting point before opening a specific food profile, label guide, comparison, or data tool.
| Section | What it helps with | Useful next step |
|---|---|---|
| Raw vs cooked records | Related pages grouped by the same reader intent. | Open the closest specific guide or comparison page. |
| Weight change | Related pages grouped by the same reader intent. | Open the closest specific guide or comparison page. |
| Cooking method variants | Related pages grouped by the same reader intent. | Open the closest specific guide or comparison page. |
| Tracking basis | Related pages grouped by the same reader intent. | Open the closest specific guide or comparison page. |
Key topics to explore next
The pages below are natural next steps for readers who want a more specific answer. Some pages may already be available, while others may be added as the cluster grows. When a listed page is live, use it as the focused guide for that narrower question.
- Raw vs Cooked Broccoli Nutrition Facts
- Raw vs Cooked Chicken Breast Nutrition Facts
- Boiled vs Baked Potato Nutrition Facts
- Raw vs Cooked Carrots Nutrition Facts
- Raw vs Cooked Salmon Nutrition Facts
- How to Track Macros: Raw vs Cooked Weight
- Steamed vs Boiled Vegetables: Nutrient Comparison
Tools that can help you check the numbers
Tools are useful when a reader needs to check another food form, compare values, or understand serving-size context. They do not replace the source notes in each article, but they can make the data easier to explore.
How eNutritionFacts handles sources
Food data pages identify the source record, food form, data type, per-100g basis, serving-size basis when available, and last checked date. Label and ingredient pages start from the relevant label, regulatory, or methodology source before adding interpretation. This makes the source path easier to audit and helps readers understand why two similar foods or labels may not show identical values.
Read more about the site’s source process in the Nutrition Data Methodology and about review routing in the Expert Review Policy.
Raw and cooked record pairs
Raw-vs-cooked pages are most useful when they compare matching source records. Each comparison should identify the raw or uncooked record, the cooked or prepared record, the data type, and the comparison basis.
Weight change and tracking basis
Cooking can remove water, add water, drain liquid, or change the edible portion. That can change values per 100g. Readers who weigh food should match the record to the form they are using: raw record for raw weight, cooked record for cooked weight, and a clear note when a recipe uses both.
Preparation methods covered
The most useful comparisons include boiled, baked, steamed, roasted, drained, air-fried, freeze-dried, and raw forms when source records are available. The method matters because water change and edible portion change can affect the comparison basis.
How to compare pages in this hub
The most useful comparison starts by matching the question to the page type. A food profile is best for one specific food. A comparison page is best when two foods need to be viewed side by side. A label guide is best when the reader needs to understand a term on a package. A preparation-impact guide is best when raw and cooked values seem different.
This hub brings those page types together so readers do not have to treat every nutrition number the same way. A calorie value, a sodium value, a fiber value, and an ingredient term all need context. The right page gives that context before the reader makes a comparison.
How to read uncertainty in nutrition data
Nutrition data is precise enough to be useful, but it is not identical across every food, product, recipe, or serving. Natural foods can vary by variety, ripeness, growing conditions, edible portion, and preparation. Packaged foods can vary by formulation, serving label, and update date. Cooked foods can vary by water content and method.
A careful nutrition page explains those limits without making the data feel unusable. The number is still valuable when the source is clear. The limit simply tells readers how closely that number matches the food, form, and serving they are actually checking.
How source notes help readers trust the page
Source notes are not decorative. They tell readers whether the page is based on a USDA record, a branded-food label record, a regulatory definition, a preparation-method comparison, or a site methodology explanation. A clear source note makes the article easier to verify and easier to refresh when data changes.
For food pages, the most useful source note identifies the food name, FDC ID, data type, serving basis, and last checked date when available. For label and ingredient pages, the most useful source note identifies the guidance or definition used to clarify the label wording.
How this hub connects with methodology and review policies
Methodology pages explain how the site handles source records, serving-size context, data checks, and update logic. Review-policy pages explain when an article needs a writer, data check, scientific review, or clinical review route. Those trust pages are part of the reading path when a topic becomes more complex.
The goal is to keep the public article clear while still making the evidence path visible. Readers do not need to understand the internal workflow to benefit from the page. They are best able to see what source was used, what the page is explaining, and where to read more about the site’s standards.
How this hub stays useful as the site grows
A strong hub is not a one-time index. It becomes more useful as related pages are added, refreshed, and connected. When a new food profile, label guide, preparation comparison, or ingredient explainer is published, the relevant hub can help readers find it in context.
This matters because nutrition reference sites can become difficult to browse when they grow. A clear hub keeps the most important paths visible: start broad, choose the right group, open a focused page, check the source, and use a tool when comparison or verification helps.
Frequently asked questions
Is this hub a substitute for personalized nutrition advice?
No. This hub explains nutrition data, labels, ingredients, or comparisons for educational use. Personal nutrition decisions can depend on health history, medication, age, pregnancy, allergies, and other factors that require qualified guidance.
Why does eNutritionFacts use source records?
Source records make nutrition values traceable. Food composition can vary by data type, preparation method, brand, serving size, and update date, so each article should identify the record or guidance used whenever possible.
Related pages are connected through contextual links to the relevant hub, nearby guides, methodology pages, and tools that help readers verify or compare the information.
When does a page need expert review?
Expert review is recommended when a page moves beyond basic label reading or data explanation into health-sensitive interpretation, clinical conditions, pediatric nutrition, pregnancy, breastfeeding, allergens, metabolic health, or contested ingredient safety.
This hub is for educational and informational purposes only and is not medical advice. Individual nutrition needs may vary. See the Medical Disclaimer.
Why water weight changes the numbers
Cooking often changes water content. Some foods lose water during roasting, baking, grilling, or pan cooking. Other foods absorb water during boiling or simmering. Because nutrition tables commonly show values per 100g, a water-weight change can make a cooked food look more concentrated or less concentrated even when the ingredient has not become a different food.
This is why raw and cooked records need careful reading. A raw record describes the food before preparation. A cooked record describes the food after a specific method. The record that matches the weighed food is usually the clearer comparison basis.
How to match the record to the food form
A reader comparing raw broccoli with steamed broccoli needs to know which cooked method is being used. Boiled, steamed, roasted, microwaved, and drained forms can differ. Rice, potatoes, oats, beans, chicken, salmon, carrots, and spinach can all change weight during preparation. The article must identify the form before interpreting the values.
The best reader experience is a clear source pair: one raw or uncooked record, one cooked or prepared record, the data type, the method, and the comparison basis. When the records are not perfect matches, the page should say that plainly.
How this hub connects preparation articles
The hub gives readers one place to understand the pattern before opening a specific comparison. Raw vs cooked spinach, raw vs cooked broccoli, boiled vs baked potato, raw vs cooked carrots, raw vs cooked chicken breast, and raw vs cooked salmon all need the same basic method: name the records, state the preparation method, compare the values, and explain the weight basis.
That structure helps keep each preparation page practical. The page can explain why values differ without turning cooking method differences into broad health claims or personal dietary advice.
When preparation data needs extra caution
Preparation data can become misleading when added ingredients are mixed into the record. Plain boiled potato is different from potato prepared with oil, butter, or sauce. Plain cooked chicken is different from a breaded or seasoned prepared product. A clear article keeps those forms separate and tells readers when a record includes more than the base food.
The hub also helps readers understand that tracking raw weight and cooked weight are not interchangeable unless the conversion is stated. That makes the page useful for label reading, cooking comparisons, and food logging without becoming app-specific advice.