
To start running as a beginner, alternate short runs with walking — 1 minute of running and 2 minutes of walking, repeated 8 times, 3 days a week — and build the running intervals gradually over 4 to 8 weeks. Most beginners can run a 5K (3.1 miles / 5 km) without stopping in 8 to 12 weeks. The two rules that matter most: run slowly enough to hold a conversation, and never increase your weekly running time by more than about 10%. See what your first runs burn with our running calories calculator — this guide gives you the week-by-week plan, the shoe and warm-up basics, the mistakes that end most beginner attempts, and the red flags that mean stop and get checked.
That first session is 24 minutes total (8 × 3 minutes = 24) with only 8 minutes of actual running, and that is exactly right. The CDC physical activity guidelines recommend 150 minutes of moderate activity a week for adults, and three 24-minute run/walk sessions put you at 72 minutes in week 1 — nearly halfway there before you can run a full mile. You do not need to be fit to start running; running is how you get fit, and the walking breaks are the plan, not a failure of it.
See What My Runs BurnThe plan below is the classic beginner structure, used by Couch-to-5K programs for decades: three sessions a week, with at least one rest day between sessions, and running intervals that grow while walking intervals shrink. Each session starts with a 5-minute brisk walk as a warm-up and ends with a 5-minute easy walk to cool down — those minutes are not in the table, so add 10 minutes to each session total. By the end of week 4 you will be running 20 minutes in a single session, which is more than halfway to a 5K for most beginners. If a week feels hard, repeat it before moving on — repeating a week is progress, not a setback, and it is how you avoid the overuse injuries that stop most beginners in week 3.
| Week | Run / walk pattern | Repeats | Running minutes | Session total* |
|---|---|---|---|---|
| Week 1 | Run 1 min / walk 2 min | × 8 | 8 min | 24 min |
| Week 2 | Run 2 min / walk 2 min | × 6 | 12 min | 24 min |
| Week 3 | Run 3 min / walk 2 min | × 5 | 15 min | 25 min |
| Week 4 | Run 5 min / walk 2 min | × 4 | 20 min | 28 min |
| After week 4 | Run 8 min / walk 2 min | × 3 | 24 min | 30 min |
*Session total excludes the 5-minute warm-up walk and 5-minute cool-down walk; add 10 minutes for the full session.
After week 4, keep the same pattern: lengthen the run intervals and shorten the walks until the walking breaks disappear. A typical path is week 5 at 8 minutes of running per interval, week 6 at 10 minutes, week 7 at 15 minutes, and week 8 running 30 minutes continuously — which, at a beginner pace of about 11 to 12 minutes per mile, covers roughly 2.5 to 2.75 miles (4 to 4.4 km), within sight of the 3.1-mile (5 km) finish line. Some beginners get there in 8 weeks, most in 10 to 12, and both are normal: the timeline depends on your starting fitness, your age, and how consistently you run three times a week. The calorie side is straightforward too — a 160 lb (73 kg) runner burns roughly 100 calories per mile, so a 3-mile run is about 300 calories. Our running pace calculator turns your target distance into a per-mile pace you can actually hold.
Proper running shoes are the single most important purchase a beginner makes, and they are the only gear you truly need. Running shoes are built to absorb impact and guide your foot through its natural stride; everyday sneakers, cross-trainers, and fashion trainers are not, and running in them is the fastest route to shin splints and sore knees. Go to a specialty running store if you can: most will watch you walk and jog, check whether your feet roll inward or outward, and recommend shoes that fit your gait — and many let you run in them and exchange them if they do not work. Expect to pay about $80 to $130 for a good beginner pair, and replace them after roughly 300 to 500 miles (480 to 800 km), when the cushioning wears out even if the uppers still look fine.
Fit matters more than brand. Your running shoes should be about half a size larger than your everyday shoes, because feet swell during a run — you should have about a thumb's width (roughly 0.5 in / 1.3 cm) between your longest toe and the end of the shoe. Try them on in the afternoon, when your feet are at their largest, wearing the socks you will run in. And buy running-specific socks too: moisture-wicking synthetic or wool-blend socks prevent the blisters that cotton socks cause once they get damp. Everything else — watch, belt, fancy shirt — is optional. Cotton t-shirts chafe when they get sweaty, so a cheap synthetic top is worth it, but do not let gear shopping delay the first run: shoes, socks, and anything comfortable will do.

The most common beginner mistake is running too fast, and the fix is the talk test: you should be able to speak in full sentences while you run. If you can only gasp out a word or two, slow down — walk if you have to, because the plan says the walking breaks are part of the workout. This conversational pace is roughly Zone 2, about 60 to 70% of your maximum heart rate, and it is where beginners build the aerobic base that makes everything else possible. A rough maximum heart rate estimate is 220 minus your age — so for a 40-year-old, about 180 beats per minute, with conversational running at roughly 108 to 126 beats per minute. Our heart rate zones calculator works out your zones from your age and resting heart rate if you want the numbers.
Forget speed entirely for the first month. Your only goals are time on your feet and consistency: three sessions a week, every week. A beginner pace of 11 to 13 minutes per mile (about 6:50 to 8:05 per km) is completely normal, and many beginners start at 13 to 15 minutes per mile. Speed comes later, and it comes on its own: the same run that feels hard in week 1 will feel easy by week 6 at the same pace, because your heart, lungs, and legs have adapted. The runners who improve fastest are not the ones who push hardest in week 1 — they are the ones who are still running in week 8, and the ones still running in week 8 are the ones who went slowly enough to enjoy it.
Every run starts with a 5-minute brisk walk, then 2 to 3 minutes of easy leg swings and gentle dynamic movement — walking lunges, high knees at walking pace, and ankle circles — before the first running interval. Static stretching (holding a stretch for 30 seconds) belongs after the run, not before it: research consistently shows static stretching cold muscles does not prevent injury and can slightly reduce performance, while a dynamic warm-up raises muscle temperature and prepares joints for impact. The cool-down is the mirror image: 5 minutes of easy walking after the last interval, then gentle static stretches for calves, quads, hamstrings, and hip flexors, holding each for 20 to 30 seconds while your breathing settles.
Skipping the warm-up is the beginner shortcut that costs the most. Cold muscles and tendons are stiffer and less elastic, and the first running interval is when most strains happen — a pulled calf or a tweaked hamstring in week 2 can cost you three weeks of running, which is exactly the kind of setback that ends a new habit. The full warm-up and cool-down add 10 minutes to a 24-minute session, making it 34 minutes door to door, and they are the cheapest injury insurance in the sport. If you are short on time, cut a running interval — never cut the warm-up.
Running too fast is mistake number one, covered above — if you cannot talk, you are too fast. Mistake number two is running every day: beginners need rest days because the fitness gains happen during recovery, not during the run, and running on tired legs is how shin splints and stress fractures start. Three days a week with a rest day between sessions is the right dose for the first two months. Mistake number three is increasing too much too soon — the 10% rule says never add more than about 10% to your weekly running time, so a week of 24 running minutes becomes 26 or 27, not 40. Mistake number four is comparing yourself to other runners: the person passing you on the trail has probably been running for years, and their easy pace is your sprint — run your own plan. Mistake number five is ignoring pain that changes your stride: soreness that fades as you warm up is normal, but pain that makes you limp or alter how you run is a signal to stop, rest, and reassess. And mistake number six is running in old or wrong shoes — if your shoes are past 500 miles or were never running shoes at all, fix that before blaming your knees.
Rest is not the absence of training — it is part of training. Muscle, tendon, and bone all adapt during the 24 to 48 hours after a run, which is why the plan puts a rest day between sessions and why a rest week every fourth week (cutting volume by about 20 to 30%) is smart once you are running 30 minutes or more. On rest days, walking is excellent: a 30-minute walk keeps blood flowing and adds to your weekly activity without stressing the same tissues. Sleep matters too — most adults need 7 to 9 hours, and poor sleep is one of the biggest predictors of a bad run and a nagging injury. If you want to track the walking side of your recovery, our walking calories calculator shows what those easy miles add up to.
So what is a realistic 5K timeline? A complete beginner following the plan three times a week typically runs 30 minutes continuously in 8 weeks and finishes a 5K in 10 to 12 weeks, at a pace of about 11 to 13 minutes per mile — a finish time of roughly 34 to 40 minutes for 3.1 miles (3.1 × 11 = 34.1 and 3.1 × 13 = 40.3). If you already walk regularly or play other sports, you may get there in 6 to 8 weeks. If you miss sessions, it takes longer — and that is fine, because the goal is a habit that lasts, not a deadline. The CDC's guideline of 150 minutes of moderate activity a week is a useful checkpoint: by the time you are running 30 minutes three times a week plus walking on rest days, you are comfortably exceeding it, and the habit is doing far more for your health than any single race time.
Most beginner running pain is normal adaptation — muscle soreness that peaks 24 to 48 hours after a run and fades, or a mild ache that disappears once you warm up. The red flags are different and specific: sharp pain that starts suddenly during a run; pain in one spot on a bone (especially the shin or foot) that hurts to touch; knee pain that swells; pain that makes you limp or change your stride; pain that is worse the morning after a run and does not improve over two or three rest days; or any chest pain, dizziness, or unusual breathlessness during exercise. Bone pain that is pinpoint and tender is the classic sign of a stress reaction or stress fracture, and running through it can turn weeks of rest into months. Chest pain or dizziness during exercise is a stop-immediately-and-seek-care symptom, not a push-through-it one. When in doubt, rest for a few days — fitness lost in a week of rest is regained in a week of running, but an injury ignored for a month can cost a season. If pain persists beyond a week of rest, see a doctor or a physical therapist rather than guessing.
Our running calories calculator shows what those first miles burn, and our running pace calculator sets a pace you can hold.
Calculate My Run BurnWritten by the Live Fitness Check editorial team · Reviewed against our calculator methodology · Last updated November 2026
Disclaimer: This guide is for general information only and is not medical advice. If you have a heart condition, joint problems, or have been inactive for a long time, talk to your doctor before starting a running program. Stop and seek care if you experience chest pain, dizziness, or unusual breathlessness during exercise.