The calories you're not counting are the ones keeping the scale stuck
Most trackers only count what you tell them. The tablespoon of oil the vegetables cooked in, the glaze on the salmon, the dressing you eyeballed, that is roughly 200 uncounted calories a day, and it is usually why eating healthy is not moving the number. Forkd reads the whole plate and shows its reasoning.
Free to start · iPhone
Quick answer
Hidden calorie detection is Forkd's signature feature. When you log a meal by photo, voice, or text, it reasons about the ingredients most likely to be present but invisible, cooking oils, dressings, sauces, and glazes, and surfaces them as an editable AI Assumptions list. This closes the 200 to 400 calorie gap that sinks most food logs.
untracked calories a day from invisible oils and sauces.
of Americans exceed the added-sugar limit, much of it unlogged (CDC).
how far eyeball estimates miss. AI photo logging cuts that to 8 to 12%.
Reads the whole plate
A pan-fried dish gets a cooking-oil assumption, a salad gets a dressing assumption. Forkd surfaces the extras a photo alone cannot show.
Shows its reasoning
Nothing hidden, nothing sneaky. Each assumption comes with the why, as a list you can adjust in two taps.
You stay in control
Accept what is right, edit what is not, remove what does not apply. Every gram is yours to confirm.
How the detection works
When you log a meal, Forkd does not just name the visible food. It reasons about what a dish like this is usually made with, the cooking fat, the sauce base, the sugar in the marinade, and surfaces those as an AI Assumptions list you can adjust in two taps.
You are in control of every gram. Keep the dressing, halve it, or remove it, and the estimate updates instantly.
Why food logs under-count calories
Research consistently finds people underestimate intake by 20 to 40%. It is rarely deliberate. A meal that looks like 400 calories in the frame can easily be 600 once the cooking oil and dressing are counted. Photo-only apps inherit that blind spot because they log what is visible. Forkd is built to surface what is not.
Explore more of Forkd
Frequently asked questions
What are hidden calories?
Hidden calories are the calorie-dense extras a photo cannot show: cooking oil, butter, dressings, sauces, glazes, and drink add-ins. They are the most common reason a food log understates real intake.
How does an app detect ingredients I didn't enter?
Forkd recognises the dish type and reasons about what it is typically made with, then surfaces those as an editable AI Assumptions list. A pan-fried dish gets a cooking-oil assumption, a salad gets a dressing assumption.
Can I turn off or edit the AI's assumptions?
Yes. Every assumption is editable in two taps. Accept it, adjust the amount, or remove it entirely. Most people leave assumptions on, because they are the difference between a log that looks right and one that is right.
Why am I not losing weight even though I track?
The most common reason is hidden calories: oils, dressings, and sauces that never make it into a manual log. That gap is often 200 to 400 calories a day. Forkd flags those extras so your tracked intake matches what you actually ate.
Start tracking smarter with Forkd
Snap a photo, say it, or type it. Catch the hidden calories and see the full nutrition picture, free to start.
