Scan a nutrition label
Photograph the panel on a packet and it gets read into numbers you can use. Useful for anything branded — sauces, stock, plant milks, protein bars — where the packet is more accurate than a generic database entry.
Photograph the panel straight on, filling the frame. The image is resized in your browser before it is sent, and is never stored — only the numbers read from it are kept.
Why scan a label at all?
Generic database entries are averages. For anything branded — a jar of sauce, a carton of oat milk, a stock cube — the packet in your hand can differ from the average by a lot, and sodium is the worst offender: two brands of the same product can be threefold apart.
Where a recipe's nutrition hinges on one branded ingredient, reading its actual label is the single biggest accuracy improvement available.
What it can and cannot read
It transcribes what is printed — it does not calculate. If a panel does not list a nutrient, the result shows zero rather than a derived guess, and anything it could not read confidently is listed explicitly so you know what to check. A wrong number would be worse than an admitted gap.
Blurred, angled or partly-cropped panels are where it struggles. If a value looks wrong, it probably is — check it against the packet.