Pizza, no cheese: thick vs thin USDA FDC 2708675 vs 2708674
Per 100 g, thick reports 38.3 g carbohydrate, while thin reports 31 g carbohydrate.
The comparison uses two cited USDA records. Their complete source names, household portions, nutrient values, and FoodData Central links remain visible below.
Highlighted difference
Carbohydrate 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.
-
38.3 g -
31 g
Shared basis: 100 g · g
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 · Pizza, no cheese, thick crust | B · Pizza, no cheese, thin crust | Difference |
|---|---|---|---|
| Calories | 293 kcal | 276 kcal | A +17 kcal |
| Protein | 7.6 g | 7.5 g | A +0.1 g |
| Total fat | 12.3 g | 13.7 g | B +1.4 g |
| CarbohydrateMaterial difference | 38.3 g | 31 g | A +7.3 g |
| Dietary fiber | 1.9 g | 1.8 g | A +0.1 g |
| Total sugars | 5.5 g | 5 g | A +0.4 g |
| Sodium | 514 mg | 551 mg | B +37 mg |
| Saturated fat | 2.8 g | 3.4 g | B +0.6 g |
| Potassium | 171 mg | 195 mg | B +24 mg |
| Calcium | 23 mg | 26 mg | B +3 mg |
| Iron | 3 mg | 2.8 mg | A +0.3 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 (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 276 kcal, compared with 293 kcal in the other record—a difference of 17 kcal.
Which reports more protein?
Record A
Record A reports 7.6 g, compared with 7.5 g in the other record—a difference of 0.1 g.
Which reports more fiber?
Record A
Record A reports 1.9 g, compared with 1.8 g in the other record—a difference of 0.1 g.
Which reports less sodium?
Record A
Record A reports 514 mg, compared with 551 mg in the other record—a difference of 37 mg.
What differs in the source descriptions
The exact names carry information the numbers cannot.
USDA assigns both records to “Pizza,” but the topic label is broad. Record A is “Pizza, no cheese, thick crust.” Record B is “Pizza, no cheese, thin crust.” 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 |
|---|---|---|
| Crust wording | thick crust | thin crust |
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 248 g. Record B uses USDA reference amount at 150 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 98 g (40% 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 piece, NFS124 g
- 1 piece, small pizza82 g
- 1 piece, medium pizza84 g
- 1 piece, large pizza124 g
- 1 piece, extra-large pizza129 g
- 1 personal size pizza (5-7" diameter)207 g
- 1 small pizza (8-10" diameter)495 g
- 1 medium pizza (11-12" diameter)676 g
Record B measures
- 1 piece, NFS75 g
- 1 piece, small pizza51 g
- 1 piece, medium pizza54 g
- 1 piece, large pizza75 g
- 1 piece, extra-large pizza81 g
- 1 personal size pizza (5-7" diameter)110 g
- 1 small pizza (8-10" diameter)306 g
- 1 medium pizza (11-12" diameter)432 g
One shared household label
1 medium pizza (11-12" diameter): 676 g in A vs 432 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 · 676 g | B · 432 g |
|---|---|---|
| Calories | 1,981 kcal | 1,192 kcal |
| Protein | 51.2 g | 32.2 g |
| Dietary fiber | 12.8 g | 7.8 g |
| Sodium | 3,475 mg | 2,380 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 Flour, wheat, all-purpose, enriched, bleached, Beverages, water, tap, drinking, Sauce, pasta, spaghetti/marinara, ready-to-serve, Olives, ripe, canned (small-extra large). Record B’s include Flour, wheat, all-purpose, enriched, bleached, Sauce, pasta, spaghetti/marinara, ready-to-serve, Beverages, water, tap, drinking, Olives, ripe, canned (small-extra large). Ingredient-code overlap is 100%, and normalized listed-input-weight variation is 14%.
Record A · 13 coded inputs
Pizza, no cheese, thick crust
- Flour, wheat, all-purpose, enriched, bleachedIngredient code 20081 · open source index32.2% of listed input weight
- Beverages, water, tap, drinkingIngredient code 14411 · open source index20.4% of listed input weight
- Sauce, pasta, spaghetti/marinara, ready-to-serveIngredient code 6931 · open source index12.4% of listed input weight
- Olives, ripe, canned (small-extra large)Ingredient code 9193 · open source index5.1% of listed input weight
- Onions, rawIngredient code 11282 · open source index5.1% of listed input weight
- Pepperoni, beef and pork, slicedIngredient code 7057 · open source index5.1% of listed input weight
- Peppers, bell, green, rawIngredient code 11333 · open source index5.1% of listed input weight
- Sausage, Italian, pork, mild, cooked, pan-friedIngredient code 7089 · open source index5.1% of listed input weight
Record B · 13 coded inputs
Pizza, no cheese, thin crust
- Flour, wheat, all-purpose, enriched, bleachedIngredient code 20081 · open source index24.7% of listed input weight
- Sauce, pasta, spaghetti/marinara, ready-to-serveIngredient code 6931 · open source index16.9% of listed input weight
- Beverages, water, tap, drinkingIngredient code 14411 · open source index15.6% of listed input weight
- Olives, ripe, canned (small-extra large)Ingredient code 9193 · open source index7% of listed input weight
- Onions, rawIngredient code 11282 · open source index7% of listed input weight
- Pepperoni, beef and pork, slicedIngredient code 7057 · open source index7% of listed input weight
- Peppers, bell, green, rawIngredient code 11333 · open source index7% of listed input weight
- Sausage, Italian, pork, mild, cooked, pan-friedIngredient code 7089 · open source index7% of listed input weight
13 shared coded inputs
The largest shared entries include Flour, wheat, all-purpose, enriched, bleached, Beverages, water, tap, drinking, Sauce, pasta, spaghetti/marinara, ready-to-serve, Olives, ripe, canned (small-extra large), Onions, raw. Shared codes can still carry different listed weights.
0 A-only and 0 B-only coded inputs
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 100% ingredient-code overlap and 14% 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 Pizza, no cheese, thick crust versus Pizza, no cheese, thin crust. Links are chosen by record identity, controlled contrast, formulation input, nutrient spread, or serving context—not by loose keyword similarity.
Equal-weight result
Pizza, no cheese, thick crust is higher in carbohydrate per 100 g
Pizza, no cheese, thick crust reports 38.3 g versus 31 g for Pizza, no cheese, thin crust: a 7.3 g difference when both are normalized to 100 g.
Inspect the underlying evidenceThe denominator changes the answer
Pizza, no cheese, thin crust is denser; Pizza, no cheese, thick crust is higher in its source amount
Pizza, no cheese, thin crust reports 551 mg per 100 g and 827 mg in USDA source amount (150 g). Pizza, no cheese, thick crust reports a lower 514 mg per 100 g but a higher 1,275 mg in USDA source amount (248 g).
Record identity is part of the estimate
Distinguish “Pizza, no cheese, thick crust” from “Pizza, no cheese, thin crust”
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 Pizza, no cheese, thick crust versus Pizza, no cheese, thin crust, each path states why the destination belongs here, so you can distinguish a true evidentiary connection from a merely similar label.
Pizza, no cheese, thick crust and Pizza, no cheese, thin crust 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 A shared source-formulation input Beverages, water, tap, drinkingUSDA input 14411 appears in 2 of 2 context records; its summed listed input weight spans 118.5–211 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 shared source-formulation input Flour, wheat, all-purpose, enriched, bleachedUSDA input 20081 appears in 2 of 2 context records; its summed listed input weight spans 187.5–333 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 Inspect an exact record Pizza, no cheese, thick crustOpen the full nutrient table, household measures, formulation inputs, and FoodData Central 2708675 citation for this exact record—not a name-level average.
Follow this evidence path Check another exact record Pizza, no cheese, thin crustOpen the full nutrient table, household measures, formulation inputs, and FoodData Central 2708674 citation for this exact record—not a name-level average.
Follow this evidence path Put the observed spread in corpus context Potassium: density and serving contextIn this page’s records, potassium runs from 171 mg in Pizza, no cheese, thick crust to 195 mg in Pizza, no cheese, thin crust, all per 100 g.
Follow this evidence path Put the observed spread in corpus context Calcium: density and serving contextIn this page’s records, calcium runs from 23 mg in Pizza, no cheese, thick crust to 26 mg in Pizza, no cheese, thin crust, all per 100 g.
Follow this evidence path