Excaloricate
Eating out is where most calorie tracking quietly falls apart. There's no label, no serving size, and no way to weigh anything. You can't see the oil the kitchen cooked in, and the portion arrives looking like a decision someone else already made for you.
The instinct is to either give up tracking for the night or to log a guilty round number like "1000 kcal" and move on. Neither helps. Here's a saner way to estimate a restaurant meal closely enough that your week still adds up.
Start with the cooking fat you can't see
The single biggest gap between a home-cooked meal and the same dish at a restaurant is fat. Restaurants cook with butter, oil and cream far more generously than you do, because that's what makes food taste like restaurant food.
A plate of vegetables you'd log at 150 kcal at home can easily be 350 kcal when it arrives glistening. A "healthy" grilled chicken salad can hide 200+ kcal of dressing and oil before you've touched the bread.
When in doubt, add a hidden 100–200 kcal of fat to any savory restaurant dish. You won't always be right, but you'll rarely be badly wrong.
Estimate the protein by the deck of cards
You can't weigh the steak, but you can eyeball it. Use your hand and a couple of reference objects:
- A palm-sized piece of meat or fish is roughly 100–150 g — call it 200–300 kcal for chicken or white fish, more for fatty cuts.
- A piece the size of a full deck of cards is one "restaurant portion" of protein. Two decks stacked is the slab you get at a steakhouse.
- A cupped handful of rice, pasta or fries is roughly 200 kcal. Restaurant sides are usually two to three of those.
You don't need precision here. You need to not log a 12-ounce ribeye as if it were a chicken breast.
Find the calorie anchor on the plate
Most restaurant meals have one item doing most of the calorie damage. Find it before you eat and the rest is rounding:
- Anything fried — the batter and oil usually double the calories of whatever's inside.
- Cream or cheese sauces — a pasta in cream sauce is often 800–1100 kcal for the bowl.
- The bread basket and the drinks — these are the calories people forget entirely. A couple of slices with butter plus two drinks can be 500 kcal before the meal arrives.
Log the anchor honestly, estimate the rest loosely, and you'll land close.
Describe it, don't compute it
This is exactly the situation the app is built for. You don't have a label to read or a database entry to find — you have a memory of a plate. So describe it the way you'd describe it to a friend: "grilled salmon, big pile of mashed potato, side of green beans in butter, two glasses of wine." Let the estimate come back and adjust your day around it.
The describe-it approach beats the database for restaurant food precisely because there is no correct database entry for this kitchen's version of the dish. A reasonable estimate logged tonight is worth more than a perfect number you never enter.
The one rule that matters
A slightly-wrong restaurant log that you actually record beats a perfect one you skip. The people who keep their weight steady while eating out aren't measuring — they're estimating fast, logging anyway, and letting the average across the week carry them. Over a month, a meal you over- or under-shoot by 200 kcal disappears into the noise. The meals you never logged at all are the ones that move the scale.