You own a food scale and log to the gram. The USDA lists two entries for the same boneless skinless chicken breast: 106 calories per 100 grams and 165. Both are accurate. Which one your app needs depends on whether the chicken hit the scale raw or cooked.
Should You Weigh Chicken Raw or Cooked?
Weighing cooked chicken and logging it against a raw database entry undercounts by 59 calories per 100 grams, a 55.7 percent calorie density increase caused by water loss during cooking. Matching the weighing method to the correct database entry eliminates the error entirely.
— USDA FoodData Central · FDC 2646170 (raw) + FDC 171477 (roasted)
The first entry measures raw chicken at 74.8 grams of water per 100 grams of breast meat. Cooking drives that water off. What remains is denser: the same protein and fat concentrated into less mass. The second entry measures what lands on the plate after that moisture left.
Nutrition databases worldwide calculate cooked food values from raw food data using cooking yield factors, converting between the two based on moisture and fat changes during preparation. The raw entry is the anchor. Every tracking app that pulls from these databases inherits the same architecture: the chicken breast listing that appears first is almost always the raw-weight value.
A person who weighs cooked chicken and logs it against the raw-weight entry undercounts by 59 calories per 100 grams. For a 200-gram cooked breast, the invisible gap is 118 calories, a 55.7 percent calorie density increase that never appears in the daily total. Same food. Same scale. Same careful logging. The error only undercounts, stacking across every meal.
118 kcal
The invisible undercount in a single 200-gram cooked chicken breast logged against a raw database entry
The fix is mechanical. Match the scale to the entry. Weigh raw, select the raw entry. Weigh cooked, select the cooked entry. Most major tracking apps now carry both versions. The problem lived in the mismatch between what the scale measured and what the database assumed.
The 59-calorie figure applies to oven-roasted boneless skinless breast specifically. Actual cooking yield varies with method, temperature, duration, and starting fat content. Grilling at high heat drives off more moisture than poaching. A fattier cut loses both water and fat, widening or narrowing the gap. The mismatch exists for every cooking method, but the exact size shifts.
This tracking error runs on a separate mechanism from the one most advice addresses. Research has found that people unconsciously omit a large share of what they actually eat from recall alone, even when their portion estimates are accurate. That is a memory problem, a gap between what happened and what the brain recorded. The raw-versus-cooked mismatch is not a memory problem. It is a database architecture problem that survives a digital scale, a barcode scanner, and perfect recall.
You just closed one gap, the unit mismatch between your scale and your app. The memory-based gap is still open, running on its own track. One error is about which entry the app selects. The other is about which meals the brain forgets. Both push the logged total below what the body actually received. The full scope of what calorie tracking actually misses goes further than either error alone.