Count calories
from a photo.

You take the photo, Calsense does the rest. It looks at your picture, names the dish, estimates the serving in grams, and gives you its calories, protein, carbohydrates and fat — marked as an estimate with a confidence band, not dressed up as a fact. It takes a few seconds, and nothing is logged until you have looked at it.

Honestly, it depends on the photo. A clear shot where the food is visible gives you a solid estimate. Sauces, hidden oils and stacked food make it harder — which is exactly why Calsense labels every photo result with a confidence band and lets you correct it. Change the weight, retype a number, or add a note and ask again. You always get the final say.

Yes — this is the food Calsense is built around. Most calorie apps fall apart the moment your dinner isn’t something you can look up in a database. Calsense is built for dal chawal, curries, rotis, sabzi, biryani, and the family recipes nobody ever measured. If you eat it at home, Calsense wants to count it.

Yes. Photograph the plate and Calsense estimates the dish as served — the pasta with its sauce, the sides, the butter you did not see going in. Restaurant portions are exactly where guessing goes wrong, so the serving weight is the first thing to check, and the one tap that changes every other figure.

Yes, and you probably should. Drinks are where calories quietly slip past — the smoothie, the second coffee, the cocktail at dinner. Photograph it or describe it, and if you tell Calsense the size or what went in, the estimate gets better.

Then you fix it in a couple of taps. Rename the dish, change the weight and every figure rescales, or retype the calories or a macro yourself. If it has the wrong dish altogether, add a note — “the rice is brown, portion is small” — and Calsense analyses the photo again with your note as context. Nothing gets saved until you’re happy with it.

Both. Every entry carries protein, carbohydrates and fat against a target derived from your body and goal. Calsense keeps going — vitamins, minerals, fibre and sodium against reference intakes adjusted for your profile — and tells you which ones you are actually short on, over 7 or 30 days.

Yes, for everything except the estimates. Logging from the built-in food reference is a table and arithmetic you could check by hand, and your diary is on the phone, so it opens and works with no signal — anything you log offline is saved to your account as soon as there is a connection. A photo, or a description of a dish the reference does not know, goes to our server and on to Anthropic for the estimate, so that part needs one. What you send for an estimate is not kept: our server records that an analysis happened, not what was in it.

Yes. You sign in with Apple or Google. The account holds your diary — meals, water, supplements, measurements and your setup answers — so it comes back after a reinstall or on a new phone. It also holds your basic profile (date of birth, sex, height and weight) so our other apps can offer it back instead of asking again. Meal photos are the exception: they stay on the phone that took them, so a photo does not follow you to a new device.

Not for every meal, no. A clear photo is enough for a good estimate, and for most people that’s plenty. If you’re in a phase where precision really matters, type the weight you measured and Calsense rescales the estimate to it — but the whole point of Calsense is that the scale becomes optional.