What to Eat Before a Workout (and What to Eat After)

The short answer to what to eat before a workout: mostly carbohydrate, some protein, not much fat or fiber, and the amount scaled to how long you have before you start. Three hours out, eat a normal meal. An hour out, eat something smaller and easier to digest. Fifteen minutes out, eat something small or nothing at all. That is genuinely most of the advice, and the rest of this page is about the part nobody can answer for you.

Because the honest framing is this: your pre-workout meal is not deciding your physique. Your total intake across the week is doing that — the macro calculator guide covers how that total gets split, and the TDEE guide covers where it comes from. What the meal before training decides is whether the session feels good: whether you fade on the last set, or spend the warm-up regretting the burrito. That is a comfort-and-performance question, it varies enormously between people, and it is answerable — but only from your own record of what you ate and how you then trained.

That is the gap ChatRPE closes. It is an AI fitness coach built on a Universal Logbook, so the meal and the session that followed it land in the same memory instead of in two apps that never speak. After a couple of months you can stop reasoning from general rules and ask what your own best sessions had in common.

The short version

• Time before the session decides the size of the meal, more than anything else does.
• Carbohydrate is the useful fuel; it is the one that runs low during hard or long work.
• Fat and fiber slow digestion, which is fine at lunch and unhelpful thirty minutes before squats.
• Training fasted is a real option, especially for shorter or easier sessions — it is a preference, not a mistake.
• The post-workout meal is less urgent than it is made to sound. Hitting your daily protein and calories matters more than the clock.
• Everything above is a starting point. Which pre-workout food works for you is an n=1 question, and your training log can settle it.

How long before a workout should you eat?

This is the question underneath the question, so answer it first. Work backwards from when you actually start.

The pattern is that the closer you get to the session, the smaller and simpler the food becomes. Nothing about that is a rule you can break and be punished for — it is just digestion.

What to eat before a workout, by category

Deliberately no brand list here, because the useful version is a category you can fill from whatever is in your kitchen.

Easy carbohydrate does the actual work: oats, rice, potatoes, bread, fruit, honey, dried fruit, a sports drink if the session is long. Closer to the session, favor the fastest-digesting end of that list.

A moderate amount of protein sits alongside it — eggs, yogurt, chicken, a shake. It is there for the day's total more than for the session itself, so getting it in around training is convenient rather than critical. The protein calculator covers what your daily target should be.

Less fat and fiber than usual, specifically in the hour or two beforehand. Both slow gastric emptying, and a stomach that is still working when you start a heavy set is the single most common complaint people have about their pre-workout food. This is timing advice, not a reason to avoid either nutrient — the rest of the day is where they belong.

Fluid, unglamorously. Being a little short on water costs more sessions than any pre-workout food choice does.

Try this: "I train at 6 p.m. and usually eat lunch at noon. Suggest two pre-workout options from foods I already log, one for when I have two hours and one for when I have twenty minutes."

Is it bad to work out on an empty stomach?

For most people, no. Training fasted — the early-morning session before breakfast — is a perfectly reasonable way to train, and plenty of people prefer how they feel doing it. The evidence that eating first meaningfully changes body composition over a week is not strong; what changes is how the session goes.

Where it more often costs you something is in long or genuinely hard work: a heavy session with many working sets, a long ride or run, or anything over roughly an hour of real effort. There, having some carbohydrate in you before you start is more likely to be the difference between finishing the plan and cutting it short. And "more likely" is doing real work in that sentence — this is exactly the kind of claim that is true on average and wrong for specific people, which is why the next section exists.

If you get lightheaded, shaky, or unusually weak training fasted, that is information, and it is worth eating before training rather than pushing through it.

If you train fasted because you keep an eating window rather than because of when the session lands, the decision is a slightly different one — that is a question about your schedule for the whole day, not about this session, and the intermittent fasting guide covers it.

What to eat after a workout

The post-workout meal has a reputation it has not really earned. The old version of the advice — protein within thirty minutes or the session was wasted — has softened a great deal, and the current consensus is closer to hours than minutes for anyone eating a reasonable amount of protein across the day.

So the practical version is short:

• Eat a meal with protein in it within a few hours. It does not need to be a shake, and it does not need to be immediate.
• Include carbohydrate, particularly if you train again within a day or the session was long.
• If you trained fasted, close the gap sooner — not because a window is slamming shut, but because you have now gone a long time without eating.
• Judge it by the daily total. A post-workout meal that wrecks your daily calories to serve a timing rule is a bad trade.

If the shake is what makes hitting your protein target realistic, use it — convenience is a legitimate reason. The protein tracker guide covers keeping that daily number on track without weighing everything, and the muscle building guide covers what the protein is in service of.

From a general rule to your own answer

Test your pre-workout meal on your own sessions

Here is the workflow that turns this page into something specific to you, and it takes about ten seconds a session.

Log the meal and the session in the same place. Say or type what you ate — "oats and a coffee, training in an hour" — and ChatRPE structures it into a nutrition entry rather than making you find the right screen. Log the workout the same way. Both land in one history.

Record how the session actually went. The cheapest version is RPE — how hard the working sets felt — which you are probably already logging if you train seriously. If you want something more direct, track a custom metric like session energy on a 1–10 scale; the custom tracking guide covers defining one cleanly so the scale means the same thing in November as it did in August.

Then ask the question rather than answering it yourself. ChatRPE can keyword-search your own history — your entries, their notes, and their categories — so "which sessions did I log as fasted?" is a real query against your record and not a memory exercise. From there it can summarize each group: average RPE, top-set weight, how many sessions you cut short.

Try this: "Search my training notes for sessions I logged as fasted and compare their average RPE and top-set weight against the sessions where I ate beforehand."

Read the answer with two honest caveats attached. ChatRPE's numeric analysis works over a recent window of entries rather than your whole archive, so ask for a date range when you are looking back months. And when it reports a "trend," that is a plain first-half-versus-second-half comparison, not a statistical test — it tells you where to look, it does not settle the argument.

You can also see it instead of reading it. Ask for your session RPE and your pre-workout carbohydrate on one chart, each on its own axis with a moving average over the noise, and the relationship is either visible or it is not. If it is a comparison you want standing rather than re-requested, pin it to a saved fitness dashboard and it is waiting the next time you wonder.

The likely outcome, and this is worth saying plainly: for a lot of people the answer is "it barely matters, eat what is comfortable." That is a genuinely useful finding. It ends a question you would otherwise keep relitigating, and it hands the attention back to the levers that do move the needle — total intake, protein, and whether the training is progressing at all.

ChatRPE is not a dietitian or a physician. If you have diabetes, a GI condition, or any medical reason your food timing is not a matter of preference, set it with a clinician rather than a chatbot.