Cucumber: cooked vs raw USDA FDC 2709928 vs 2709784
Per 100 g, cooked reports 45 calories, while raw reports 16 calories.
The comparison uses two cited USDA records. Their complete source names, household portions, nutrient values, and FoodData Central links remain visible below.
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.
- Cucumber, cooked 45 kcal
45 kcal - Cucumber, raw 16 kcal
16 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.
| Nutrient | A · Cucumber, cooked | B · Cucumber, raw | Difference |
|---|---|---|---|
| CaloriesMaterial difference | 45 kcal | 16 kcal | A +29 kcal |
| Protein | 0.7 g | 0.6 g | A +0.1 g |
| Total fatMaterial difference | 3.2 g | 0.2 g | A +3 g |
| Carbohydrate | 3.4 g | 3 g | A +0.4 g |
| Dietary fiber | 0.6 g | 0.5 g | A +0.1 g |
| Total sugars | 1.9 g | 1.7 g | A +0.2 g |
| SodiumMaterial difference | 145 mg | 2 mg | A +143 mg |
| Saturated fat | 0.8 g | 0 g | A +0.8 g |
| Potassium | 194 mg | 170 mg | A +24 mg |
| Calcium | 19 mg | 16 mg | A +3 mg |
| Iron | 0 mg | 0 mg | Same reported value |
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 16 kcal, compared with 45 kcal in the other record—a difference of 29 kcal.
Which reports more protein?
Record A
Record A reports 0.7 g, compared with 0.6 g in the other record—a difference of 0.1 g.
Which reports more fiber?
Record A
Record A reports 0.6 g, compared with 0.5 g in the other record—a difference of 0.1 g.
Which reports less sodium?
Record B
Record B reports 2 mg, compared with 145 mg in the other record—a difference of 143 mg.
What differs in the source descriptions
The exact names carry information the numbers cannot.
USDA assigns both records to “Other vegetables and combinations,” but the topic label is broad. Record A is “Cucumber, cooked.” Record B is “Cucumber, 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.
| Description dimension | Record A | Record B |
|---|---|---|
| Preparation wording | No matching controlled term in the source name | raw |
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 93 g. Record B uses USDA reference amount at 60 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 33 g (35% 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 cup185 g
- 1 slice10 g
- USDA reference amount93 g
Record B measures
- 1 piece/slice10 g
- 1 stick10 g
- 1 regular200 g
- 1 miniature65 g
- 1 cup120 g
- USDA reference amount60 g
One shared household label
1 cup: 185 g in A vs 120 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 · 185 g | B · 120 g |
|---|---|---|
| Calories | 83 kcal | 19 kcal |
| Protein | 1.3 g | 0.7 g |
| Dietary fiber | 1.1 g | 0.6 g |
| Sodium | 268 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 Cucumber, with peel, raw, Oil or table fat, NFS, Salt, table. Record B’s include Cucumber, with peel, raw. Ingredient-code overlap is 33%, and normalized listed-input-weight variation is 3%.
Record A · 3 coded inputs
Cucumber, cooked
- Cucumber, with peel, rawIngredient code 11205 · open source index96.8% of listed input weight
- Oil or table fat, NFSIngredient code 81200100 · open source index2.9% of listed input weight
- Salt, tableIngredient code 2047 · open source index0.3% of listed input weight
Record B · 1 coded input
Cucumber, raw
- Cucumber, with peel, rawIngredient code 11205 · open source index100% of listed input weight
1 shared coded input
The largest shared entries include Cucumber, with peel, 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.
- 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.
- 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 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 Cucumber, cooked versus Cucumber, raw. Links are chosen by record identity, controlled contrast, formulation input, nutrient spread, or serving context—not by loose keyword similarity.
Equal-weight result
Cucumber, cooked is higher in calories per 100 g
Cucumber, cooked reports 45 kcal versus 16 kcal for Cucumber, raw: a 29 kcal difference when both are normalized to 100 g.
Inspect the underlying evidenceCheck the weight before comparing serving totals
Source amounts span 60–93 g
Cucumber, raw uses USDA source amount (60 g), while Cucumber, cooked uses USDA source amount (93 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 “Cucumber, cooked” from “Cucumber, 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 Cucumber, cooked versus Cucumber, raw, each path states why the destination belongs here, so you can distinguish a true evidentiary connection from a merely similar label.
Cucumber, cooked and Cucumber, 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 contextIn this page’s records, calories runs from 16 kcal in Cucumber, raw to 45 kcal in Cucumber, cooked, all per 100 g.
Follow this evidence path A formulation detail that separates records Oil or table fat, NFSUSDA 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, 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 Put the observed spread in corpus context Sodium: density and serving contextIn this page’s records, sodium runs from 2 mg in Cucumber, raw to 145 mg in Cucumber, cooked, all per 100 g.
Follow this evidence path 2 context records in this source topic Other vegetables and combinationsCucumber, cooked and Cucumber, raw belong to this USDA source-category collection. Its displayed ranges and complete exact-record catalog provide the peer set for a manual comparison; the destination does not preselect this page’s record.
Follow this evidence path Inspect an exact record Cucumber, cookedOpen the full nutrient table, household measures, formulation inputs, and FoodData Central 2709928 citation for this exact record—not a name-level average.
Follow this evidence path