Onions: cooked no added fat vs raw USDA FDC 2709950 vs 2709795
Per 100 g, cooked no added fat reports 141 mg sodium, while raw reports 1 mg sodium.
The comparison uses two cited USDA records. Their complete source names, household portions, nutrient values, and FoodData Central links remain visible below.
Highlighted difference
Sodium at the same 100-gram weight
Bar length shows the two cited values on one shared denominator. It does not rank either food or establish why they differ.
- Onions, cooked, no added fat 141 mg
141 mg - Onions, raw 1 mg
1 mg
Shared basis: 100 g · mg
Equal-weight evidence
Nutrition per 100 grams
Both columns use the same mass, which compares nutrient concentration without allowing the two representative source amounts to change the denominator. “A +” or “B +” reports the arithmetic difference between the cited values; it is not a quality score.
On smaller screens, focus a comparison table and scroll horizontally to read every column.
| Nutrient | A · Onions, cooked, no added fat | B · Onions, raw | Difference |
|---|---|---|---|
| Calories | 47 kcal | 38 kcal | A +9 kcal |
| Protein | 1.3 g | 0.9 g | A +0.4 g |
| Total fat | 0.1 g | 0.1 g | No difference at displayed precision |
| Carbohydrate | 11 g | 8.5 g | A +2.5 g |
| Dietary fiber | 2 g | 1.7 g | A +0.3 g |
| Total sugars | 5 g | 5.8 g | B +0.8 g |
| SodiumMaterial difference | 141 mg | 1 mg | A +140 mg |
| Saturated fat | 0 g | 0 g | No difference at displayed precision |
| Potassium | 171 mg | 171 mg | Same reported value |
| Calcium | 27 mg | 17 mg | A +10 mg |
| Iron | 0.3 mg | 0.2 mg | No difference at displayed precision |
Values come from the two cited USDA FoodData Central Survey Foods records. Feast does not average records, impute missing values, or infer a nutrient from the food name.
Read the table by question
Every material primary-nutrient difference on this page is numerically higher in A (1 of 1).
These answers describe concentration per 100 grams. “More” and “less” identify the arithmetic direction only; they do not decide which record is a better match or which food is better for a person.
Which reports fewer calories?
Record B
Record B reports 38 kcal, compared with 47 kcal in the other record—a difference of 9 kcal.
Which reports more protein?
Record A
Record A reports 1.3 g, compared with 0.9 g in the other record—a difference of 0.4 g.
Which reports more fiber?
Record A
Record A reports 2 g, compared with 1.7 g in the other record—a difference of 0.3 g.
Which reports less sodium?
Record B
Record B reports 1 mg, compared with 141 mg in the other record—a difference of 140 mg.
What differs in the source descriptions
The exact names carry information the numbers cannot.
USDA assigns both records to “Onions,” but the topic label is broad. Record A is “Onions, cooked, no added fat.” Record B is “Onions, raw.” Feast paired them because their contrast-neutral food identities are an exact match, not merely because they share a generic category.
The controlled name parser found 2 interpretable distinctions. These labels organize wording already present in the names; they do not establish that a distinction caused a nutrient difference.
| Description dimension | Record A | Record B |
|---|---|---|
| Preparation wording | No matching controlled term in the source name | raw |
| Added-fat wording | no added fat | No matching controlled term in the source name |
Even a clean name contrast can carry hidden companions. A fried record may also include coating; a restaurant record can use a different recipe; a reduced-sodium description can differ in more than salt; and a source amount can reflect a different reporting convention. That is why this page reports the complete pair rather than treating one word as an intervention.
Portion context
A representative source amount is not a shared “serving.”
Record A uses USDA reference amount at 105 g. Record B uses USDA reference amount at 15 g. Those labels and gram weights come from their respective records. They are useful for scaling the chosen profile, but they are not recommendations and need not describe equal amounts.
The two representative amounts differ by 90 g (86% of the larger amount). This is why the main table holds mass at 100 g. After selecting the closer description, use its household measure or a gram estimate for the amount actually eaten.
A cup, piece, slice, sandwich, fillet, or fluid ounce can have different gram weights across records. A matching label is not enough: check the listed grams. If accuracy matters more than convenience, weighing the food or using a current package label can be more specific than a generic survey-food measure.
Record A measures
- 1 cup210 g
- 1 slice15 g
- 1 whole148 g
- USDA reference amount105 g
Record B measures
- 1 slice15 g
- 1 ring5 g
- 1 cup160 g
- 1 whole148 g
- USDA reference amount15 g
One shared household label
1 cup: 210 g in A vs 160 g in B
The household label matches, but the source gram weights differ. These values scale each record by its own listed grams; they are practical portion context, not an equal-mass comparison.
| Nutrient | A · 210 g | B · 160 g |
|---|---|---|
| Calories | 99 kcal | 61 kcal |
| Protein | 2.7 g | 1.4 g |
| Dietary fiber | 4.2 g | 2.7 g |
| Sodium | 296 mg | 2 mg |
USDA source formulation evidence
The listed inputs provide another way to audit the match.
FNDDS includes input-food rows behind each standardized survey-food record. Record A’s leading listed inputs include Onions, raw, Salt, table. Record B’s include Onions, yellow, raw, Onions, white, raw, Onions, red, raw. Ingredient-code overlap is 0%, and normalized listed-input-weight variation is 100%.
Record A · 2 coded inputs
Onions, cooked, no added fat
- Onions, rawIngredient code 11282 · open source index99.7% of listed input weight
- Salt, tableIngredient code 2047 · open source index0.3% of listed input weight
Record B · 3 coded inputs
Onions, raw
- Onions, yellow, rawIngredient code 10025360% of listed input weight
- Onions, white, rawIngredient code 10025530% of listed input weight
- Onions, red, rawIngredient code 10025210% of listed input weight
0 shared coded inputs
The two listed formulations do not share an ingredient code in this source extract. Shared codes can still carry different listed weights.
2 A-only and 3 B-only coded inputs
A-only entries include Onions, raw, Salt, table. B-only entries include Onions, yellow, raw, Onions, white, raw, Onions, red, raw.
Important: repeated rows carrying the same ingredient code are combined before the shares and overlap are calculated. These weights belong to USDA’s source formulation: they are not a reconstructed plate, final cooked yield, visitor serving, ingredient declaration, or estimate of what is visible in a photo. USDA’s FNDDS documentation explains that these calculation recipes can represent multiple variants, may include retention or moisture adjustments, and are not product-label ingredient lists.
Choosing the closer record
Match context first; scale second.
- 01
Read both names literally
Compare cooking method, coating, edible skin or peel, sauce, additions, venue, source form, and food subtype. For this pair, the full A and B descriptions above are the evidence—not shortened search labels.
- 02
Use listed inputs as a check
If the name still leaves ambiguity, compare the leading and unique source inputs. They can reveal that two near names refer to meaningfully different standardized formulations, but they do not reconstruct your dish.
- 03
Choose an amount for that record
After choosing A or B, use its own named measure and gram weight. Do not transfer a cup, slice, or “typical amount” from the other record as if the measures were interchangeable.
- 04
Account for missing details
Brand, current restaurant recipe, cooking oil, drained weight, toppings, substitutions, and unfinished portions may not be captured. A label or weighed recipe can supersede a generic reference when it better matches the actual food.
Limits and responsible interpretation
This is a comparison of records, not a causal study.
The two records come from 2021–2023 FoodData Central Survey Foods data. The nutrient table faithfully compares their published values on the same weight basis. It does not measure two plates prepared at the same time, isolate one ingredient, or estimate the uncertainty around either value.
For this pair, the source names differ across 2 documented description dimensions, while the listed formulations show 0% ingredient-code overlap and 100% normalized listed-weight variation. Moisture, ingredient proportions, preparation, and record construction can therefore move together. The page can describe the combined record difference; it cannot isolate the effect of one word.
A higher or lower number is not an overall verdict. Protein, fiber, sodium, energy, fat, micronutrients, preferences, allergies, budget, portion, and an individual’s goals answer different questions. Feast therefore reports directions and magnitudes without applying a universal “healthier” label.
This page is educational and does not diagnose a condition, prescribe a target, or replace advice from a qualified professional. For an allergy, medically directed diet, or strict ingredient limit, use verified ingredient information and guidance appropriate to that situation.
How this page qualified
A page is published only when the pair clears materiality and diversity gates.
Both records must occupy the same USDA survey-food topic and share a close food identity after a controlled vocabulary separates preparation, edible-part, source, claim, crust, and sauce wording. Exact contrast-neutral identities receive priority. Close ingredient or form substitutions can qualify when name overlap remains high and the numerical evidence is material.
For primary nutrients, Feast requires both an absolute and relative difference: at least 20 kcal and 12% for energy; 2 g and 18% for protein or fat; 5 g and 15% for carbohydrate; 1 g and 20% for fiber; 4 g and 20% for sugars; or 100 mg and 20% for sodium. A focused one-nutrient pair also needs a material representative-amount or formulation distinction. Rounding-only pairs are not published.
Unordered FDC IDs define a canonical pair, so reversing A and B cannot create another page. Each source record can appear twice at most, each USDA topic contributes no more than 40 pages, and closely repeated identity families are capped. Those rules produced a selective comparison library rather than every mathematical combination in the corpus.
Read the complete nutrition-page methodology for import, nutrient mapping, portion scaling, Daily Value, and uncertainty rules.
Decision support from the exact records on this page
Turn source data into a better next decision
These conclusions and reading paths are computed from 2 exact records behind Onions, cooked, no added fat versus Onions, raw. Links are chosen by record identity, controlled contrast, formulation input, nutrient spread, or serving context—not by loose keyword similarity.
Equal-weight result
Onions, cooked, no added fat is higher in sodium per 100 g
Onions, cooked, no added fat reports 141 mg versus 1 mg for Onions, raw: a 140 mg difference when both are normalized to 100 g.
Inspect the underlying evidenceCheck the weight before comparing serving totals
Source amounts span 15–105 g
Onions, raw uses USDA source amount (15 g), while Onions, cooked, no added fat uses USDA source amount (105 g). Use per 100 g for equal-weight composition; use the serving column only when those named source amounts answer your question.
Record identity is part of the estimate
Distinguish “Onions, cooked, no added fat” from “Onions, raw”
These are separate USDA records with separate formulations or survey descriptions. Match preparation, additions, and the named household amount before borrowing either record’s nutrients.
Inspect the underlying evidenceContextual knowledge graph
Follow the relationship that matches your question
For Onions, cooked, no added fat versus Onions, raw, each path states why the destination belongs here, so you can distinguish a true evidentiary connection from a merely similar label.
Onions, cooked, no added fat and Onions, raw are explicitly linked in this guide, which separates direct name matches from contextual variants.
Follow this evidence path Put the observed spread in corpus context Sodium: density and serving contextIn this page’s records, sodium runs from 1 mg in Onions, raw to 141 mg in Onions, cooked, no added fat, all per 100 g.
Follow this evidence path Test a nearby record choice Onions, cooked, fat added vs Onions, rawOnions, raw is held as one side of the comparison. The explicit record-description contrast is Preparation wording: No matching controlled term in the source name versus raw; it is a selection cue, not evidence of cause.
Follow this evidence path A formulation detail that separates records Onions, rawUSDA input 11282 appears in 1 of 2 context records; its summed listed input weight spans 100–100 g across those source formulations. These are source-formulation input weights, not plated or serving weights. Follow the code to inspect every represented occurrence.
Follow this evidence path A formulation detail that separates records Salt, tableUSDA input 2047 appears in 1 of 2 context records; its summed listed input weight spans 0.3–0.3 g across those source formulations. These are source-formulation input weights, not plated or serving weights. Follow the code to inspect every represented occurrence.
Follow this evidence path Test a nearby record choice Onions, cooked, fat added vs Onions, cooked, no added fatOnions, cooked, no added fat is held as one side of the comparison. The explicit record-description contrast is Added-fat wording: added fat versus no added fat; it is a selection cue, not evidence of cause.
Follow this evidence path Inspect an exact record Onions, cooked, no added fatOpen the full nutrient table, household measures, formulation inputs, and FoodData Central 2709950 citation for this exact record—not a name-level average.
Follow this evidence path