How accurate is the AI calorie counter,in numbers?
Within 8% of a registered dietitian on average. Median error under 5%. Inside the 5 to 15% range peer-reviewed studies report. Here's the per-meal breakdown and how this compares to manual logging.
AI photo vs manual database logging.
Manual underestimation figures from Stubbs et al. (2014) and the Schoeller (1990) family of food-diary validation studies. AI photo error from internal RD-graded benchmark + the 5 to 15% peer-reviewed consensus range.
Error isn't uniform.
| Meal type | Typical error |
|---|---|
| Restaurant chains (single plate) | 3 to 6% |
| Home cooking, distinct ingredients | 4 to 8% |
| Packaged foods with visible labels | under 2% |
| Snacks with countable items | 5 to 10% |
| Mixed soups and stews | 10 to 20% |
| Buffet plates, many small items | 8 to 15% |
| High-prep-variance fried foods | 10 to 20% |
The interface shows a confidence indicator on each estimate, and the harder categories are flagged. One-tap adjust lets you correct.
Portion estimation
is the wildcard.
Detection is usually right. Database lookup is deterministic arithmetic. Portion estimation from a single photo is inherently lossy. The 8% benchmark target reflects this: the lower the prep variance and the cleaner the photo, the closer to ground truth.
Accuracy improves with usage. One-tap adjust feedback teaches the system what your portion-sizing eye looks like, and the model itself improves between releases. We don't ship if average error regresses on the RD benchmark panel.
Follow-ups, answered.
Keep reading.
Test the numbers yourself.
Snap a meal you know the calories of and compare to the AI estimate.