One meal, actually read
What comes back, on a plate where only one thing had a label.
A weekday lunch: a shop-bought chicken and bacon sandwich, a handful of salted crisps, and an apple.
Energy
a range, not a number610to815kcal
A range, because two of the three items were estimated from a photograph. The sandwich is exact — its label was read. The crisps and the apple are not, and a total cannot be more certain than the least certain thing in it.
What was on the plate
- Chicken and bacon sandwich96% confidentBarcode scanned — the label was read directly.
- Salted crisps, small bag71% confidentRecognised from the photograph. Pack size estimated from the bag in shot.
- Apple88% confidentRecognised from the photograph. Size estimated against the plate.
Front of pack, with the basis of every figure
The one thing worth noticing: Salt. This lunch is 2.6g, which is 43% of a day’s 6g guideline before dinner. The sandwich carries most of it, and that is a swap rather than a sacrifice.
Why it does not just give you a number
A photo-calorie app would return a single confident number for this plate. Independent testing presented in 2026 found that leading apps underestimate meal energy by around 250 to 345 calories, with macronutrient error rates between 48% and 66%. The response here is not a better guess — it is a range, a stated basis for every figure, and an unmeasured nutrient left visibly unmeasured.
This example is stored, not generated. Nothing on this page calls a model, spends an allowance or costs anything, and it is the same for everybody who reads it — which also means it is not a cherry-picked run you could not reproduce.