Photo calorie counting: why we chose typing instead

A photo of your toast is a photo of toast. It doesn't show the butter, the oil the eggs were fried in, or whether that latte was made with oat or whole milk. When we started Ramen, photo logging looked like the obvious feature. We left it out on purpose. You already know what went into your food, so the quickest honest log is the one where you just say it. Here's why that works, and where it doesn't.

What photo calorie counting has to guess

A camera sees the top of a plate. To turn that picture into calories, an AI calorie counter has to fill in everything the lens can't see. That's a lot.

• Fat added in cooking. Oil in the pan, butter melted into rice, dressing soaked into a salad. None of it shows up clearly in a picture.
• Portion depth. A deep bowl and a shallow plate can look the same from above. So can a thin smear of peanut butter and a thick one.
• What's inside. A burrito, a sandwich, a pie or a plate of dumplings is a closed shape. The filling is a guess.
• Swaps that look identical. Oat milk and whole milk. Regular cola and diet. Full-fat yogurt and low-fat.
• Everything off the plate. The drink, the bites while cooking, the chips taken from someone else's plate.

The things a photo misses are often the most calorie-dense parts of the meal. A tablespoon of cooking oil is roughly 120 calories on its own. Miss it twice a day and the gap adds up quickly, even when the rest of the estimate is reasonable.

What a preliminary NIH study found

This isn't only a hunch. A preliminary NIH (NIDDK) study presented at NUTRITION 2026 tested photo logging in several apps on 102 meals that had been weighed in a metabolic kitchen. The apps underestimated calories and fat by about a third.

Two things are worth saying about that result. First, it is preliminary and hasn't been peer reviewed yet, so treat it as an early signal rather than the final word. Second, it fits the mechanism above. If fat is the hardest thing for a camera to see, you would expect calories and fat to be the numbers that come in low.

We're not saying any one app is bad. Photo logging as a method has a ceiling, because a picture can only carry what's visible.

Why a typed line carries more of the meal

When you type what you ate, you add the details a camera can't pick up. You were there. You saw the butter go in.

Compare a photo of breakfast with these lines:

• 2 eggs scrambled in butter
• toast, 2 slices, with peanut butter
• flat white, oat milk

Each line says how something was cooked, how much there was, and which version it was. That's the information an estimate depends on. A typed food log doesn't need you to weigh anything, either. "A big bowl", "2 slices" and "a handful" all give useful context, and you can add grams when you have them.

Typing is also quick. One line per food, written the way you'd write a note. In Ramen, most answers arrive in about 2 seconds, and things you've logged before come back instantly.

Where typing falls short

We'd rather be upfront about the limits than pretend there aren't any.

• You have to know what was in it. At a restaurant you can't see how much oil the kitchen used. Typing the dish and the place helps, but it's still an estimate.
• Vague lines get vaguer numbers. "Some pasta" gives the app less to work with than "a big bowl of pasta with pesto".
• You have to remember. A photo is a prompt you can come back to later. A typed log works best when you write it close to the meal.

Ramen handles uncertainty in the open. Every number is an estimate, and when it's less sure, you'll see a "~" next to it. Tap any number and you get a plain-language explanation of how it was worked out, so you can see what it assumed and add detail if something's off.

How Ramen treats a typed meal

The idea is simple: your words, with numbers beside them.

• Your words stay yours. Ramen never rewrites, reorders or corrects what you typed. "Leftover pad thai, cold, standing up" stays the way you wrote it.
• Every number explains itself. Tap a number to read why.
• A "~" when it's less sure. Home-cooked or vague lines often get one. That's the honest case.
• No guilt. No red numbers, no streaks, no "you blew it" messages.
• Private by design. A lookup sends only the food line, with no email attached. Your journal lives on your phone and works offline.

There's no camera button and no barcode scanner in Ramen. That's a choice, not a gap on a roadmap.

Tips for logging meals without a photo

Whatever app you use, these habits make a typed log more useful:

1. Mention the fat. "In butter", "fried", "with olive oil", "creamy sauce". It's the detail most likely to be missed.
2. Use household amounts. "A mug", "half a plate", "3 spoonfuls". You don't need a scale.
3. Name the version. Oat or whole milk, diet or regular, full-fat or light.
4. Log the drink. Coffees, juices, beers and smoothies are easy to forget.
5. Name the place for eating out. A chain dish by name gives the estimate a starting point.
6. Write it soon. A line typed right after lunch is easier than reconstructing the day at 10pm.

None of this needs to be perfect. A rough line written every day is more useful than a detailed log you give up on in a week.

Try the typed approach

If you've tried photo calorie counting and found yourself second-guessing the numbers, try writing tomorrow's lunch as a single line in your Notes app, butter and all. That's the whole idea behind Ramen, with the numbers filled in beside each line. Ramen is coming soon to iPhone. Join the waitlist and we'll send you one email when it's out.