Yes, for macro tracking, weigh foods in one state—prefer raw for accuracy—and match your logging entry to raw or cooked.
Chasing consistent macros starts with consistent measurements. Heat pulls water out of meat, and it puts water into grains and pasta, which changes weight. If you switch between raw and cooked weights from meal to meal, your numbers drift. Pick one method, stick to it, and use food database entries that match that method.
Weighing Food For Macros: Raw Vs. Cooked Basics
Most home cooks find raw weighing simpler for proteins and grains. Raw weight isn’t influenced by doneness or pan time, and packaged nutrition labels list servings in the uncooked state for many foods. Cooked weighing still works—many meal preppers use it—so long as your app entry says “cooked,” “boiled,” “grilled,” or similar. The rule isn’t raw only; the rule is be consistent and match your entry.
Why Weight Shifts During Cooking
Meat loses water and some fat during heating. Starches absorb water. Vegetables steam off moisture. The macro content per gram changes because the water fraction shifts, not because protein or carbs disappear into thin air. That’s why 100 grams of raw chicken isn’t equal to 100 grams of cooked chicken on your tracker.
Quick Conversions You Can Use
These typical yields help when you only have a cooked weight or a raw weight but need the other. They’re averages; pan temperature, cut, and time on heat all move the needle. When accuracy matters, weigh in your chosen state rather than converting.
| Food Type | Raw → Cooked (Typical) | Notes |
|---|---|---|
| Chicken Breast | 100 g raw → ~75 g cooked | Water loss varies with heat; trim visible fat for repeatable results. |
| Ground Beef (90% lean) | 100 g raw → ~70–75 g cooked | Fat drips plus water loss reduce weight; drain method changes yield. |
| Salmon Fillet | 100 g raw → ~80–85 g cooked | Higher fat fish retains more moisture than very lean fish. |
| White Rice | 100 g dry → ~300 g cooked | Absorbs water; ratio depends on method and variety. |
| Brown Rice | 100 g dry → ~250–300 g cooked | Slightly lower expansion than white in many pots. |
| Pasta | 100 g dry → ~200–250 g cooked | Shapes vary; al dente cooks weigh a bit less. |
| Oats (rolled) | 40 g dry → ~120 g cooked | Cook time and milk vs. water shift the final mass. |
| Potato | 200 g raw → ~170–180 g baked | Water steams off in the oven; foil changes the loss. |
| Leafy Greens | 100 g raw → ~30–40 g sautéed | Large water loss; oil adds mass if used. |
Pick A Method And Stick With It
Choose the approach that fits your kitchen flow, then keep it steady for the whole week or training block.
If You Prefer Raw Weighing
- Batch-trim proteins, portion raw weights, and label bags or containers.
- Log entries that say “raw,” “uncooked,” or list the meat as “as purchased.”
- Cook as usual; you’ve already banked the macros by weight.
If You Prefer Cooked Weighing
- Cook a full pan, then portion after resting to let steam escape.
- Use entries labeled “grilled,” “baked,” “boiled,” or “cooked.” Match the method when possible.
- Keep doneness and drain method the same across batches to keep yields steady.
Label Rules And Database Entries
Food databases contain both raw and cooked records. Government datasets separate them clearly. When you open an entry, read the description and serving basis. If it says “raw,” use raw weight. If it says “cooked, roasted,” that’s for a cooked weight on your scale. To learn how these datasets are built and how yields are handled, see the USDA’s FoodData Central overview and the beef cooking yields report; both explain weight change and retention methods used in data prep.
What To Do When An App Entry Looks Off
Sometimes the calories per 100 g in your app don’t match common sense. Two quick checks fix most cases: first, confirm raw vs. cooked in the entry title; second, confirm the cooking method. If it still seems odd, switch to a record from a government dataset inside the app, or enter a custom food with your own label data.
Protein, Carbs, And Fat: What Actually Changes
Protein grams in the pan don’t vanish; the weight per gram changes because water leaves. That’s why cooked meat shows more protein per 100 g than its raw counterpart. Starches go the other way: water soaks in, so cooked rice shows fewer carbs per 100 g than dry rice. Fat can drip from meat or be added through oil or sauce, changing totals if you log the pan pick-ups. Oil that stays in the skillet doesn’t count unless it ends up on your plate.
Simple Methods That Keep Numbers Tight
- Use the same pan, heat level, and time for your weekly meal prep.
- Strain or blot meats the same way each time if you want repeatable fat numbers.
- Cook grains with a measured water ratio so expansion stays steady.
- Weigh sauces and oils in, or weigh the bottle before and after cooking to capture only what you consumed.
When Conversions Make Sense
Maybe your family serves cooked portions at the table, or a restaurant meal lands in a container. In those cases, use the table up top to back-convert a cooked weight to a raw estimate, or vice versa. Keep a small card in your kitchen with your usual foods and your own measured yields; after two or three batches, you’ll have reliable house numbers that beat any generic factor.
Worked Mini-Examples
Grilled chicken: you portion 600 g raw breast for the week. Your grill yields about 75% cooked mass, so you expect ~450 g cooked. Log the 600 g raw on day one, or log each meal as cooked using an entry labeled “cooked, grilled.” Both routes arrive at the same weekly protein, so long as the entry matches the state you weighed.
Pasta night: the box says 56 g dry per serving. You cook 224 g dry for four servings. After boiling, the pot lands at ~500 g. Each plate gets 125 g cooked, and you log the cooked entry that matches “boiled.”
Second Table: Logging Shortcuts You’ll Use Weekly
| Food | Pick This In Your App | Reason |
|---|---|---|
| Chicken Thigh, Pan-seared | “Chicken, thigh, cooked, pan-broiled” | Matches cooked state and method; keeps fat and moisture loss aligned. |
| Ground Turkey, Batch-prepped | “Turkey, ground, cooked” | Drained mass differs from raw; cooked entry avoids guessing. |
| Sirloin, Oven-roasted | “Beef, top sirloin, roasted, cooked” | Roast yields differ from grilled; method tag matters. |
| White Rice From Rice Cooker | “Rice, white, cooked” | Water uptake triples mass; cooked entry lines up with serving spoon weights. |
| Dry Oats For Overnight Oats | “Oats, rolled, dry” | You portion jars before soaking; log dry weight. |
| Penne, Al Dente | “Pasta, cooked” | Shape and doneness change weight; cooked listing accounts for that spread. |
| Baked Potato, No Oil | “Potato, baked, flesh and skin, without fat” | Baked mass is lower than raw; oil-free entry fits. |
Common Pitfalls And Simple Fixes
Mixing Raw And Cooked In One Day
This is the fastest way to scramble your totals. Pick a lane for the week. If a meal forces the other lane, add a note in your tracker and use a conversion once, not daily.
Trusting Crowd-Sourced Entries Blindly
Many app records come from user uploads. Great for coverage, not always great for accuracy. Prefer entries from government datasets or brand-verified labels. When in doubt, switch to a verified record.
Ignoring Sauces, Oils, And Drippings
Pan sauces can swing totals. Either weigh oil in and out, or pick a cooked entry that includes typical fat retention for that method. If you pour off drippings, don’t log them.
Templates You Can Copy
Raw-First Prep Day
- Weigh raw proteins and grains for the whole week.
- Label containers with weight and macros from raw entries.
- Cook, cool, and store. Eat by portions, not by cooked weight.
Cooked-First Prep Day
- Cook a batch to your usual doneness.
- Weigh cooked food after resting.
- Log using cooked entries that match the method.
How Nutrition Labels Tie In
Packaged dry goods such as rice and pasta list serving sizes in the uncooked state. Many raw meats list a serving based on raw weight too. Some ready-to-eat items list cooked values instead. Read the label once, then mirror that basis in your app. When the label and your weighing habit disagree, favor your habit and pick a matching database record so daily totals stay steady.
Eating Out Or Ordering In
Restaurant data often lists cooked weights, but portion sizes swing wildly. Treat those entries as estimates. If you care about tighter numbers, build the meal with components—cooked steak entry, cooked rice entry, measured sauce—rather than a single generic “beef bowl” line. The closer the entry names match the foods on your plate, the closer your macros land to reality.
Sources Worth Keeping Handy
You can browse government food records directly. Two helpful stops: the FoodData Central help page and the USDA report on beef cooking yields. Both explain how raw and cooked entries are defined and why yields differ by method.
Speed Tips For Busy Weeks
- Snap a photo of your scale readouts during prep so you can log later without guessing.
- Save favorite entries in your app with stars or folders to avoid lookups.
Bottom Line For Consistent Macros
Pick raw or cooked weighing, match every entry to that choice, and keep your methods steady. If you must switch, use typical yields or your own measured factors. Consistency beats perfection, and small, steady habits make macro tracking painless.