When It Hurts — Don’t Run. Or Should You Run Anyway?

Almost every runner deals with pain.

Sometimes it’s just a trace of training. And sometimes it’s a signal to stop.

How do you tell one from the other? When is pain part of progress, and when is it a warning sign of injury?

In this guide we’ll break down:

• acceptable vs dangerous pain,
• the difference between fatigue and damage,
• how to use the RPE scale,
• and give you a self-check table so you can make decisions without guessing.

🧠 Why it matters to tell one pain from another

“It hurts” is not a diagnosis. It can be anything from muscle soreness to a tear.

Your main task is to learn to recognize your body’s signals and not treat a fracture like fatigue (and vice versa).

🔍 Different types of pain

📌 Main rule: If pain gets worse during a workout → stop. If pain doesn’t go away at rest within 2–3 days → see a doctor.

🚨 Red flags: when you must not run

• Pain in one specific point that worsens with load
• Swelling, puffiness, bruising
• Clicking and locking in a joint
• Numbness, tingling, burning
• Pain that makes normal walking difficult
• Sleep disruption because of pain

📌 Any one of these is already a reason to stop. Two or more — definitely skip the workout and see a specialist.

✅ When running is okay

• Muscle fatigue after yesterday’s workout
• Muscle soreness that eases during warm‑up
• Mild pulling pain that doesn’t break your running form
• A feeling of “heaviness” that disappears after 10–15 minutes

📊 Self-check table: run or not

📌 If you have 2 or more “❌” — skip the workout. If you have 3 or more “✅” — you can most likely run, but at an easy pace.

🔟 RPE scale: how to measure load

RPE (Rate of Perceived Exertion) is a subjective load scale from 1 to 10, where:

• 1 — rest
• 3–4 — easy run, you can chat
• 5–6 — moderate run, breathing deeper
• 7–8 — hard run, talking is difficult
• 9 — almost maximum
• 10 — all-out effort

📌 RPE helps you connect heart rate, perception, and pain.

📘 How to use RPE together with pain

🔄 How to adjust your plan when you’re in pain

If the pain is acceptable but slows your progress:

• Reduce the volume (run 6 km instead of 10)
• Remove intervals and tempo sessions
• Run by heart rate or RPE, not by pace
• Swap running for swimming, cycling, elliptical
• Add self-massage, sleep, nutrition — recovery doesn’t happen on its own

🛠 How to do a “test run” when you’re in pain

If you’re unsure, do a running check:

1. Warm up for 10–15 minutes
2. Easy run for 5–10 minutes
3. Assess: did the pain go away, stay, or get worse?
4. Re-assess 2 hours later and the next morning

📌 If the pain got worse after the test → rest at least 48 hours.

🧘‍♂️ Not everything that hurts is bad

• Muscle soreness is a sign of growth — as long as it’s moderate
• Muscle pain is more a sign of overload than of injury
• Sometimes uncomfortable ≠ dangerous

But…

If you can’t say “it’s under control” — then it’s already not under control.

🎯 Prevention: don’t push it to pain

• Increase volume by no more than 10% per week
• Add strength training twice a week
• Watch your form and cadence (170–180 steps/min)
• Sleep at least 7 hours
• Don’t run tempo when you’re not recovered

📌 Quick decision cheat sheet

🧠 Key points

• Pain ≠ a complete ban, but pain without analysis is a direct path to injury
• Use the RPE scale and the self-check table
• It’s not heroics that keeps you in shape, but consistency and recovery
• When in doubt — rest. It’s not a step back, it’s a pause for progress

And remember: the ones who keep training aren’t those who never get injured, but those who know how to stop in time.