Raw vs. Cooked Vegetable Calories: Why a Cup Isn't a Cup

5 min read

Pull up a USDA entry for spinach and you'll find two numbers that, taken at face value, look like a contradiction. One cup of raw spinach is about 7 calories. One cup of cooked spinach is about 41 calories. That's almost a 6x jump for the same vegetable.

The vegetable did not somehow generate energy by being heated. What happened is more boring and more useful to understand: cooked spinach is more dense. A cup of it holds far more actual spinach because the water-filled cell walls have collapsed. You're comparing very different quantities of food and calling them both "a cup."

This is a small detail that quietly wrecks people's calorie counts on the volume-eating side of things, so it's worth getting precise about.


The Two Numbers, Side by Side

For most leafy greens and softer vegetables, here's the gap (numbers rounded from USDA FoodData Central):

VegetableRaw (1 cup)Cooked (1 cup)Raw (100g)Cooked (100g)
Spinach7 cal41 cal23 cal23 cal
Kale33 cal36 cal49 cal28 cal
Swiss chard7 cal35 cal19 cal20 cal
Mushrooms (sliced)15 cal44 cal22 cal28 cal
Broccoli (chopped)31 cal55 cal34 cal35 cal
Brussels sprouts38 cal56 cal43 cal36 cal
Cabbage (shredded)22 cal34 cal25 cal23 cal
Zucchini (sliced)19 cal27 cal17 cal15 cal
Onions64 cal92 cal40 cal44 cal

Two things jump out:

  1. Per-cup, cooked is almost always more calories than raw — sometimes dramatically more (spinach, chard, mushrooms).
  2. Per-100g, raw and cooked are essentially the same — small differences either direction depending on water loss vs. minor nutrient leaching into cooking water.

This is the whole insight in one table. Per-gram, calories barely change. Per-cup, they change a lot because the cup is now full of much more food. The detailed mechanism (water loss, no calorie change in the actual macros) is the same one covered in does cooking change the calorie count.


Why This Matters for Volume Eaters

If you're using vegetables to fill space — the explicit play in volume eating and the foundation of how non-starchy vegetables crush at satiety per calorie — the difference between raw and cooked matters in a specific way.

Raw vegetables have stretched, water-filled cells that take up real volume in your stomach. A bowl of salad is bulky. The stretch receptors that signal fullness fire on volume, and raw vegetables deliver volume per gram and per calorie better than almost anything else.

Cooked vegetables collapse. A pound of raw spinach reduces to about a cup and a half of cooked. The calories didn't change — they're still ~75 cal for the full pound — but you've gone from a bowl that takes ten minutes to chew to something that fits on a fork in two bites. The fullness signal is much weaker per calorie even though the calorie count is identical.

This is why "I'll have a salad" tends to work for hunger management and "I'll have a side of sautéed spinach" tends to be a more flexible side dish but a weaker fullness lever. Same vegetable. Different volume. Different fullness.

Practical implication: when you want a vegetable to fill you up, eat it raw or only lightly cooked (steamed, blanched). When you want it as flavor or as a nutrient hit without the bulk, cook it down — but don't expect it to function as a filler.


The Nutrient Side: It's Not Just Calories

Cooking changes how available the nutrients are. This is a separate question from calorie count, but it's the right context for understanding when raw and when cooked is the better play.

Cooking increases availability of some nutrients:

  • Lycopene in tomatoes. Raw tomato has lycopene locked inside cell walls. Cooking and a bit of fat (oil with the sauce) release it. Cooked tomato sauce has roughly 2–4x the bioavailable lycopene of raw tomato.
  • Beta-carotene in carrots, sweet potatoes, and squash. Same mechanism — heat breaks cell walls and the carotenoids become more absorbable. Roughly 6x more bioavailable from cooked carrots than raw.
  • Lutein in spinach and kale. Cooking with a bit of fat increases absorption considerably.

Cooking decreases availability of others:

  • Vitamin C in most vegetables. Heat-sensitive and water-soluble — boiling leaches it into the cooking water, and high heat degrades what's left. Raw bell peppers, broccoli, and citrus dominate cooked versions for vitamin C.
  • Sulforaphane in cruciferous vegetables. Broccoli, kale, Brussels sprouts, and cabbage produce this compound when their cells are damaged by chewing or chopping, mediated by an enzyme called myrosinase. Cooking destroys the enzyme. Lightly steamed or raw cruciferous vegetables have significantly more sulforaphane than fully cooked ones.
  • Folate. Heat-sensitive; long cooking can cut folate content by 50%+. Quick steaming preserves more.

There's no single right answer here. The functional rule is eat the same vegetables both ways across the week — some raw for vitamin C, sulforaphane, and volume; some cooked for lycopene, beta-carotene, and palatability. Both versions are essentially free at any reasonable portion when you're tracking calories.


How to Log This Without Going Insane

If you weigh your vegetables in grams, the rule is simple: the per-100g entry works for raw or cooked, within a few calories. A 100g serving of cooked broccoli and 100g of raw broccoli are nutritionally close enough that it doesn't matter — there's no oil added in the cooking (assuming you didn't oil-roast), and water in vs. water out doesn't change the macros.

If you log by volume — cups, tablespoons — you have to use the right entry. "1 cup of raw spinach" and "1 cup of cooked spinach" are different USDA entries because they're different amounts of food. Mixing them up is the source of essentially all bad vegetable logging.

Recommended workflow:

  1. Weigh in grams when you can
  2. If you must use cups, match the entry to the state you measured (raw cup → raw entry; cooked cup → cooked entry)
  3. Don't worry about whether your cooking method was identical to the database method — for non-oil-cooked vegetables, the per-100g calories are stable across grilling, steaming, roasting, boiling
  4. Add oil separately if you cooked with oil (see how much oil food absorbs when frying for absorption rates — many vegetables soak quite a bit)

The Bottom Line

A cup of cooked vegetables is not the same amount of food as a cup of raw. The calories per gram barely changed; the cup is just denser. For volume-eating purposes, raw fills you up cheaper. For some nutrients, cooked is more available; for others, raw is. Eat both. Log by grams when you can. And if you cooked it in oil, that's a separate, real calorie addition that has nothing to do with the vegetable.

Try the PE Diet Calculator

Enter the macros for any food and instantly see its Protein-to-Energy ratio, calorie breakdown, and macro percentages.

Use the Calculator