How to Write a Chase Scene That Doesn't Drag
Outline, plan, and fix your story in StoryDev — AI that knows your entire story, on a visual canvas.
Start Free →Founding members lock in $5/mo forever · No credit card required
Your chase scene sprawls across pages, but the reader skims or closes the book. Midway through drafting, you see the words piling up—twists, turns, near-misses—but the tension fizzles. You're stuck because every lap feels like filler, and the protagonist's flight drags without forward momentum.
This hits when action dominates description over consequences. You focus on the physical scramble, forgetting what hangs in the balance, so the scene turns into a loop of repetitive motion instead of a pressure cooker.
Mid-draft, it's fixable. Spot the bloat, tighten the beats, and ramp the costs to make every second count.
Signs You Have This Problem
- Protagonist dodges the same obstacle type three times (alleys, doors, cars) with no variation.
- Scene exceeds 1,500 words but advances plot by less than one minute in story time.
- Reader feedback notes 'repetitive' or 'lost interest halfway through.'
- Pursuer's actions repeat: gains ground, then slips back, gains ground again.
- No new information or character revelation emerges during the pursuit.
- Environment details overwhelm: every street sign, puddle, or shadow described.
- Chase ends abruptly without payoff, like capture or escape feeling unearned.
Why It Happens
Chase scenes drag because writers treat them as pure motion, stringing physical actions without escalating costs. You map a route—protagonist runs, hides, sprints—and fill gaps with sensory details to hit word count. But motion alone loops; without rising pressure, it reads like a treadmill.
The root is flat stakes. Early in the draft, you set up 'must escape' but forget to layer immediate losses: a sprained ankle costs mobility, ditching a weapon costs defense, or a bystander spotted costs allies. Repetition creeps in from mimicking movie chases, where visuals carry the load, but prose demands tighter progression.
Mid-draft blindness worsens it. You're deep in the sequence, so equal weight lands on every beat, flattening urgency. Without a tracker for pace and stakes, the scene bloats before you notice.
How to Fix It
- Map beats to a 5-phase arc. Break into pursuit (hook with close call), escalation (obstacle forces choice), complication (pursuer adapts), climax (highest risk), resolution (win/loss with cost). Limit to 800-1,200 words total.
- Escalate stakes every phase. Phase 1: lose phone. Phase 2: twist ankle. Phase 3: pursuer calls backup. Phase 4: cornered, reveal secret. Tie each to character goal or flaw.
- Prune repetitive motion. Cut duplicate actions (no second identical dodge). Replace with decisions: barricade door (buys 10 seconds but blocks exit) or leap fence (faster but exposes position).
- Shift POV to consequences. Intersperse 1-2 sentences per paragraph on internal fallout—what failing means (family endangered, mission blown)—not just external scenery.
- Test read-aloud pace. Time it: aim for 2-3 minutes aloud. Slash any beat that doesn't spike heart rate or force a page turn.
Common Questions
How long should a chase scene be?
400-1,200 words max. Shorter for interpersonal chases (foot pursuit); longer only if stakes compound every 200 words.
Foot chase or car chase—does it matter?
Both drag without stakes escalation. Cars allow vehicle-specific costs (crash risks, fuel gauge); feet demand body limits (lungs burning, muscle failure).
What if the chase must span chapters?
End chapter one on a micro-cliffhanger (trapped in alley), cut to pursuer's view or consequence in next, resume with new phase. Never continuous prose.
Fix It Faster With StoryDev
StoryDev's pacing and stakes tracker maps your chase beats, flags drags mid-draft, and suggests escalations to keep action tight and propulsive.
Try StoryDev Free →