If food data sometimes looks incorrect, it’s usually because the app shows values for raw, uncooked, or dry foods, while the portion being logged is cooked. Cooking changes the water content and density of food, which affects calorie and macro counts. That’s why it’s important to check whether a food entry refers to a cooked, uncooked, or dry version. Here are some common examples:
Meat and fish 🥩🐟 (steak, chicken breast, pork, salmon) – calories per gram increase after cooking due to water loss.
Pasta, cereals (rice, oatmeal, couscous, quinoa, bulgur, buckwheat), legumes (beans, lentils, peas, chickpeas) 🍚🍝 – calories per gram decrease when cooked because they absorb water.
Vegetables 🥦🥕 – some lose water and nutrients when boiled or roasted, slightly changing their nutrition values.
For the most accurate tracking, it’s usually recommended to weigh foods in the same state as the food entry you’re logging:
Raw or uncooked – use the weight before cooking.
Dry – use the dry weight for foods such as rice, pasta, grains, and dried legumes.
Cooked – use the weight after cooking when the entry is specifically for a cooked food.
To find accurate data for cooked foods, try adding the cooking method (like “boiled rice” or “grilled chicken”) to your search. Also check the food name or serving information to make sure it clearly indicates whether the nutrition values are based on cooked, uncooked, or dry weight. This ensures the nutritional values match the actual state of the food you eat.