How to Get Rid of a Side Stitch While Running: My 90-Second Reset

If you want to know how to get rid of a side stitch while running, my first move is simple: I reduce the load before I fight the pain. I shorten my stride, drop to an easy jog or brisk walk, and let my breathing settle. Then I press gently into the sore area while breathing out slowly. If the pain releases, I rebuild pace in stages. If it does not, I stop the run.

That is the field answer I have used across 12 years of running. I do not promise an instant cure, because a side stitch—also called exercise-related transient abdominal pain—does not have one proven cause or one guaranteed fix. I use a short rescue sequence, then decide from the response rather than from pride.

Runner slowing to a walk and applying gentle pressure below the ribs during a side stitch
Reducing intensity is the first step; pressure and controlled breathing are comfort measures, not guaranteed cures.

My 90-second side-stitch rescue

When the familiar sharp pull appears under my ribs, I run this sequence in order. I give each step enough time to change the sensation. I do not stack five frantic tricks on top of one another.

0–15 seconds: downshift immediately

I stop chasing pace. I shorten my stride, soften the effort, and move to a jog. If the pain is already changing my posture or breathing, I walk. A side stitch is usually a performance problem before it is a danger signal, but forcing the original pace gives me no clean way to judge what is happening.

15–35 seconds: make room for the exhale

I relax my shoulders and stop taking shallow, hurried breaths. I inhale comfortably, then make the exhale a little longer without forcing it. I may purse my lips if that helps me control the outflow. My aim is not a magical breathing ratio. My aim is to reduce panic, restore rhythm, and see whether lower effort changes the pain.

If breathing feels chaotic even before a stitch appears, I work on effort-based control away from the crisis. My guide to breathing while running explains the cues I use from easy pace to hard efforts.

35–55 seconds: support the sore spot

I place my fingers over the painful area and apply firm but comfortable pressure as I exhale. I do not dig into my abdomen or keep pressing if touch makes the pain worse. Sometimes I lean forward slightly for a few steps. This is a low-risk relief attempt, not proof that I have identified the tissue causing the pain.

55–75 seconds: check whether the trend changed

I ask one question: is the pain clearly easing? “Maybe” is not the same as yes. If it is fading while I walk or jog, I stay easy. If it is stable, intensifying, spreading, or paired with another symptom, I stop testing it.

75–90 seconds: choose the run, not the ego

If the pain has nearly disappeared, I resume with several minutes at a genuinely easy pace. I do not surge to “make up” lost time. If the pain returns as soon as I increase effort, I end the hard work and jog or walk home. If it does not settle at low effort, I end the run.

My rule: a side stitch that improves gives me permission to reassess—not permission to race the next minute.

Does the pain behave like a side stitch?

I never label all side or abdominal pain a stitch. A typical episode begins during exercise, is fairly localized—often near the lower edge of the ribs—and may feel sharp or stabbing when strong, or cramping, aching, or pulling when milder. It usually improves when I slow or stop. Some runners also feel discomfort near the shoulder tip.

Pattern I treat as a likely stitchPattern I do not self-label
Starts during running and tracks with effortAppears at rest or wakes me from sleep
Localized under or near the rib marginDiffuse, steadily worsening, or unusually tender abdomen
Eases when I slow, walk, or stopPersists well after exercise or keeps recurring outside running
No major accompanying symptomsChest pain, breathing difficulty, faintness, fever, vomiting, blood, or a rigid abdomen

This comparison is a safety filter, not a diagnosis. If I cannot confidently say the pattern is familiar and transient, I do not use a running article to explain it away.

What I think is happening—and what I refuse to pretend

I have heard side stitches blamed on a cramped diaphragm, poor fitness, dehydration, weak abs, eating too much, breathing on the wrong foot, and nearly every organ under the ribs. None of those stories explains every episode.

The working explanations include irritation of tissues lining the abdominal cavity, movement or tension around abdominal structures, posture, and the effects of food or fluid in the gut. The pain is real; the precise mechanism is not settled. That uncertainty changes how I coach the problem: I look for the runner’s repeatable triggers instead of prescribing one universal cure.

Why I do not call it “just a diaphragm cramp”

The diaphragm story is easy to remember, but it is too neat. A stitch can occur in different abdominal locations, sometimes with shoulder-tip pain, and it responds inconsistently to breathing tricks. I still use controlled breathing because it lowers effort and helps me regain composure. I do not use the result to claim I cured a diaphragm spasm.

Why dehydration is not my automatic answer

A stitch is not a reliable dehydration test. At the same time, drinking a large volume quickly—especially a very concentrated or unfamiliar drink near hard running—can be provocative for some runners. I keep hydration needs and stitch troubleshooting connected but distinct. In hot weather I follow a sensible heat-running and hydration plan; I do not avoid necessary fluid out of fear of a stitch.

My side-stitch fingerprint

One isolated stitch tells me little. A repeated pattern tells me where to test. I build a “fingerprint” from six details and record them immediately after the run, before memory edits the story.

  1. Timing: how many minutes into the run did it start?
  2. Location: right, left, central, high, low, or shoulder tip?
  3. Effort: easy, steady, tempo, intervals, downhill, or race effort?
  4. Intake: what and how much did I eat or drink, and when?
  5. Context: heat, fatigue, poor sleep, hills, unfamiliar route, or nerves?
  6. Response: which action helped, how quickly, and did the pain return?

I care more about recurrence than coincidence. If three episodes follow a large pre-run meal, that is actionable. If one happened after a banana, I do not ban bananas for life.

The four trigger lanes I test

Lane 1: meal and drink timing

I look first at large meals, large drink boluses, and concentrated beverages close to the run. I do not impose one waiting time on everyone. Meal size, fat, fiber, intensity, and individual tolerance all matter. I begin by moving the suspected item earlier or reducing the amount—not by underfueling the entire day.

For a clean trial, I choose familiar food and keep it simple. My guide to foods worth testing carefully before a run helps narrow common troublemakers, while my broader runner’s nutrition guide keeps the experiment from turning into unnecessary restriction.

Lane 2: the opening effort

I often find the opening mile reveals more than the final mile. Excitement, hills, or cold legs can push breathing and torso movement higher before the body settles. I start deliberately easy, especially before a race or speed session, and then build. If I cannot speak a short sentence in an “easy” opening, I use my easy-run pace test to recalibrate.

Lane 3: warm-up and posture under fatigue

I use a short progressive warm-up before hard running rather than stepping from stillness into race pace. I want my breathing, stride, and trunk movement organized before the intensity rises. My eight-minute running warm-up gives me a repeatable baseline.

During the run, I avoid collapsing forward and bracing my abdomen like I am expecting a punch. I think “tall enough to breathe, relaxed enough to move.” There is no perfect posture that prevents every stitch, but my running-form framework helps me spot tension and overstriding without forcing a cosmetic pose.

Lane 4: trunk capacity

I include trunk strength because it supports running as a whole, not because I can promise planks will cure stitches. I train anti-extension, anti-rotation, carries, and controlled breathing under light load. Stronger trunk function may be useful, but an association is not the same as proof of prevention.

I keep that work proportional. Two consistent sessions beat a heroic core circuit that leaves me too sore to run well. My two-day strength plan for runners shows how I fit it around running.

My three-run trigger isolation

When stitches recur, I do not change food, warm-up, breathing, pace, and core training at once. That may help, but it teaches me nothing. I use three comparable easy runs on a familiar route and change one variable.

Run A: establish the honest baseline

I reproduce my normal routine without deliberately provoking pain. I record the six fingerprint fields. This is not a dare. If the stitch has been severe, atypical, or medically concerning, I skip the experiment and seek assessment.

Run B: change the strongest suspect

I move a large meal earlier, reduce a drink bolus, or slow the first ten minutes—whichever best matches the pattern. Everything else stays as similar as practical: route, duration, effort, and time of day.

Run C: repeat before I believe it

If Run B went well, I repeat the same setup. One symptom-free run can be luck. A repeated improvement is a better reason to keep the change. If the stitch persists across controlled trials, I stop chasing folklore and reassess the pattern more broadly.

Race-day decisions when the stitch arrives

In a race, I lose less time by responding early than by spending a mile twisted around the pain. At the first clear signal, I reduce effort slightly and lengthen the exhale. If it builds, I use the full 90-second rescue. I would rather walk for 20 seconds than turn a manageable stitch into a complete shutdown.

If it eases, I rebuild in three steps: easy running, steady running, then planned race effort. I give each step time. If the stitch returns, I drop back. I do not introduce an unfamiliar gel, gulp a large amount of fluid, or aggressively stretch my torso mid-race just because I am frustrated.

When I stop calling it a side stitch

I stop running and seek urgent medical help for sudden severe abdominal pain; a hard, rigid, or very tender abdomen; chest, neck, or shoulder pain; difficulty breathing; fainting; vomiting blood; or blood in the stool. I also get assessed when pain is persistent, worsening, occurs at rest, repeatedly appears in the same unusual pattern, or comes with fever, vomiting, unexplained weight loss, or urinary symptoms.

A familiar stitch should trend down when the load comes down. If it does not, I do not keep pressing on the area and running. For a broader decision boundary, I use my stop, modify, or get-help rules. This article cannot diagnose abdominal pain.

My five-step side-stitch decision card

  1. Reduce the load. I shorten my stride, slow to an easy jog, or walk.
  2. Settle the breath. I relax my shoulders and use a controlled, slightly longer exhale.
  3. Support, do not attack. I apply comfortable pressure to the sore area and may lean forward slightly.
  4. Read the trend. I continue only when the pain is clearly easing and no warning sign is present.
  5. Find the fingerprint. After the run, I record timing, location, effort, intake, context, and response before changing one trigger.

Frequently asked questions

How do I get rid of a side stitch fast while running?

I slow to a jog or walk, relax my shoulders, make my exhale controlled and slightly longer, and apply comfortable pressure to the painful area. If it clearly eases, I resume gradually. If it persists, worsens, or changes my movement, I stop the run.

Should I run through a side stitch?

I do not maintain hard effort through it. I reduce the load and judge the trend. I may continue easily if the pain nearly resolves and no warning sign is present, but I stop if it stays strong, returns with each pace increase, or feels atypical.

What causes a side stitch when running?

The exact cause is not settled. Possible contributors include irritation of tissues in the abdominal cavity, movement around abdominal structures, posture, recent food or fluid, and exercise intensity. I look for repeatable personal triggers instead of assuming one cause.

Does breathing on the opposite foot stop a side stitch?

It may help an individual runner regain rhythm, but I do not consider it a proven universal cure. I care more about lowering effort, relaxing the upper body, and producing a controlled exhale than matching every breath to a particular foot.

How long should I wait after eating before running?

There is no perfect interval for everyone. A large meal generally needs more time than a small familiar snack, and hard running is less forgiving than an easy jog. I change meal size or timing gradually and protect overall fueling rather than skipping food indiscriminately.

Can core exercises prevent side stitches?

Trunk strength is useful for runners and may help some people, but I cannot promise it prevents side stitches. I use consistent whole-body strength training as one foundation while testing more immediate triggers such as opening pace and pre-run intake.

When should side pain while running worry me?

I seek urgent help for sudden severe pain, a rigid or very tender abdomen, chest pain, breathing difficulty, fainting, or gastrointestinal bleeding. I arrange assessment when pain persists after exercise, occurs at rest, worsens, or comes with other unexplained symptoms.

My bottom line

I get rid of a side stitch by making the run easier first, not by trying to outsmart the pain at full speed. I slow down, settle my exhale, add comfortable pressure, and judge the trend. That sequence is memorable under stress and honest about uncertainty.

The bigger win comes after the run. I capture the fingerprint, change one likely trigger, and repeat the test. That is how I turn an annoying mystery into a manageable decision—without pretending every pain under the ribs is harmless.

Ken, founder of NextGait

Written by Ken — I have spent 12 years running more than 12,500 miles, testing 63 shoes, and completing 36 races from 5Ks to a 50K ultra. I run 30–40 miles most weeks on the Atlantic City Boardwalk and write from real training decisions, not one-run demos. More about me →

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top