How to Know If You're Overtraining From Running

What are the earliest signs you're overtraining?

The earliest signs are usually an elevated resting heart rate paired with fatigue that doesn't lift after a normal rest day. Your resting heart rate (RHR) is the number of beats per minute measured first thing in the morning, before you sit up or check your phone. It reflects how recovered your nervous system is overnight. A rise of roughly 5 to 10 beats per minute above your personal baseline for three or more consecutive mornings — especially combined with an easy run that suddenly feels like a moderate one — is a common early flag in the sports-medicine literature on training stress. One rough morning doesn't mean much; a multi-day pattern does.

A second early tell is a creeping rise in perceived effort (RPE, or rate of perceived exertion) at paces that used to feel automatic. If an 10:00/mile easy run now feels like a 9-out-of-10 effort instead of a 4-out-of-10, that's your body telling you the tank is lower than your training log suggests.

How can I tell a normal niggle from an overuse injury forming?

Normal training soreness — delayed-onset muscle soreness, or DOMS — is symmetrical, peaks 24 to 48 hours after a hard session, and fades within 3 to 5 days on its own. A niggle that lasts longer than a week, shows up on only one side, or gets sharper rather than duller as you keep running is behaving differently, and it's worth paying attention to.

This matters because the majority of running injuries are classified as overuse injuries rather than the result of a single traumatic event, according to orthopaedic and sports-medicine sources. That means the low-grade, easy-to-dismiss signals are often the only warning you get before a stress reaction becomes a bone stress injury or a tendon irritation becomes tendinopathy. Recurring issues that seem minor in isolation — blisters that keep coming back, shoulder and neck tension, calf tightness, or side stitches that show up more on tired days — can all be downstream effects of accumulating fatigue changing how you move, not just isolated nuisances.

What is the acute:chronic workload ratio, and how do I use it?

The acute:chronic workload ratio (ACWR) compares your training load over the past 7 days (acute load) against your rolling average load over the past 28 days (chronic load). Training load can be calculated simply, such as weekly distance multiplied by an average perceived-effort score, or pulled from a GPS watch's built-in load metric.

Research popularized by sports scientist Tim Gabbett found that spikes in training load are strongly linked to injury risk, and the acute:chronic workload ratio became a widely used tool for flagging those spikes before they turn into injuries. In that body of work, ratios climbing above roughly 1.5 — meaning this week's load is 50% higher than your typical month — were associated with a higher injury rate, while ratios in the 0.8–1.3 range are generally treated as a lower-risk zone. These are population-level thresholds from sports-science research, not a guarantee for any one runner, but they're a useful sanity check after a big volume or intensity jump.

Acute:Chronic Ratio What it suggests Practical response
Below 0.8 Undertraining or detraining Rebuild volume gradually, don't jump straight back to peak load
0.8–1.3 Commonly cited "sweet spot" Continue your current plan
1.3–1.5 Caution zone Hold volume steady, watch fatigue and sleep markers closely
Above 1.5 Higher-risk spike Consider a deload week, add recovery days

A phone-based tool like StrideIQ can flag things like a drop in cadence (steps per minute) or a growing left-right asymmetry during an easy run — sometimes a sign of accumulating fatigue — but it doesn't calculate acute:chronic load. That's a training-log or GPS-watch metric, and it's worth tracking alongside anything a single video can tell you.

Can sleep and mood really signal overtraining before it shows up as an injury?

Often, yes. Position statements on overtraining syndrome from major sports-medicine bodies list disturbed sleep, loss of motivation, irritability, and a sense of increased effort at familiar paces among the recognized clinical signs of accumulated training stress, alongside physical markers like elevated resting heart rate.

If you're sleeping fewer than 7 hours a night for several nights running despite feeling exhausted, or you're dreading runs you used to look forward to, treat that as data rather than just a bad mood. Appetite changes, a flattened motivation to train, and irregular menstrual cycles in female runners are also worth tracking — the last one can be a marker of low energy availability, which is a separate but related concern from training-load overtraining.

What's the right way to deload or rest when you're overreaching?

A standard deload cuts weekly training volume by roughly 20 to 40% for one week, typically scheduled every 3 to 4 weeks as part of normal periodization, and more aggressively (and for longer) if you're already showing fatigue markers rather than doing it preventively.

During a deload:

If a single deload week doesn't resolve the fatigue, elevated RHR, or lingering niggle, that's a signal to look further rather than push through — training adjustments alone may not be the fix.

What can self-monitoring and form checks NOT tell you about overtraining?

Tracking resting heart rate, sleep, training load, and mood gives you useful early signals, but none of these tools — including a training log, a wearable, or a phone-video form check — can diagnose overtraining syndrome, a bone stress injury, anemia, or Relative Energy Deficiency in Sport (RED-S). They flag patterns worth investigating; they don't replace a clinical evaluation.

The evidence connecting training-load spikes to injury is genuinely strong at the population level, but individual response to load varies a lot, and no ratio or heart-rate number can promise a specific runner will or won't get hurt. Similarly, a single phone video can estimate cadence reliably but has much lower confidence for things like ground-contact time or joint angles, so it's a limited window into what's actually driving fatigue.

See a sports medicine physician or physical therapist if elevated resting heart rate or fatigue doesn't improve after about a week of easy running and extra sleep, if pain doesn't fade with rest, or if you notice a missed or irregular menstrual cycle or unexplained weight change. This article is general information for a performance-minded runner monitoring their own training — it isn't a diagnosis or an individualized treatment plan.

Frequently Asked Questions

How many rest days do I need if I think I'm overtraining?

There's no fixed number that applies to everyone. Many runners benefit from 2-4 additional easy or off days combined with a deload week (20-40% less volume) before reassessing resting heart rate, sleep, and how easy runs feel. If symptoms persist beyond that, see a sports medicine provider rather than guessing at more rest on your own.

Is it okay to run through mild soreness?

Mild, symmetrical soreness that fades within a few days (DOMS) is generally fine to run through at an easy effort. Soreness that's one-sided, sharp, worsens during the run, or lingers past a week is a different signal and worth backing off from, and possibly getting assessed.

How long does a deload week take to show results?

Most runners see resting heart rate and perceived effort at easy paces normalize within 3-7 days of a genuine deload. If fatigue or elevated RHR persists past that, it's worth looking beyond training load alone — sleep, nutrition, illness, or a developing injury may be involved.

Can I be overtraining even if I don't feel injured?

Yes. Overtraining symptoms often show up first as fatigue, mood changes, disturbed sleep, or a plateau or decline in performance well before any specific pain appears. Waiting for pain as the trigger to act misses the earlier, more useful warning signs.

Sources