How to Train for Your First Marathon

Let's start with the thing nobody says up front: training for a marathon is mostly a time management problem.

Yes, you need to build fitness. Yes, you need to run more miles than you're running now. But the thing that actually breaks first-time marathoners — the thing that causes DNS (did not start), DNF (did not finish), or just a miserable 26.2 miles — is not having enough time. Time to train, time to recover, time to sleep, time to eat enough food. If you're currently working 50-hour weeks, commuting two hours a day, and raising kids, you need to know that before you sign up for an April race in January.

This isn't meant to discourage you. It's meant to set you up to actually finish.

How Long Do You Actually Need?

Sixteen to twenty weeks is the minimum for most people. If you've never run a half marathon, go with 20. If you've already run a half and you're currently running 20-25 miles per week, 16 weeks is workable.

Here's why rushing it destroys you: marathon training requires your body to adapt to stress in a very specific way. Your cardiovascular system adapts fast — within a few weeks, your heart and lungs will feel like they're handling the training fine. But your connective tissue — tendons, ligaments, the cartilage in your knees — adapts slowly. Stress fractures, IT band syndrome, and plantar fasciitis don't come from one hard run. They come from accumulated load on tissue that wasn't ready for it. Compressing 20 weeks of training into 12 is how you end up in a boot three weeks before your race.

Ten months out from your target race is not too early to start building a base. Twelve weeks out is too late.

The Three Workouts That Actually Matter

Training plans can look complicated, but almost everything they contain falls into one of three buckets. Get these three right and ignore the noise.

1. The Long Run

This is the centerpiece of the whole training cycle. Every week, you do one run that's longer than everything else — eventually peaking somewhere between 18 and 22 miles depending on your plan.

Pace: Slow. Slower than you think. A common rule is 60-90 seconds per mile slower than your goal marathon pace. If you're targeting a 4:30 marathon (about 10:18/mile), your long runs should be around 11:45-12:15/mile. This is supposed to feel almost embarrassingly easy. Most beginners run their long runs too fast, end up too depleted to recover properly, and wonder why they feel terrible all week.

Fuel: For runs under 75 minutes, water is fine. Once you're consistently hitting 90+ minutes, you need to practice taking in carbohydrates. Start experimenting with gels, chews, or real food early in training — don't wait for race week to figure out what your stomach can handle. A rough target is 30-60g of carbohydrates per hour after the first hour. Take a gel every 35-45 minutes and chase it with water, not a sports drink (double-dosing electrolytes causes GI issues).

When to bail: If it's over 80°F and humid, shorten the run or move it to a treadmill. Heat stress on a long run is not the same as heat stress on a 5-miler. Finish the miles another way.

2. Easy Runs

These are most of your miles — probably 75-80% of your total weekly running. They should genuinely be easy. You should be able to hold a full conversation without gasping.

The problem is that most runners don't actually run these easy. They run them at what feels like a "comfortable" pace, which ends up being moderate effort — not easy enough to recover, not hard enough to create real fitness gains. You end up perpetually tired.

An easy run should be in zone 2: about 60-70% of your max heart rate. If you have a watch with heart rate, use it. If you don't, the talk test is decent: you should be able to say a full sentence without pausing to breathe. The first few weeks of actually running this easy will feel almost insulting. You'll look at your pace and feel embarrassed. Run there anyway. The people who are great at easy runs are the people who peak on race day instead of two weeks before it.

3. One Quality Session Per Week

One day per week, you run hard. This is enough. More than one hard session per week is usually counterproductive for beginners — your body doesn't have enough recovery capacity yet.

What "quality" means changes through the training cycle. Early on, it might be strides (8-10 second bursts) at the end of an easy run. Mid-training, it might be a tempo run: 20-40 minutes at a pace you could hold for about an hour, comfortably hard. Late in training, some marathon-specific work like 3-4 miles at goal marathon pace helps your legs remember what that effort feels like.

What it never is: all-out sprinting, track intervals 4 days a week, or anything that leaves you so sore you can't run the next day.

Weekly Mileage: Where to Start and How to Build

If you're starting this process having run less than 15 miles per week, you're not ready to jump into a standard 16-week plan. Spend 6-8 weeks building your base first — just consistent easy running, 4-5 days a week, before you add any structure.

The 10% rule is the most cited rule in running and one of the most ignored. It says: don't increase your weekly mileage by more than 10% from one week to the next. So if you ran 30 miles this week, next week's max is 33. It feels conservative. It's not — it's the pace at which connective tissue can adapt. You can build aerobic fitness faster than that, but your tendons and bones cannot.

Also follow this pattern: three weeks of building, one week of pulling back. A "down week" at about 60-70% of your recent peak mileage lets your body consolidate the gains. Most people hate down weeks and skip them. Don't. The fitness you built in the last three weeks gets locked in during the down week.

What a Real Training Week Looks Like

Here's a sample mid-training week at about 40 miles:

Day	Workout	Notes
Monday	Rest or easy 30-min walk	Recovery from Sunday's long run
Tuesday	7 miles easy	True zone 2, no heroics
Wednesday	8 miles with 4 miles at tempo	Warm up 2 miles, tempo 4 miles, cool down 2 miles
Thursday	5 miles easy	Easy, seriously
Friday	Rest or 30-min cross-train	Bike, swim, strength — low impact
Saturday	6 miles easy	Shake out before Sunday
Sunday	14 miles easy	Long run — fuel every 40 min from mile 6 onward

That's 40 miles, but more importantly notice what it isn't: six hard days, no recovery, skipped long runs. The plan only works when the easy days stay easy.

The Long Run in More Detail

The long run deserves its own section because it's where most first-timers get into trouble.

Start slower than you think you need to. The last 4 miles of a 16-miler should feel about the same as the first 4. If miles 13-16 feel like survival, you went too fast — and on race day you'll have 10 more miles after that.

Walk breaks are not cheating. Especially in your early long runs, walking for 60 seconds every mile keeps your heart rate in check and saves your legs. Many marathoners PR using run-walk strategies. Jeff Galloway has built an entire career around this. Don't let ego talk you out of a tool that works.

Practice your race-day nutrition. Every long run over 10 miles is a dress rehearsal. Use the gels/chews/real food you'll use on race day. Try different brands — some people tolerate maltodextrin-based gels fine, others get GI distress and do better with real food like dates or banana pieces. Figure this out in training, not at mile 18 of the race.

Run the terrain. If your race has hills, run hills. If it's flat, train flat. Specificity matters more than people realize.

When Things Go Wrong

They will go wrong. Here's what to actually do.

You miss a week. Life happens. Missing one week doesn't derail a training cycle. Pick up where you left off, maybe at 80% of the mileage you were at before the break. Don't try to "make up" the missed miles — that's how you get hurt.

You miss two or three weeks. More significant, but still recoverable. Go back in your plan to where you were two to three weeks before the gap. Yes, you'll repeat some weeks you already ran. That's fine.

Minor injury. The hardest skill in marathon training is knowing the difference between soreness (normal) and injury (something is actually wrong). Soreness is general, diffuse, and goes away after the first mile of a run. Injury is localized, gets worse as you run, and doesn't improve with warmup. For the latter, rest it, ice it, and if it's still there after 3-4 days, see a sports medicine doctor or physical therapist. Don't run through sharp localized pain.

Taper madness. In the final 2-3 weeks before the race, your mileage drops significantly. This is called the taper. It is psychologically brutal. You'll feel sluggish, your legs will feel heavy, your mind will tell you you're losing fitness. You're not. The taper is when your body stores glycogen and heals all the micro-damage from training. Every weird feeling during the taper is normal. Don't add extra miles because you feel anxious. Trust the process.

Race Day Basics

Pacing: The most common marathon mistake is going out too fast. Everyone feels great in mile 1. The first half of the marathon feels like nothing — you're on adrenaline, the crowd is there, your legs are fresh. Hold yourself back. A good target: run the first half about 1-2 minutes slower (total) than your goal finish time would suggest. You can negative split (run the second half faster than the first), which is both more comfortable and typically produces faster times.

What to eat: Don't change anything on race day. Eat what you've been eating before long runs. For most people that's something carbohydrate-heavy 2-3 hours before the start — oatmeal, toast, a bagel. Don't eat anything you haven't tested. Race morning is not the time to discover that a gas-station muffin doesn't agree with you.

The wall: Around mile 18-22, most first-timers hit what's known as "the wall" — a sudden and dramatic drop in energy that happens when glycogen stores run out. You can delay or avoid it by: starting conservatively, taking in carbohydrates consistently throughout the race, and being well-trained. You can't entirely prevent it in your first marathon. But you can mitigate it.

When the wall hits: slow down slightly, keep taking fuel, keep moving forward. Walk if you need to. Almost everyone who keeps moving eventually finishes. Almost no one who walks for the last 6 miles wishes they had skipped the race.

---

You don't need to be fast to finish a marathon. You need to be consistent, patient, and honest with yourself about recovery. The runners who finish their first marathons happy are the ones who trained slowly enough that the race itself felt like the reward — not the survival test.

If you're ready to build a plan around your actual fitness, schedule, and goal race, RunPlannerAI can create a personalized marathon training plan built around your current weekly mileage and target finish time.

For more detail on specific plan structures, see our marathon training plan guide or our dedicated beginner marathon training plan.