Feast Get Feast
Menu

Portions and preparation · USDA nutrition

Tomatoes calories per cup: 36–120 across 4 of 5 named USDA examples

Across 4 of 5 named USDA examples, a cup contains 36–120 calories. Their listed weights span 180–240 g, so each calorie value is calculated from that example's own gram weight and published calories per 100 g. The remaining 1 specifically named example does not list that exact household measure.

Portion calculator

Estimate your portion

Choose a source measure or enter the weight you ate.

Preparation and portion

Named measures come from this exact source record.

Estimated for 120 g

52calories

Tomatoes, canned, cooked

Protein
1 g
Carbs
3.9 g
Fat
3.6 g

These values scale the selected reference food by weight. Ingredients, preparation, and portion size can change your meal’s estimate.

FoodData Central Survey Foods (FNDDS) · FDC 2709722 Full nutrition profile →

Compare all 5 food records, nutrition tables and USDA sources

The 5 exact records in this guide report 4–60 calories in the records' own listed source servings and 20–50 calories per 100 grams. Those are observations from named database records—not a universal range or an estimate of an unseen plate.

Match my meal

Start with the description closest to what you ate

For Tomatoes, begin by separating “Tomatoes, canned, cooked” from “Tomatoes, raw.” Choosing a card filters this source set; it does not infer the portion or fill in ingredients the chosen description does not name.

Showing all 5 linked records.

Equal-weight view

How tomatoes records compare at 100 grams

All 5 cited records are shown at the same 100-gram weight. The source servings may differ.

  1. Tomatoes, for use on a sandwich 20 kcal
    20 kcal
  2. Tomatoes, raw 20 kcal
    20 kcal
  3. Tomatoes, canned, reduced sodium, cooked 39 kcal
    39 kcal
  4. Tomatoes, canned, cooked 43 kcal
    43 kcal
  5. Tomatoes, fresh, cooked 50 kcal
    50 kcal

Shared basis: 100 g · kilocalories

What this page compares

Named source records, not one universal meal

This guide keeps 5 named USDA records in view: 5 direct matches. They span 2 source categories, including Tomatoes and Vegetables on a sandwich. The exact descriptions remain the unit of comparison; the familiar heading is only the doorway into the evidence.

Why these records appear together: The deterministic grouping rule “normalized first description segment” placed these 5 records together under the exact grouping key “tomatoes.” That rule determines membership before any nutrition result is read.

For Tomatoes, this page can compare 5 named records from FDC 2709722 through FDC 2709719. It cannot observe which preparation was eaten, recover unnamed additions, or supply the eaten grams.

Read the shared calculation, provenance, and uncertainty method →

Editor’s decision brief

The three facts to carry into the table

Carry the denominator, exact identity, and strongest observed contrast into every number below.

Portion

20–120 g before composition

The largest source amount is 6.0× the smallest. Read per-serving calorie differences with that mass gap in view.

Composition

30 kcal separates the fixed-weight endpoints

The lower endpoint is “for use on a sandwich”; the higher is “fresh.” This isolates density, not ingredient causation.

Discriminator

153 mg sodium gap per 100 g

Of protein, fiber, and sodium, the strongest normalized contrast is between “for use on a sandwich” (4 mg) and “fresh” (157 mg).

Observed source examples

Three landmarks inside this source set—not universal endpoints

The cards are ordered by calories in each record's listed serving. Serving weights differ, so use per-100-gram values to compare composition. These selected records do not define a calorie range for every tomatoes.

Important: “Lower” begins with Tomatoes, for use on a sandwich; “higher” ends with Tomatoes, fresh, cooked, using each record’s own source amount. Those labels order this selected set only—they are not endpoints for every tomatoes meal.

Full comparison

Compare every selected FNDDS record

For Tomatoes, serving columns preserve each record’s own listed amount, while calories per 100 g hold weight constant. A dash means the cited record does not supply that field; it does not mean the nutrient is absent.

On smaller screens, focus the table and scroll horizontally to read every column.

USDA records selected for the Tomatoes nutrition guide
Exact source record Match Source amount Calories kcal / 100 g Protein Fiber Sodium USDA
Tomatoes, canned, cooked Direct name match 120 gUSDA reference amount 52 kcal 43 1 g 2.2 g 156 mg FDC 2709722 ↗
Tomatoes, canned, reduced sodium, cooked Direct name match 120 gUSDA reference amount 47 kcal 39 0.9 g 2.2 g 22 mg FDC 2709724 ↗
Tomatoes, for use on a sandwich Direct name match 20 gUSDA reference amount 4 kcal 20 0.2 g 0.2 g 1 mg FDC 2710255 ↗
Tomatoes, fresh, cooked Direct name match 120 gUSDA reference amount 60 kcal 50 1.3 g 1.8 g 188 mg FDC 2709721 ↗
Tomatoes, raw Direct name match 90 gUSDA reference amount 18 kcal 20 0.7 g 1.1 g 4 mg FDC 2709719 ↗

Portion analysis

Serving total and calorie density answer different questions

The listed source amounts run from 20 to 120 grams—a 100-gram gap before composition enters the comparison. Their own source servings run from 4 calories for “for use on a sandwich” to 60 for “fresh.” At a fixed 100 grams, “for use on a sandwich” is 20 calories and “fresh” is 50—a fixed-weight separation of 30 calories. For Tomatoes, the serving view answers “how much is in the database portion?”; the 100-gram view answers “how concentrated is the matched record?” Neither reveals how many grams were actually eaten.

The scaling rule: multiply a per-100-gram value by eaten grams ÷ 100. The arithmetic is exact; the result is only as defensible as the record match and portion estimate.

Preparation analysis

The long description carries the evidence

The published descriptions distinguish forms such as “canned, cooked”, “canned, reduced sodium, cooked”, “for use on a sandwich”, “fresh, cooked”, and “raw”. The source formulations contain 8 distinct ingredient codes; examples that appear in only part of the set include oil or table fat, nfs, tomatoes, red, ripe, raw, year round average, salt, table, and tomato, roma. On this Tomatoes page, those rows make the records inspectable, but they are not a controlled experiment: they cannot tell us that one named input, by itself, caused a nutrient difference.

Database precision is not meal certainty. Retain the exact description beside the number so later corrections remain possible.

What changes the comparison

Four drivers worth checking before choosing a record

The family label “Tomatoes” cannot resolve the differences between Tomatoes, canned, cooked and Tomatoes, raw. The four checks below identify the record wording, source weight, and formulation evidence that can.

  1. 01

    Source weight before serving calories

    The source amounts span 20–120 grams. Compare per 100 grams before reading a serving-calorie gap as a composition gap.

  2. 02

    The words that split the family

    Representative record-level distinctions include “canned, cooked”, “canned, reduced sodium, cooked”, “for use on a sandwich”, “fresh, cooked”, and “raw”. Those phrases are evidence for choosing a record, not decorative subtitle text.

  3. 03

    Formulation evidence, with limits

    8 source-input codes appear across the selected records. Their presence and listed weights describe USDA formulations, not finished plated proportions.

  4. 04

    The unresolved plate

    Even “Tomatoes, canned, cooked” leaves the eaten grams and unnamed oils, sauces, toppings, substitutions, or leftovers unresolved. Preserve those Tomatoes unknowns for correction instead of converting them into false precision.

Record matching

Match identity first; scale quantity second

Read the source name as a sequence of decisions. First confirm that tomatoes is the right meal family. Then resolve the phrases that actually separate this set—“canned, cooked”, “canned, reduced sodium, cooked”, “fresh, cooked”, and “raw”—before comparing gram weight. If a package, menu, or known recipe provides a closer first-party description, prefer it and keep this USDA record as a transparent fallback.

A practical matching checklist

  1. Read the complete Tomatoes source description, including preparation and additions.
  2. Compare the listed source weight with the amount actually eaten.
  3. Prefer a current package or restaurant source when a specific branded item is known.
  4. Record toppings, sauces, cooking fat, sides, and substitutions that the selected description does not name.

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 5 exact records behind Tomatoes source-record guide. Links are chosen by record identity, controlled contrast, formulation input, nutrient spread, or serving context—not by loose keyword similarity.

Equal-weight result

Tomatoes, fresh, cooked is higher in sodium per 100 g

Tomatoes, fresh, cooked reports 157 mg versus 4 mg for Tomatoes, for use on a sandwich: a 153 mg difference when both are normalized to 100 g.

Inspect the underlying evidence

The denominator changes the answer

Tomatoes, for use on a sandwich is denser; Tomatoes, canned, reduced sodium, cooked is higher in its source amount

Tomatoes, for use on a sandwich reports 0.8 g per 100 g and 0.2 g in USDA source amount (20 g). Tomatoes, canned, reduced sodium, cooked reports a lower 0.8 g per 100 g but a higher 0.9 g in USDA source amount (120 g).

Choose the record before reading the number

Tomatoes, canned, cooked and Tomatoes, raw are not interchangeable

The page keeps both records at the same 100 g denominator and makes Preparation wording (No matching controlled term in the source name versus raw) the explicit record-description contrast. It does not show that the wording difference caused a nutrient difference. Pick the description that matches the food in front of you rather than averaging away the distinction.

Inspect the underlying evidence

Contextual knowledge graph

Follow the relationship that matches your question

For Tomatoes source-record guide, each path states why the destination belongs here, so you can distinguish a true evidentiary connection from a merely similar label.

Compare two records on this page Tomatoes, canned, cooked vs Tomatoes, raw

Both records appear in this page’s evidence set. 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 Compare two records on this page Tomatoes, fresh, cooked vs Tomatoes, raw

Both records appear in this page’s evidence set. 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 Oil or table fat, NFS

USDA input 81200100 appears in 3 of 5 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 Tomatoes, red, ripe, raw, year round average

USDA input 11529 appears in 2 of 5 context records; its summed listed input weight spans 60–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 Put the observed spread in corpus context Sodium: density and serving context

In this page’s records, sodium runs from 4 mg in Tomatoes, for use on a sandwich to 157 mg in Tomatoes, fresh, cooked, all per 100 g.

Follow this evidence path Put the observed spread in corpus context Calcium: density and serving context

In this page’s records, calcium runs from 10 mg in Tomatoes, for use on a sandwich to 32 mg in Tomatoes, canned, reduced sodium, cooked, all per 100 g.

Follow this evidence path 1 context record in this source topic Vegetables on a sandwich

Tomatoes, for use on a sandwich belongs 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