How to track soup, stew, and chili calories (the densest tracking problem)

Soups, stews, and chili are the hardest food category to track accurately. Solid foods you can weigh. Dry foods you can measure. But a 4-quart pot of beef stew with potatoes, carrots, beef, broth, oil, and seasonings? That's a tracking nightmare unless you have a system.

Here it is.

The recipe-then-volume method

Step 1: Track the entire pot's ingredients once. Add up total calories.

Step 2: Measure the total finished volume in cups.

Step 3: Calories per cup = total cal ÷ total cups.

Now every time you ladle a bowl, count cups.

Example: a chili pot with 2,400 total cal and 12 cups of volume = 200 cal per cup. A two-cup bowl is 400 cal. Done.

Why the "weight per cup" of stew matters

Soup-like foods have wildly variable calorie density depending on liquid-to-solid ratio.

• Clear chicken broth: 15 cal/cup
• Chicken noodle soup: 75 cal/cup
• Lentil soup: 230 cal/cup
• Beef stew: 270 cal/cup
• Chili (typical): 250–350 cal/cup
• New England clam chowder: 180 cal/cup
• Mac and cheese (yes, it's a stew): 600 cal/cup

A "bowl" can be 1.5 cups (smaller bowl) to 3 cups (mug-style). The number that matters is cups, not bowls.

The lazy man's tracking shortcut: recipe + serving size

If you don't want to math per-cup:

• Build the recipe in your tracker
• Decide it serves 6 (or however many you'll eat over)
• Weigh the finished pot
• Each "serving" is total weight ÷ 6
• Log one serving per bowl

This works when you eat consistent portions. It breaks when you have a big bowl one night and a small bowl another.

The actual measurement workflow

Best for chili, stew, soups:

1. Cook the dish
2. Weigh the empty pot, then weigh the pot full
3. Subtract → grams of finished dish
4. Convert to cups (most stews are roughly 240 g/cup)
5. Calories per gram or per cup → ladle and log

Time investment: 90 seconds, once per pot. Tracking time per bowl after that: 5 seconds.

What about restaurant soups?

Restaurant soups are harder because:

• You don't know the recipe
• The bowl size is unfamiliar
• Cream-based soups can be 4× the calorie density of broth-based ones

Strategy:

• Photo log it
• Default to 250 cal/cup for cream soups, 100 cal/cup for broth-based
• Estimate cups by eye (most restaurant soup bowls are 1.5–2 cups)
• Adjust upward by 10% (restaurants tend to use more oil/butter than home)

The "soup as a tool" angle

If you're cutting and you're hungry: vegetable-heavy broth-based soups (minestrone, chicken vegetable, gazpacho) are some of the highest-satiety, lowest-calorie foods you can eat. A 2-cup bowl can be 200 cal and keep you full for 3 hours.

Cream-based soups do the opposite — high satiety per cup but very high calorie density. Watch the portion.

Soup mistakes that wreck the math

• Logging "1 cup" when you ate 2 (eyeball error)
• Forgetting the bread you dipped (200+ cal of bread)
• Forgetting the cheese topper or sour cream dollop (100+ cal each)
• Not counting the oil drizzle on top
• Counting consommé and lobster bisque as the same kind of "soup"

The CalorieScan AI workflow for soups

In the app:

• Photo log restaurant soups (let the AI estimate cream vs. broth)
• Build recipes for soups you cook regularly
• For the recipes, use the "per cup" feature so portion size is flexible
• Add a sub-entry for any bread, cheese, or topper

The honest summary

Soup is harder than it looks. Cup-counting beats bowl-counting. Recipe-once-eat-many beats logging from scratch.

If you eat soup regularly: build a library of 5 saved recipes with per-cup tracking. You'll save hours over a year.

A bowl of soup is an honest meal. The label "bowl" is a vague unit of measurement.