Onions100 g vs 100 gTwo cited FDC recordsUpdated

Onions, green: cooked vs raw USDA FDC 2709953 vs 2709794

Per 100 g, cooked reports 63 calories, while raw reports 32 calories.

The comparison uses two cited USDA records. Their complete source names, household portions, nutrient values, and FoodData Central links remain visible below.

Record A · FDC 2709953

Onions, green, cooked

Check this record in FoodData Central ↗

Record B · FDC 2709794

Onions, green, raw

Check this record in FoodData Central ↗

Highlighted difference

Calories 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.

  1. 63 kcal
  2. 32 kcal

Shared basis: 100 g · kcal

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.

Per-100-gram nutrient comparison for Onions, green, cooked and Onions, green, raw
NutrientA · Onions, green, cookedB · Onions, green, rawDifference
CaloriesMaterial difference 63 kcal 32 kcal A +31 kcal
Protein 2.1 g 1.8 g A +0.3 g
Total fatMaterial difference 3.2 g 0.2 g A +3 g
Carbohydrate 8.4 g 7.3 g A +1 g
Dietary fiber 3 g 2.6 g A +0.4 g
Total sugars 2.7 g 2.3 g A +0.3 g
SodiumMaterial difference 161 mg 16 mg A +145 mg
Saturated fat 0.8 g 0 g A +0.8 g
Potassium 315 mg 276 mg A +39 mg
Calcium 83 mg 72 mg A +11 mg
Iron 1.7 mg 1.5 mg A +0.2 mg

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 (3 of 3).

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 32 kcal, compared with 63 kcal in the other record—a difference of 31 kcal.

Which reports more protein?

Record A

Record A reports 2.1 g, compared with 1.8 g in the other record—a difference of 0.3 g.

Which reports more fiber?

Record A

Record A reports 3 g, compared with 2.6 g in the other record—a difference of 0.4 g.

Which reports less sodium?

Record B

Record B reports 16 mg, compared with 161 mg in the other record—a difference of 145 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, green, cooked.” Record B is “Onions, green, 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 1 interpretable distinction. These labels organize wording already present in the names; they do not establish that a distinction caused a nutrient difference.

Controlled wording distinctions
Description dimensionRecord ARecord B
Preparation wordingNo matching controlled term in the source nameraw

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 15 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 representative amounts do not cross Feast’s material portion-difference threshold of both 15 grams and 20%. They are still separate source measures, so the 100-gram table remains the appropriate place for an equal-weight comparison.

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.

One shared household label

1 cup: 225 g in A vs 100 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.

Nutrition for one 1 cup using each record’s own source gram weight
NutrientA · 225 gB · 100 g
Calories142 kcal32 kcal
Protein4.7 g1.8 g
Dietary fiber6.8 g2.6 g
Sodium362 mg16 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, spring or scallions (includes tops and bulb), raw, Oil or table fat, NFS, Salt, table. Record B’s include Onions, spring or scallions (includes tops and bulb), raw. Ingredient-code overlap is 33%, and normalized listed-input-weight variation is 3%.

1 shared coded input

The largest shared entries include Onions, spring or scallions (includes tops and bulb), raw. Shared codes can still carry different listed weights.

2 A-only and 0 B-only coded inputs

A-only entries include Oil or table fat, NFS, Salt, table.

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.

USDA shorthand in this evidence
  • NFS means “not further specified.” The record intentionally leaves the exact subtype, size, or preparation unresolved.

Choosing the closer record

Match context first; scale second.

  1. 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.

  2. 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.

  3. 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.

  4. 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 1 documented description dimension, while the listed formulations show 33% ingredient-code overlap and 3% 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, green, cooked versus Onions, green, 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, green, cooked is higher in calories per 100 g

Onions, green, cooked reports 63 kcal versus 32 kcal for Onions, green, raw: a 31 kcal difference when both are normalized to 100 g.

Inspect the underlying evidence

These listed servings have equal weights

2 listed servings each weigh 15 g

The 2 records with a listed serving weight on this page each use 15 g. Their serving totals therefore compare equal weights, even if the household labels differ. Match the preparation and adjust the weight to the amount you eat.

Record identity is part of the estimate

Distinguish “Onions, green, cooked” from “Onions, green, 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 evidence

Contextual knowledge graph

Follow the relationship that matches your question

For Onions, green, cooked versus Onions, green, raw, each path states why the destination belongs here, so you can distinguish a true evidentiary connection from a merely similar label.

Best next guide for this exact record Onions

Onions, green, cooked and Onions, green, 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 Calories: density and serving context

In this page’s records, calories runs from 32 kcal in Onions, green, raw to 63 kcal in Onions, green, cooked, all per 100 g.

Follow this evidence path
A formulation detail that separates records Oil or table fat, NFS

USDA input 81200100 appears in 1 of 2 context records; its summed listed input weight spans 3–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
A formulation detail that separates records Salt, table

USDA 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
Put the observed spread in corpus context Sodium: density and serving context

In this page’s records, sodium runs from 16 mg in Onions, green, raw to 161 mg in Onions, green, cooked, all per 100 g.

Follow this evidence path
Inspect an exact record Onions, green, cooked

Open the full nutrient table, household measures, formulation inputs, and FoodData Central 2709953 citation for this exact record—not a name-level average.

Follow this evidence path
Check another exact record Onions, green, raw

Open the full nutrient table, household measures, formulation inputs, and FoodData Central 2709794 citation for this exact record—not a name-level average.

Follow this evidence path