So, I’ve been using Bevel to track my calories lately, and something’s just not clicking for me.

I logged my potato wedges, and it said they were 988 calories. That already sounds off, right? But what really bugs me is how it comes up with that number. They’re just chilling in a pan at home, not some fancy restaurant portion. So, how is it so sure about such a high number like it knows exactly what it’s dealing with?

I also manually added to capture  that I used about 15g of olive oil for seasoning and the rest of the ingredients. So, there’s no hidden oil or extra cooking fat that could explain such a massive jump. That’s why the estimate feels so random.

What really throws me is that the app says both “Capture Photo” and “Bevel AI” use artificial intelligence. So, how does the same picture give such different results depending on which mode you use? If both are AI, what’s actually changing that makes one way more accurate than the other?

I even start wondering if this is just a design thing, like the simpler capture flow being less useful, and the AI chat version being pushed as a “pro” feature, even if it’s not really better for tracking real-world food. Not saying that’s definitely true, but it’s hard not to wonder when the results are this inconsistent.

Either way, the fact that the same image can produce such different calorie estimates just doesn’t make sense to me.

 And it is not like we can downvote the capture picture calorie to let the team know how wrong it is. 

But seriously are you guys getting normal calculations with it  or is it me?

Do Not Use Capture Picture for Photo