Calorie tracking for runners: a simple, honest guide

Short answer: as an endurance athlete, track calories to make sure you’re eating enough to fuel training and recover — not just to eat less. Aim to cover your training energy (endurance running burns very roughly 100 kcal per mile — about 62 kcal per km — depending on body weight and pace), get carbohydrate around your harder and longer sessions, and hit a steady protein target (about 1.2–2.0 g per kg of body weight per day) to recover. The easiest way to keep it up for months is to make logging effortless — with Forkmate you just tell the AI assistant you already use what you ate.

Why runners track differently from dieters

Most calorie apps are built on one assumption: you want to eat less. For an endurance athlete that’s often the wrong frame. Under-fuelling is the more common — and more damaging — mistake. Chronically eating less than you burn is the core of what sports scientists call Low Energy Availability (LEA), the driver behind Relative Energy Deficiency in Sport (RED-S), which is linked to compromised bone health, hormonal disruption, poor recovery, and worse performance (IOC consensus statement on RED-S, Br J Sports Med 2023).

So the point of tracking isn’t a smaller number. It’s the right number: enough total energy to train and recover, with the macros pointed at performance. Tracking is how you find out whether you’re actually eating what your training demands — because most people, when they check, are eating less than they think.

Step 1: know your baseline

Before you add training, you need your maintenance calories — your Total Daily Energy Expenditure (TDEE). A widely used starting estimate is the Mifflin-St Jeor equation for your resting metabolic rate, scaled by an activity factor (Mifflin et al., Am J Clin Nutr 1990). It’s an estimate, not gospel — bodies vary — but it’s a solid place to start.

If you’d rather not do the arithmetic, Forkmate’s 60-second quiz runs the same maths and gives you a starting daily calorie goal you can adjust as you learn how your body responds.

Step 2: fuel the work

On top of your baseline, you burn extra energy training. As a rough guide, running costs on the order of ~100 kcal per mile (about 62 kcal per km) for many runners, scaling with body weight and, to a lesser degree, pace and terrain. Cycling and other sports vary widely. Treat any single number as an estimate and adjust based on how you feel and how your weight trends over weeks.

Two practical rules of thumb from sports-nutrition guidance:

• Carbohydrate is the endurance fuel. Sports-nutrition bodies recommend scaling carbs to training load — roughly 5–7 g/kg/day for moderate training and 6–10 g/kg/day for endurance programmes of 1–3 hours a day (Academy of Nutrition and Dietetics / ACSM / DC joint position, Med Sci Sports Exerc 2016). Put simply: bigger training days need more carbs.
• Don’t drift into a deep deficit by accident. If you’re trying to lose weight, keep the deficit modest so you protect recovery and training quality. Aggressive cuts and heavy training rarely mix well.

Step 3: get enough protein

Protein isn’t just a strength-athlete concern. Endurance training damages muscle too, and protein drives repair. General guidance for athletes is about 1.2–2.0 g of protein per kg of body weight per day, spread across meals (Academy/ACSM/DC position, 2016). This is exactly why Forkmate shows protein, carbs, and fat on every meal — not just a calorie total. The macro split is what tells you whether you’re recovering, not just whether you’re “under.”

Step 4: make logging something you’ll actually keep doing

Here’s the honest truth about tracking: the accuracy of any single entry matters far less than whether you keep logging at all. Food databases, portion estimates, and even lab measurements all carry real margins of error. The athletes who benefit are the ones who log consistently through busy training weeks — not the ones who chase perfect numbers for a fortnight and quit.

That’s the whole idea behind Forkmate. Instead of stopping mid-day to open an app and search a database, you just tell the AI assistant you already use — Claude, Cursor, or any MCP client, right from your phone or laptop:

Post-run breakfast: 3 eggs, a bowl of oats with berries, and a banana.

It logs the meal and macros, shows you the numbers to confirm, and your day shows up in a clean web diary with a calorie ring and protein / carb / fat bars. Logging that survives 5am alarms, long weekend sessions, and travel is logging that actually changes anything.

A note on Strava and Garmin

If you’ve read other trackers’ guides, you’ve probably seen the advice to sync Strava or Garmin so your calorie targets adjust to your training. It’s good advice — and we want to be straight with you: direct Strava and Garmin sync is on the Forkmate roadmap, not a feature we ship today. For now, you fuel using your own sense of the day’s training plus the estimates above, and log your food conversationally. Automatic training-aware targets are what we’re building toward — see the Forkmate roadmap for where that sits.

The recap

1. Find your baseline with a TDEE estimate — or the 60-second quiz.
2. Fuel the work: more carbs on bigger days; don’t slide into an accidental deep deficit.
3. Hit ~1.2–2.0 g/kg of protein to recover, spread across the day.
4. Log consistently — good-enough numbers you actually record beat perfect numbers you abandon.

Forkmate is built for exactly this: nutrition that fits your training, logged by talking to the AI you already use. It’s a general-wellness tool, not medical advice — if you have a clinical condition, a history of disordered eating, or specific performance goals, work with a registered sports dietitian.