Photo by Markus Winkler on Pexels
You’ve read the studies. Running helps manage type 2 diabetes — improves insulin sensitivity, helps with weight management, lowers cardiovascular risk. Great. None of that tells you what to actually do when you’re lacing up at 6:30am, your fasting glucose reads 9.2 mmol/L, and you’re not sure whether to eat first, skip the run, or just go and hope for the best.
This is the gap most generic advice leaves you in. “Exercise is good for diabetes management” is true and also useless at 6:29am. What you need is what to check, when to eat, what to carry, and what a bad number actually means for today’s run — not next month’s HbA1c.
This isn’t medical advice — always work with your GP or diabetes team on your specific plan, especially if you’re on insulin or sulfonylureas, where the hypoglycemia risk is real and different from someone managing with metformin or lifestyle alone. But here’s what actually helps on the ground.
Check your numbers, but know what you’re checking for
If you’re newly running with type 2 diabetes, testing before and after a run for the first few weeks tells you far more than any generic pace chart. You’re building your own reference data — how your body responds to running, not a textbook body.
- Before you run: aim for 5–15 mmol/L (90–270 mg/dL) as a general safe-to-start range, though your own target range should come from your care team. Below 5 mmol/L, eat something with fast carbs before heading out.
- After you run: test again, especially in the first month. This is how you learn your personal pattern — some runners see a modest drop, some see numbers hold, a few (especially on certain medications) see a delayed drop hours later.
- If you use a CGM: use it. Watching the trend arrow during a run beats a single static number. A flat or slightly rising arrow before you start is a green light; a sharp downward arrow means wait or fuel first.
The goal isn’t perfection — it’s pattern recognition. By week four or five of regular running, most people know roughly what a Tuesday morning easy run does to their number without needing to test every single time.
Time your run around your medication, not just your schedule
This matters more than pace or distance. If you’re on insulin or a sulfonylurea (like gliclazide), your hypoglycemia risk is highest when insulin activity peaks — which varies by drug and dose, so this is genuinely a conversation for your prescriber, not a blog post. But general timing principles that most runners find useful:
- Running 1–2 hours after a meal tends to be more stable than running fasted, particularly if you’re on medication that can cause lows.
- If you run fasted (popular for early risers), keep the run easy and short — 20–30 minutes — until you know your fasted response.
- Avoid running during your medication’s peak activity window if that’s when you’re most prone to lows. Your pharmacist or diabetes nurse can tell you when that is for your specific drug.
If you’re metformin-only or managing through diet and exercise alone, hypoglycemia risk during running is low — this whole section matters less for you, and you can focus more on the consistency piece than the safety piece.
Fuel like a runner who also has diabetes — not the other way around
Standard running nutrition advice (“carb up before a long run”) still applies, but the timing and composition matter more for you.
Before a run under 45 minutes: you often don’t need to eat specifically for the run — normal meal timing is fine, assuming your pre-run number is in range.
Before a run over 45 minutes, or any run where you’re worried about a low: 15–20g of carbs 15–30 minutes beforehand — a banana, a slice of toast, a small glass of juice. Pair with a small amount of protein if you have time, which slows the glucose response slightly.
During long runs (60+ minutes): carry fast-acting carbs regardless of your current number. Glucose tablets, a small gel, or jelly babies work. This isn’t the same advice as a non-diabetic marathoner reaching for energy gels purely for performance — for you, it’s also a safety net.
Here’s a rough framework, but again — personalise this with your own testing:
| Run duration | Pre-run check | Carry with you | Post-run check |
|---|---|---|---|
| Under 30 min | Optional if in range | Nothing extra needed | Optional |
| 30–60 min | Recommended | Glucose tabs (just in case) | Recommended |
| 60+ min | Essential | Fast carbs every 45 min | Essential, and again 2–3 hrs later |
| Any run, if on insulin/sulfonylurea | Essential | Fast carbs, always | Essential |
Watch for delayed lows, not just during-run lows
This is the part most first-time runners with diabetes get caught out by. You finish your run, you feel fine, your number looks fine — and then three or four hours later, sometimes even the next morning, you crash. This is because muscles keep pulling glucose from the blood to replenish glycogen stores well after you’ve stopped moving, an effect that can last up to 24 hours in some cases.
Practical response: test again a few hours after a longer or harder run, not just immediately after. If you’re prone to this, a slightly bigger post-run meal with some slow-release carbs (oats, wholegrain bread) can help smooth it out. This matters more after your long runs than your short easy ones — worth knowing if you’re following a structured plan like a 12 week half marathon training plan, where the long run is doing most of the heavy lifting physiologically.
Start easier than you think you need to
If you’re newly diagnosed, newly running, or both, the instinct is often to go hard because you want results fast. Resist it. Running at an easy, conversational pace — the kind where you could hold a sentence without gasping — is not just standard beginner advice, it’s specifically useful here. Easy efforts produce steadier, more predictable glucose responses than hard intervals or hill repeats, which can sometimes cause your blood sugar to rise temporarily due to stress hormone release, confusingly the opposite of what you’d expect. If you see a number that goes up after a hard effort, that’s a known and normal response, not a sign you’re doing something wrong.
Understanding your heart rate zones for running is genuinely useful here — zone 2 effort is both the safest starting point for blood sugar stability and the right building block for aerobic fitness anyway. Two birds.
If you’re starting from near-zero fitness, a structured beginner plan like Couch to 5K works well precisely because it’s gradual — the walk-run structure keeps effort low enough that you’re not throwing your glucose around while you’re also learning to test, fuel, and time your runs.
Hydration matters more than usual
Dehydration concentrates blood glucose and can make numbers look worse than your actual metabolic state — worth knowing before you panic over a slightly high post-run reading on a hot day. The signs of dehydration while running are the same for everyone, but if you’re managing diabetes, staying ahead of it rather than reacting to thirst is worth the extra discipline. On runs over an hour, especially in heat, an electrolyte drink can help — just check the carb content of whatever you’re using, since some are surprisingly sugar-heavy.
Know your personal warning signs, and don’t push through them
Standard low blood sugar symptoms — shakiness, sweating, sudden irritability, confusion, blurred vision — can overlap with normal hard-effort symptoms, which makes them easy to dismiss mid-run. The difference: normal exertion symptoms fade quickly once you slow down. A low doesn’t. If you stop, walk, and the shakiness or fog doesn’t lift within a couple of minutes, treat it as a low — test if you can, and take fast carbs regardless.
This is genuinely one of the few areas where “just push through, you’re tougher than you think” is the wrong advice. Pushing through a real low is how people end up in trouble, not how they build resilience.
The Honest Takeaway
- Test before and after runs for the first month, even if it feels excessive — you’re building your own personal data, and it’s the fastest way to stop guessing.
- Time runs 1–2 hours after eating where possible, and know your specific medication’s peak activity window by asking your prescriber directly.
- Carry fast carbs on any run over 30 minutes, no exceptions, regardless of how your number looks beforehand.
- Check again 3–4 hours after longer or harder efforts — delayed lows are common and easy to miss if you only test immediately post-run.
- Keep early runs easy and short. This is not the phase for proving anything — it’s the phase for learning how your body actually responds, which is what makes every run after this one safer and more useful.