Why I use a runcam to review my trail running technique
Years ago, I finished a hilly trail race in the Blue Mountains and felt reasonably pleased. The following morning, footage from my chest-mounted runcam showed a tired runner: shortened stride, rising shoulders, and a forward collapse on the descents. I had felt “strong enough”; the video showed what my body was actually doing. That gap is why I still use a runcam. It gives me visual evidence to question my technique, especially when effort and terrain have pushed my form off balance.
The camera is not a coach, nor is it the final word on good running. I use it to spot patterns, compare similar sections, and choose one small experiment for the next outing. In Australia, where a trail can combine sandstone steps, eucalyptus shade, coastal humidity, and a sudden rise in temperature, that evidence is useful. The aim is not to chase a perfect stride. It is to run with less waste, better control, and more confidence over distance.
The details I miss while running
While running, I can sense cadence or heavy steps, but I rarely notice small changes in arm swing, trunk angle, or where my feet land. The runcam slows that movement down. Watching ten seconds repeatedly can reveal that my hands are drifting inward, my head lifts when the trail rolls, or I am braking with each foot before a technical section.
I treat patterns rather than single frames as evidence. One awkward landing may be a rock. Three similar clips on the same downhill may be a habit worth changing. Comparing a fresh morning run with one taken near the end of a long effort also shows how fatigue alters my mechanics.
This feedback has changed my priorities. Instead of trying to alter everything at once, I look for the fault that repeats and costs the most energy. That might be an overstriding stride on a descent, a rigid arm position, or tension that builds through my shoulders.
Where the footage changes my decisions
Video is most useful when it answers a specific question. Before a race, I might ask whether my cadence becomes slow and heavy on loose ground. During training, I can check whether an easy effort really stays controlled on a climb. On technical trails, footage helps me judge whether my feet are landing close enough to my centre of mass.
It also improves my pacing decisions. If I see myself repeatedly braking downhill, the answer may be a steadier effort rather than simply more courage. If my stride shortens sharply after an aid station, I can compare that section with the first hour and decide whether the issue is fatigue, heat, or an unnecessarily tense pace.
That habit of examining effort rather than chasing a highlight reel fits the spirit of endurance stories. Race reports are most valuable when they expose what worked and what failed, not merely when they produce dramatic footage. The same standard applies to my own clips.
Australian trails give harsh feedback
The Blue Mountains around Mount Victoria expose poor timing quickly. Sandstone can shift underfoot, roots cross narrow tracks, and a steep descent turns braking into a full-body movement. The damp coastal trails around Sydney add another variable: humidity makes a technical surface look stable while the same section becomes slippery and less forgiving in the heat.
Canberra’s Stromlo Forest Park offers a different test. Winter runs can begin with frost and low light, while exposed ridges become bright and harsh by midday. In the Dandenong Ranges, wet clay and rock create exactly the uneven footing where a long stride and late braking fail. These places punish an imported running habit very clearly.
Australian trail culture adds a practical layer. The scene is a patchwork of club-run events, local trail series, and volunteer-supported charity races, with registration usually handled through each organiser’s event page rather than one central marketplace. Club races often rely on volunteers, homemade aid-station support, and runners gathering at the start with a bacon-and-egg roll in hand. People may call a course “properly brutal” with affection, but the local saying does not soften the lesson. A camera that survives one outing must handle dust, sweat, rain, and the need to keep moving when the battery indicator is the only warning.
The limits of a chest-mounted camera
A runcam changes the angle, not the truth. A bouncing strap, wide lens, low chest mount, or camera pointing towards my feet can distort posture and foot placement. It also cannot measure joint load, ground reaction force, or why a movement feels comfortable. I use the footage to guide questions, not diagnose injury.
Wearing a camera can also change how I run. Some outings feel freer because I am not checking a screen, while others make me self-conscious and overly smooth. That observation matters more than the image quality. If the camera makes me tense, it is poor training equipment for that session.
Privacy and courtesy deserve attention on busy tracks. I avoid publishing clear close-ups of nearby runners without permission, and I do not film where it could obstruct someone or create safety issues. A small action camera is useful only if it does not compromise my pace, other people’s privacy, or trail etiquette.
A practical recording and review routine
My setup is deliberately plain: a stable chest mount, a charged battery, enough storage, and a lens cloth for dusty tracks. I check the framing with a short walk, record a little at the start, and confirm that the controls do not need attention once the run gets serious. For longer efforts, I reduce screen brightness and carry a small power bank when practical.
Review takes less time when the recording has a purpose. I first note the route, effort, weather, and any pain, because the same movement can look different on dry rock, mud, or a steep climb. Then I choose one section and inspect it frame by frame, comparing it with footage from another day rather than an idealised clip from somewhere else.
Before the run
- Pick one technique question, such as downhill braking or arm tension.
- Secure the chest mount and check the camera angle.
- Charge the battery, clear storage, and note the route conditions.
- Keep the recording brief unless the session specifically needs more.
After the run
- Watch two or three comparable sections before making any judgement.
- Record repeated patterns, not one unusual moment.
- Choose one small adjustment for the next similar run.
- Save the clip with notes about terrain, effort, and fatigue.
Turning evidence into better runs
The useful outcome is not a cinematic running video. It is a better decision on the next trail. When footage shows that I am landing late and braking, I might shorten my stride slightly and increase cadence on the next descent. When my shoulders are visibly tight, I can test a simpler arm swing. I give each change several runs before deciding whether it helps.
I also compare what the camera shows with how the effort felt. A pattern that looks inefficient may be an appropriate response to rough ground; a technically tidy movement may still feel uncomfortable. Heart rate, terrain, and accumulated fatigue provide context that a frame cannot. The evidence becomes useful only when the pieces agree.
| Review point | Visual cue to check | Small experiment for the next run |
|---|---|---|
| Foot placement | Landing late, with visible braking before uneven ground | Shorten the stride and step closer to the trail |
| Arm swing | Hands drifting inward or shoulders rising | Let the arms swing freely and unclench the hands |
| Trunk position | Leaning forward more as fatigue builds | Keep the chest taller without forcing an upright posture |
| Head position | Chin tucked while watching the feet | Look 20 to 30 metres ahead for the next safe line |
| Cadence | With feet in frame, steps becoming slow and heavy | Keep the feet turning over rather than reaching forward |
This weekend, I am filming one easy loop from Mount Victoria, marking the three faults that repeat most, and testing only one correction on the following run before reviewing the comparison.