This question has one honest answer and one popular answer, and they are not the same. The popular answer is sixteen weeks, because that is the length of most published plans. The honest answer is that sixteen weeks is how long the final block takes, and the length of everything before it depends entirely on where you are starting from.
So this guide answers it from four different starting points, explains what actually sets the limit, and shows you how to work backwards from a race date to the week you need to begin.
The four starting points
| Where you are now | Time to the start line | What the time is for |
|---|---|---|
| Not currently running | 9-12 months | Six months or so building to a comfortable 10K and a consistent 20-mile week, then a full 16-20 week marathon block on top. |
| Running 30 minutes comfortably | 6-8 months | Two to three months raising weekly volume and getting a long run to 10 miles, then the 16-20 week block. |
| Running 15-20 miles a week, can run a 10K | 16-20 weeks | Straight into a marathon block. This is the runner every published plan is written for. |
| Running 30+ miles a week with a recent half marathon | 12-16 weeks | You already have the base. The block is about marathon-specific long runs and race-pace work. |
The row that matters most is the third one, because almost every training plan you can download assumes you are in it. A plan that opens with a 10-mile week and a 6-mile long run is not a beginner plan; it is an intermediate plan with a gentle first fortnight. If you cannot currently run 6 miles, week one of that plan is already a hard session.
The honest test
Can you run for an hour, today, without stopping and without it being an event? If yes, you are ready to start a 16-week block. If no, the sixteen weeks starts after you can — and the time it takes to get there is the part nobody counts.
What actually sets the limit
Cardiovascular fitness improves quickly. Within six to eight weeks of consistent running, most people are noticeably fitter — heart rate at a given pace drops, easy runs stop feeling like work, and the temptation to compress the timeline becomes strong.
The structures that carry you — tendons, ligaments, bone, connective tissue — adapt far more slowly, on a timescale of months rather than weeks. That mismatch is the single most common cause of marathon training going wrong: your engine outpaces your chassis, you feel great, you add volume to match how you feel, and something in a shin or an achilles or a hip objects.
This is why the answer to "how long does it take" is not a fitness question. Nearly everyone who fails to make a marathon start line healthy did so by treating it as one.
- Increase weekly volume gradually and take a lower-volume week roughly every fourth week. The exact percentage matters less than the principle of not adding week on week indefinitely.
- The long run is the session that builds the marathon and the session most likely to injure you. Extend it in small steps and not every single week.
- Most of your running should be genuinely easy — conversational, and slower than feels dignified. This is the part people skip, and it is the part that lets the volume happen at all.
- Consistency over months beats intensity over weeks. Four steady months will get you further than six brilliant weeks and a stress fracture.
Working backwards from a race date
The practical version of all of this is a subtraction. Take your race date, subtract the block, subtract the base-building, and you have the week you start — and, more usefully, an honest answer about whether the race you are looking at is the right one.
| Race date | Block starts | If you need base first, start |
|---|---|---|
| A spring marathon in late April | Early January | The previous summer |
| An autumn marathon in mid-October | Late May / early June | The previous winter |
Most UK marathons fall into two clusters, which makes this easier than it sounds. The spring cluster runs from early April to the end of May — Brighton, London, Manchester, Milton Keynes, Edinburgh — and the autumn cluster sits in October, with Chester, Yorkshire and Abingdon within a week of each other. Pick a cluster, count backwards, and you have your start date.
If the subtraction produces a date in the past, that is useful information rather than a failure. It means you want the next cluster, and the extra six months will produce a better race and a healthier build.
What the 16 to 20 weeks are actually for
A marathon block is not simply more of what you were already doing. It has a shape, and understanding the shape tells you why it cannot be meaningfully compressed.
| Phase | Rough length | What it does |
|---|---|---|
| Base | 4-6 weeks | Raise weekly volume, get the long run moving, add strides. No heroics. |
| Build | 6-8 weeks | The longest long runs, threshold work, and marathon-pace running inside them. |
| Peak | 2-3 weeks | The hardest fortnight of the block, and where a well-executed plan feels genuinely difficult. |
| Taper | 2-3 weeks | Volume drops 40-60%, intensity largely stays. This is where the training becomes fitness. |
Notice that the taper is two to three weeks of the sixteen. That is not slack in the plan you can reclaim — cutting it is one of the more reliable ways to arrive at the start line tired, and the marathon taper guide covers why in detail.
Can you do it faster than that?
People do. Twelve-week plans exist, people complete marathons off eight weeks of training, and someone you know finished one on almost nothing and will tell you about it. All of that is true and none of it changes the advice.
What a compressed timeline actually buys you is a higher chance of one of three outcomes: an injury before the start line, a race that becomes a walk somewhere after twenty miles, or a recovery that takes considerably longer than the training did. If the date is fixed and the timeline is short, the sensible adjustment is the goal rather than the schedule — go in aiming to finish comfortably rather than to hit a time, and treat it as the first marathon rather than the only one.
The one exception worth naming
If you have run marathons before and have been consistently running through the year, 12 weeks is genuinely enough, because you never lost the base. The timeline is short for people building from nothing, not for people returning to something.
How many hours a week does it take?
The other half of the question, and the one that decides whether the plan survives contact with your life. Rough guide, for the block itself rather than the base-building:
| Goal | Days running | Typical weekly hours at peak |
|---|---|---|
| Finish comfortably | 3-4 | 4-6 hours, with the long run taking half of it |
| Run a specific time | 4-5 | 6-8 hours |
| Chase a personal best | 5-6 | 8-10 hours or more |
The long run dominates all three, and it dominates increasingly as the block goes on. A three-hour long run plus fuelling, changing and being fit for anything afterwards is most of a weekend morning, and it happens most weekends for four months. That is the commitment people underestimate — not the hours, but which hours.
Put a date on it
The single largest difference between people who complete a marathon build and people who intend to is whether there is a date. An entry paid for and a start line in the calendar converts a vague ambition into a series of Tuesdays that have to happen.
This is also, for what it is worth, the whole idea behind a Verus profile: you set where you are starting from and the date you are aiming at, and the journey between them is the thing on the page. It is a public commitment rather than a private intention, and public commitments survive February better.