Why Does My Knee Hurt When I Run?
Written by Dr. Josh Funk, DPT
It depends, and that’s the honest answer worth trusting. Knee pain could be a variety of different conditions, and it isn’t typically the result of one cause. The three most common culprits in runners, runner’s knee, patellar tendinopathy, and IT band syndrome, sit in different places and behave differently. What they share is that they’re usually about movement prerequisites, load, and how you move, not damage to the knee itself. There’s no single villain, and no single fix. Which is why the real answer starts with an individualized evaluation to pinpoint your problem and what’s driving it, then a clear progression back to running.
This article is general education, not a diagnosis of your specific condition. Knee pain has several possible causes, and telling them apart accurately takes an evaluation. If your pain is sharp, followed a specific injury, or comes with swelling, locking, or the knee giving way, see a licensed physical therapist or physician immediately.
The three most common culprits, and how they differ
What tells them apart is where the pain sits and how it behaves.
Patellofemoral pain, “runner’s knee”: front of the knee, behind or around the kneecap. The most common overuse injury in runners, and its signature is that the pain is hard to pinpoint. It sits behind or around the kneecap and flares when the knee is loaded in a bent position: running, especially downhill, plus squatting, stairs, and long stretches of sitting with the knee bent (the classic “movie theater” ache). It’s genuinely multifactorial and is diagnosed largely by ruling other things out, which is exactly why a single tidy explanation rarely fits it.
Patellar tendinitis or tendinopathy: a pinpoint spot at the bottom tip of the kneecap. This one you can usually put a finger on, right where the tendon attaches at the lower tip of the kneecap. Its tell is load-dependent, dose-dependent pain: it turns on the moment you load the knee and switches off almost as soon as you stop, and it climbs with the size and speed of the load, jumping, hopping, decelerating, cutting. The most important part here is that the tendon is rebuilt with progressive loading, not rest.
IT band syndrome: sharp pain on the outside of the knee. The pain and tenderness sit over the outer knee, right around the bony bump on the outside of the thigh bone, and can radiate up or down from there. The giveaway is timing and terrain: it tends to arrive at a fairly predictable distance into a run, calms when you stop, and is worse downhill, because the knee spends more time in the shallow angle where the band compresses against that bump.
These are the three most common, not the only options. Running knee pain can also come from the meniscus, tendons elsewhere around the knee, or be referred from the hip or foot, which is one more reason a label you pick from an article, or a friend’s, so often points at the wrong plan.
What these injuries share: movement prerequisites, load, and how you move
For all their differences, these injuries have a common thread, and it isn’t one body part to blame. They’re problems with overuse or underpreparation, which means the demand placed on the knee outran what it was prepared to handle. That usually comes down to three things working together: your movement prerequisites, the mobility, control, and strength you need to run well, the load you’re putting through the knee, and how you actually move under that load. A training change, more mileage, more intensity, a block of hills, often tips a knee that was already short on one of them.
In plain terms, it’s about whether you have what it takes to handle what you’re asking of yourself. Sometimes it’s a missing prerequisite. Sometimes it’s the tissue’s capacity. Sometimes it’s the training math. For most runners it’s a mix, and the mix is personal, which is the whole reason a real answer means looking at you, not applying a template.
Why rest alone isn’t the fix
Here’s the trap runners fall into. Rest calms the pain, so it feels like the problem is solved. Then you start running again and it returns, because rest lowered the load without changing your capacity to handle it.
Recovering well means rebuilding the thing that was missing. That’s the R2P method, Movement Health, applied to your knee: build the quality of how you move (competency), build how much load your body can take (capacity), and prepare you for the real demands of running (conditioning). You keep moving where you can while that capacity comes back, and you return to full training on a plan rather than a hope.
This is why it takes a real evaluation
Because the three culprits look similar from the outside but call for different plans, and because the drivers are personal, getting this right starts with an individualized assessment, not a guess. A clinician sorts out which injury you actually have, then looks at the specific factors feeding it: your strength, your movement, your training history, and how you load the knee.
When it’s useful, that assessment can include objective testing and a running analysis to see what your body does at speed. Those are tools inside the evaluation, not the point of it. The point is a clear picture of your problem and a progression built for it. That’s what “Assess, Don’t Guess” actually means at R2P, and it’s why we build the plan around you rather than a generic protocol.
What the path back looks like
Tailored to the specific injury and what’s driving it, recovery generally follows the same shape:
- Settle it and manage load. Calm the irritation and adjust training so you can keep moving without flaring it.
- Rebuild capacity. Strengthen and load the right tissues so the knee can handle more than it could before. This is where most of the progress lives.
- Restore quality and readiness. Improve how you move and, for some runners, refine mechanics like cadence, then rebuild the specific demands of running.
- Return to mileage. Progress volume gradually, with hills and speed added back last.
When to get it checked
Most running knee pain is safe to address while staying active. Get evaluated sooner if the pain is sharp rather than achy, if it followed a specific injury, or if you have swelling, locking, or the knee giving way. And if you’ve rested and modified and it keeps returning, that’s the signal to stop cycling through guesses and get a real answer.
How Rehab 2 Perform fits
We work with runners across the spectrum, from first-timers in our Couch to 5K program to people chasing a marathon PR. Our job is to identify which injury you have, understand what’s driving it for you, and rebuild your Movement Health so you get back to running and stay there. That’s fitness-forward healthcare: we don’t stop when the pain quiets down, we build the capacity that keeps it away.
You don’t need a referral to start. In Maryland and Virginia, direct access laws let you book an evaluation on your own decision.
Why this matters to me
I’m a Doctor of Physical Therapy and a former Division I and professional athlete. The advice runners hear most, “just stop running,” is almost always the wrong one. Running isn’t the enemy, and your knees aren’t fragile. Pain is information about load and how you move, and both are things we can assess and change, once we know exactly what we’re working with. That’s the standard we hold: understand it, then build you past it.
Frequently Asked Questions
Running knee pain has several possible causes. The three most common in runners are runner’s knee (patellofemoral pain), patellar tendinopathy on the tendon just below the kneecap, and IT band syndrome on the outer side of the knee. Most are load-related issues rather than damage to the knee, and the right treatment depends on which one you have and what’s driving it.
Location is the fastest clue. Runner’s knee is felt at the front of the knee, around or behind the kneecap, and worsens with stairs and squatting. IT band syndrome is felt on the outer side of the knee, often appears at a predictable point in a run, and eases when you stop. An evaluation confirms it, since treatment differs.
Patellar tendinitis or tendinopathy is an overuse issue of the tendon at the lower tip of the kneecap, where the pain usually pinpoints. Its hallmark is load-dependent pain that turns on as soon as you load the knee and climbs with the size and speed of the load, like jumping, hopping, and decelerating. A rehabilitative program commonly includes progressive tendon loading rather than rest.
It’s usually a mix of factors rather than one cause: a change in training load combined with individual factors like strength, movement quality, and tissue tolerance. In short, the demand outran what the knee was prepared to handle. The specific mix is personal, which is why an individualized assessment matters.
Usually not. Rest lowers the load but doesn’t build your capacity to handle it, so the pain often returns when you run again. The better approach is identifying the specific problem, then managing load while you rebuild, so you can keep running through much of the process.
For most people, no. Running done sensibly isn’t inherently bad for your knees. Knee pain from running usually reflects a load or movement issue that can be identified and addressed, not permanent damage.
We start with an individualized evaluation to pinpoint which injury you have and what’s driving it, using objective testing and, when useful, a running analysis. From there we build a progression that restores how you move, your capacity to handle load, and your readiness to run, so you return to full training with less risk of it coming back.
In Maryland and Virginia, no. Direct access laws let you begin physical therapy without a physician’s referral.
Ready to Perform at Your Best?
You don’t have to choose between your knees and your running. If your knee hurts when you run, book an evaluation at one of our 15 DMV locations. We’ll pinpoint which problem you have, understand what’s driving it, and build a clear progression so you recover well and reduce the risk of it coming back. No referral needed in Maryland or Virginia. That’s Ready 2 Perform, and Assess, Don’t Guess.