How to count calories in homemade meals

Here's how to actually do it, with a worked example.

Why a homemade dish is harder to log than a packaged one

A bag of chips tells you exactly what's in it: calories per serving, servings per bag, done. A pot of chili you made from six ingredients tells you nothing. Nobody stamped a label on it.

That's the whole problem with home cooking and calorie counting — the food is usually better for you (less added sugar, less sodium, portions you control) but harder to log, because you have to reconstruct the label yourself instead of reading one. A lot of people give up right here and either stop tracking home-cooked meals or just guess a round number. Neither is great. The fix isn't complicated, though — it's a few extra minutes of arithmetic the first time you cook something, and after that you can reuse the number every time you make it again.

The ingredient-by-ingredient method, step by step

1. List every ingredient and its raw weight or volume — as it went into the pan, before cooking. "300g chicken thigh, 200g rice (uncooked), 1 tbsp olive oil, 1 onion, 400g canned tomatoes."
2. Look up the calories for each one. USDA FoodData Central is the source most nutrition apps and labels actually pull from — it's the U.S. government's public database of calories and macros for raw and prepared foods, free to search, and public domain, so there's no paywall or app download required.
3. Add up the calories for the whole dish. Every ingredient's contribution, summed.
4. Divide by the number of servings you're actually portioning it into — not what a recipe card says ("serves 4") if you're really getting 3 bowls out of it. This step is where most people's math goes wrong, and it has nothing to do with the cooking.

Worked example: a simple chicken and rice stir-fry

Ingredient	Raw amount	Calories
Chicken thigh, boneless, skinless	400g	~660
White rice, uncooked	200g	~712
Olive oil	2 tbsp	~240
Mixed vegetables (broccoli, carrot, pepper)	300g	~110
Soy sauce	2 tbsp	~20
Total		~1,742

Split that into 3 bowls and you're at roughly 580 calories per serving. Split it into 4 and it's ~435. Same pan, same ingredients — the only thing that changed the number per serving was how many bowls you actually filled. That's why step 4 matters more than most people expect.

Weigh it raw, not cooked (or account for the shift if you can't)

Food databases are built around raw or as-purchased weight, so weigh your chicken before it hits the pan, not after. Cooking changes weight — mostly through moisture loss, sometimes fat loss too — and that shift isn't small. USDA's own cooking-yield research on meat and poultry found yields (cooked weight as a percentage of raw weight) commonly landing in the 65–85% range depending on the cut and cooking method — a boneless chicken breast pan-fried tends to lose noticeably more of its raw weight to moisture than, say, a braised cut that retains more liquid.

What that means in practice: 200g of raw chicken doesn't magically become 200g of cooked chicken with fewer calories per gram — it becomes maybe 150–160g of cooked chicken with roughly the same total calories now packed into less weight. If you only ever weigh food after it's cooked and look up "cooked chicken breast" instead of tracking from the raw weight you started with, it's an easy way to end up quietly off. Weighing raw sidesteps the whole issue.

The two things people always forget

• Added oil and butter. A tablespoon of olive oil is about 120 calories, and it's invisible once it's in the pan — nobody remembers exactly how many times they drizzled the bottle. This is the one I get wrong most often myself: I'll estimate a dish, feel good about the number, and then remember I refilled the pan with oil halfway through. If you're not sure, round up rather than down.
• Sauces and marinades that don't fully transfer. If you marinated chicken in a cup of sauce and most of it stayed in the bowl, you shouldn't count the whole cup — but if you deglazed the pan and reduced it into the dish, you probably should. There's no perfect answer here; a reasonable middle estimate (count roughly half of a discarded marinade, all of a reduced sauce) beats ignoring it entirely.

A faster way: snap a photo instead of doing the math

Doing the ingredient math above is worth it once, especially for a meal you'll cook again and again — write the per-serving number down and you never have to redo it. But for a one-off dinner you improvised, the arithmetic isn't always worth the time. That's the exact gap Bocco is built for: take a photo of the plate, and it estimates the calories and macros for the whole dish in a few seconds, cooked-in oil and all.

If it reads a portion wrong, you correct it in a sentence ("this had two tablespoons of oil, not one") and the numbers recalculate — you're not starting the ingredient list from scratch.

How Bocco helps

If cooking from scratch is most of how you eat — which, if you're reading this, it probably is — you shouldn't have to choose between "log everything by hand" and "stop tracking home-cooked meals altogether." Bocco reads a photo of your plate, corrects itself in plain words when you tell it something's off, and remembers a dish once you've logged it, so the second time you make that stir-fry you don't start from zero.