The best practices for passing pedestrians on shared paths boil down to three core actions: announce your presence clearly with “On your left” or a bell, reduce your speed to match the situation, and always pass on the left side of the path while keeping pedestrians to the right. These simple rules, backed by both formal guidance from the Federal Highway Administration and the American Association of State Highway and Transportation Officials (AASHTO), have evolved from decades of real-world experience managing the growing conflicts between cyclists and pedestrians on multi-use trails.
Beyond the basic mechanics of passing, this article covers the regulatory landscape, equipment considerations, and the specific challenges posed by different path conditions and user types. Every year, approximately 60,000 pedestrians and 42,000 bicyclists are injured in roadway crashes, with the risks magnified on busy shared paths where speeds vary wildly and expectations aren’t always clear. The gap between what makes sense in theory and what works in practice is where most passing conflicts occur—and where safe cyclists build their skills.
Table of Contents
- What Does the AASHTO Standard Actually Say About Passing on Shared Paths?
- Speed Is the Real Control Variable Most Cyclists Overlook
- E-Bikes Present a Distinct Challenge You Can’t Ignore
- How to Execute a Safe Pass Without Creating Conflict
- The Low-Light Visibility Problem That’s Often Overlooked
- Accessibility and Path Width Constraints Are Real Limitations
- Looking Forward: Shared Path Culture Is Still Evolving
- Conclusion
What Does the AASHTO Standard Actually Say About Passing on Shared Paths?
The AASHTO Guide and Federal Highway Administration recommendations establish that all users should travel on the right side of shared use paths in each direction, with bicyclists passing pedestrians on the left. This directional separation is the foundation of path safety, but it only works when users actually follow it. The right-hand rule assumes a certain level of awareness and predictability, which doesn’t always exist on real trails where pedestrians might wander between earbuds in, or where uneven surfaces force sudden swerves. Centerline stripes play a critical role in reinforcing these expectations.
The FHWA recommends centerline markings on shared use paths to indicate directional separation and clarify when passing is permitted. Paths without centerlines create ambiguity—does each user have the entire width, or is there an understood middle? This uncertainty often leads to awkward standoffs where both a cyclist and pedestrian try to yield. Marked paths solve this by creating visual confirmation that the left side of the line is for passing. For extremely heavy-volume paths—think urban trails that feel like crowded sidewalks on weekends—AASHTO recommends separate lanes within a single path structure requiring a minimum width of 15 feet. Most shared paths aren’t this wide, which is why speed management and courtesy become essential rather than optional.

Speed Is the Real Control Variable Most Cyclists Overlook
Many cyclists assume that a quick “On your left!” warning gives them license to pass at near-full speed, but this misses the core principle: cyclists must reduce speed to appropriate levels for shared use conditions. On a wide, uncrowded path on a calm afternoon, that might mean slowing from 18 mph to 14 mph. On a narrow path crowded with walkers, strollers, and dogs, it might mean 5 mph or walking your bike entirely. The challenge is that pedestrians have reaction times and unpredictable behavior. A walker who hears your bell might jump left instead of right, directly into your intended path.
A parent might suddenly turn to attend to a child. These aren’t failures of pedestrian awareness—they’re just the reality of shared spaces. Cyclists who build in speed buffer account for this. However, some cyclists resist this approach, arguing it’s inefficient or that pedestrians should simply stay alert. This creates a reliability problem: you can’t build trail culture on an assumption that everyone will behave perfectly.
E-Bikes Present a Distinct Challenge You Can’t Ignore
E-bikes are faster and heavier than standard bicycles, requiring additional caution in crowded trail sections. A 50-pound e-bike at 25 mph carries significantly more momentum than a 25-pound road bike at the same speed, and the casual rider astride an e-bike often doesn’t have the handling skills of someone who chose a bicycle for active pedaling. This creates a mismatch between capability and user awareness that can be dangerous. Many e-bike riders discover they’ve exceeded their comfort zone only when they’re already moving fast and need to pass a cluster of pedestrians. The solution isn’t to ban e-bikes from shared paths—they’re legitimate users—but to approach passing with extra caution.
Some experienced cyclists slow to walking speed around heavy pedestrian traffic on an e-bike, then accelerate again once clear. This takes discipline but prevents the “I was going too fast to stop” scenarios that produce injuries. The regulatory landscape is beginning to catch up. In Washington State, for example, RCW 46.61.197 (as of 2025) allows local authorities to designate non-arterial highways as shared streets where vehicle traffic must yield right-of-way to pedestrians. Similar thinking about speed and right-of-way allocation is creeping into path design across the country.

How to Execute a Safe Pass Without Creating Conflict
The mechanics of a safe pass have four steps: first, recognize that passing is necessary; second, slow down before you’re close enough to alarm the pedestrian; third, announce yourself clearly from 20-30 feet away (not 5 feet); and fourth, complete the pass with steady, predictable movement. The clarity of your announcement matters more than its volume. “On your left!” said at conversation level from a reasonable distance is more effective than a loud shout from close behind. Different pedestrian types require different approaches. A walker in their 70s might be startled by a bicycle they didn’t hear clearly and might jump unpredictably, so announce earlier and pass more slowly. A young runner who obviously knows what a shared path is and is aware of their surroundings might need only a quick bell.
Parents with strollers are often tunnel-visioned on their kids, so announce louder. The comparison here is instructive: not all passes are created equal, and treating them identically creates unnecessary conflict. Some cyclists carry simple, clear bells rather than relying on voice. A quality bell that projects clearly is a useful backup, especially on paths where ambient noise or headphones limit verbal warnings. However, a bell alone without eye contact or verbal confirmation often isn’t enough. The strongest approach combines both announcement methods.
The Low-Light Visibility Problem That’s Often Overlooked
Seventy-six percent of pedestrian fatalities occur in low-light conditions, which includes dawn, dusk, and overcast days, not just nighttime. This statistic is often cited to warn pedestrians, but it applies equally to cyclists passing others. If a pedestrian can’t see you, they can’t reliably move out of the way when you announce yourself. Conversely, if you’re riding in low light and assume pedestrians see you coming, you’re building on a shaky assumption. Wear bright or reflective clothing in low-light conditions, and carry a flashlight or use reflective gear at night. This advice is straightforward, but many cyclists treat visibility gear as optional or something for serious commuters only.
On shared paths, visibility isn’t just about your own safety—it’s part of being a predictable, legible user to everyone around you. A cyclist in dark clothes against an evening sky blends into the background, making your bell warning seem to come from nowhere. Some paths in high-traffic areas have started installing better lighting, but most shared use paths are still unlit. The burden falls on the cyclist to make yourself visible. One practical limitation: the better your visibility, the more pedestrians will defer to you and move out of the way earlier. This actually makes passing easier, not harder.

Accessibility and Path Width Constraints Are Real Limitations
Not all shared paths are created equal, and narrow paths present specific challenges. Paths with clear width less than 60 inches require passing spaces of 60 inches minimum × 60 inches minimum at intervals of 200 feet maximum, according to U.S. Access Board standards. This means a path that’s 8 feet wide allows for passing, but one that’s 5 feet wide creates a difficult situation where pedestrians moving single-file leave no room for a bicycle to safely pass.
On these constrained paths, the only safe option is often to slow to a walk, make eye contact with the pedestrian, and ask politely if they’d be willing to step to the side briefly. This isn’t inefficient—it’s appropriate to the actual conditions. A cyclist who feels frustrated by having to walk on a 5-foot-wide path during busy hours is experiencing a legitimate conflict between their speed goals and the path’s design capacity. The path wasn’t built to accommodate 20 mph cyclists during peak use times, and no amount of technique will solve that fundamental problem.
Looking Forward: Shared Path Culture Is Still Evolving
The 2,381 bicycle and pedestrian fatalities in 2023 (1,166 bicyclists and 7,314 pedestrians killed in traffic crashes) aren’t all multi-use path incidents, but they underscore why path safety matters. Most conflicts on shared paths don’t result in serious injury—they result in startled people, awkward moments, and cyclists or pedestrians who feel the path isn’t safe for them. Over time, these minor incidents shape who uses the paths and who avoids them.
The future of shared paths likely includes smarter infrastructure: better lighting, clearer markings, wider designs in high-traffic corridors, and perhaps separated lanes where volume justifies it. Until that infrastructure exists, the responsibility falls on individual users—especially cyclists, who are typically the faster, more maneuverable, and therefore more controllable parties. Treating each pass as an opportunity to build good path culture, rather than just getting around someone, creates trails where both pedestrians and cyclists feel safe and respected.
Conclusion
Passing pedestrians safely on shared paths isn’t complicated, but it does require a shift in mindset from “I’m faster than you, move” to “I need to move through this space in a way that respects your presence and predictability.” The core practices are simple: announce clearly, slow down, pass on the left, and stay visible. But executing these practices consistently requires understanding that shared paths are shared precisely because they serve people with different speeds, abilities, and awareness levels.
The next time you’re on a busy shared path, observe how the safest, most respected cyclists operate: they slow well before they need to, they announce clearly from a distance, and they seem unhurried even when moving briskly. This doesn’t reflect a lack of bike skills—it reflects the recognition that on a shared path, being a good cyclist means being a good neighbor first. That approach makes the path safer for everyone and more pleasant for you, too.


