Does the water in your food count toward hydration?

Most hydration tracking works like this: you drink a glass of water, you tap a glass-of-water button, a counter goes up. It is a tidy loop, and it is measuring the wrong thing — or rather, only part of the right thing.

Water arrives in the body two ways, and only one of them involves a glass.

About a quarter of your water comes from food

Dietary surveys put the food share of total water intake at roughly 20–30% for most adults, and higher for anyone whose diet leans toward fruit, vegetables, soup or yogurt. The European Food Safety Authority uses 20–30% in its reference values; American intake data lands in the same band.

That is not a rounding error. On a 3,000 ml day it is 600–900 ml — three glasses you already drank and never counted.

Here is what "water content" actually looks like, by weight:

• Cucumber, lettuce, celery — about 96%
• Watermelon, strawberries, cantaloupe — about 91%
• Broth-based soup — above 90%
• Yogurt — about 88%
• Apples, oranges, grapes — about 85%
• Eggs — about 75%
• Cooked rice and pasta — about 65–70%
• Chicken breast, cooked — about 65%

A lunch of soup, an apple and a yogurt is most of a liter before you touch your drink.

Why trackers skip it

Not out of carelessness. It is a database problem.

A conventional food tracker resolves what you ate to a row in a food database, and the number it needs from that row is calories. Water content is an optional field, populated inconsistently, and it changes with preparation in ways the database entry rarely captures — boiled rice and fried rice are the same "rice" to most databases and very different amounts of water. So the field goes unused, and hydration gets its own separate counter with its own separate button.

The result is an app that knows you ate a 400 g bowl of vegetable soup and still tells you that you have had no water today.

What AIM does instead

Water is not a side counter in AIM. It is a nutrient in the same registry as protein and iron, estimated from the same analysis of the same meal.

When AIM identifies what you ate, it estimates water in milliliters including the water in the food itself — the broth in the soup, the moisture in the chicken, the water absorbed by the rice as it cooked. That total lands on your day next to everything else, and you can put a goal on it like any other nutrient.

You can still log a glass of water by saying "large glass of water". It goes into the same number. There is no second system.

The honest version of hydration tracking counts what you ate, not just what you poured.

What this changes in practice

Two things, mostly.

The first is that your hydration number stops being pessimistic. People who eat a lot of fruit and vegetables are usually closer to their intake target than a drink-only tracker suggests, and the correction is often large enough to change what you do about it.

The second is that it becomes visible when your diet shifts. A week of salads and a week of sandwiches differ by hundreds of milliliters a day, and that difference shows up in the same chart as your protein — which is the point of putting water in the nutrient registry rather than in a widget of its own.

Track it the way you track everything else, or turn it off. Both are fine. What is not fine is a counter that is wrong by a quarter and does not say so.