Take a photo of your breakfast and you have a picture of toast. Take a text note and you have the butter, the oil in the pan and the oat milk in the coffee. That is the idea behind Ramen, a calorie tracker without photos. You write the line, and the numbers appear beside it.
What a photo cannot see
A camera sees surfaces. To turn a picture into calories, an app has to guess at everything the lens misses.
- Fat added in cooking. Oil in a pan, butter in rice, dressing in a salad.
- Portion depth. A deep bowl and a shallow plate can look alike from above.
- What is inside. Burritos, pies, sandwiches and dumplings are closed shapes.
- Look-alike swaps. Oat milk and whole milk, regular and diet, full-fat and light.
These are often the most calorie-dense parts of a meal, which is why they matter. A tablespoon of cooking oil is roughly 120 calories on its own, and it leaves almost no visible trace.
What a preliminary NIH study found
This is more than a hunch. A preliminary NIH (NIDDK) study presented at NUTRITION 2026 found photo logging in several apps underestimated calories and fat by about a third across 102 weighed meals; not yet peer reviewed. You can read the release on EurekAlert.
Please hold it lightly. It is early, and it is a signal, not a final answer. It does fit the mechanism, though: if fat is the hardest thing for a camera to see, you would expect calories and fat to come out low. We are describing a method here and not criticising any single app.
How a text calorie counter works
In Ramen, you type one line per food and the app reads it.
2 eggs fried in butter, toast ~380
oat flat white ~140
chicken katsu curry, big plate ~850
pint of lager 210
These numbers are illustrative, not measured outputs. The words do the work a camera cannot. "Fried in butter" is information. "Big plate" is information. "Oat" is information.
Most real answers arrive in about 2 seconds. Tap a number to read a plain-language explanation of how it was worked out, and watch for the "~" when Ramen is less sure.
No weighing required
Text does not mean precision. You do not need a scale.
"A bowl", "2 slices" and "a big handful" work fine, and grams are welcome when you have them. If you know the calories already, type them: "latte 190" uses your figure. For more phrasing ideas, see how to log food like notes.
Where text has limits
Typing relies on you knowing what you ate. At a restaurant you cannot see how much oil the kitchen used. Vague lines give vaguer numbers, and "some pasta" tells the app less than "big bowl of pesto pasta".
That is why every number carries a reason, and why the "~" exists. Typed estimates are still estimates, and we say so. Our full thinking on the trade-off is in why we do not use photos, and how reliable calorie estimates are covers how to read the results.
Who a no-photo tracker suits
You might prefer it if you:
- cook at home and know what went into the pan
- found yourself second-guessing photo results
- like a diary that reads like your own writing
- would rather type than correct a guess
If you also dislike scanning packets, our page on a calorie counter without barcode scanning covers the other half.
Your words, privately
Ramen never rewrites, reorders or corrects what you wrote. For a lookup, only the single food line is sent, with no email attached, and no photos ever leave your phone because there are none. The journal works offline, and you can export everything or delete your account.
There are no red numbers or streaks, either. Go over your target and it is just a number.
Join the waitlist
Ramen is coming soon to iPhone. It is $9.99 a month, or $39.99 for the first year and then $59.99 a year, and waitlisters get the $39.99 first year. No card is needed now. If a camera has been guessing at your butter, join the waitlist and we will send one email when it is out.