A run cycle is the walk cycle’s louder sibling, and the difference is one thing: in a run, both feet leave the ground. That airborne moment changes everything about how you pose, time, and polish the cycle. This guide covers how to animate a run cycle in Maya: the key poses, the frame counts that read at 24fps, the body mechanics that separate a sprint from a jog, and how to use run cycle reference without copying it.
What makes a run a run
In a walk there is always at least one foot on the ground. In a run there is a stride phase where there are none: the character is airborne, a projectile between pushes. That means gravity, not the legs, controls the body’s path in the air, and your job is to make the launch and the landing believable. If a run looks wrong and you cannot say why, the answer is nearly always in the airborne spacing.
The key poses of a run cycle
- Contact. The front foot strikes, usually further under the body than in a walk, often on the ball of the foot rather than the heel. The body leans forward; the faster the run, the stronger the lean.
- Down. The planted leg compresses hard, the body hits its lowest point, and everything loaded in the landing is stored for the push. The down in a run is deeper and sharper than in a walk: this is where the impact reads.
- Push. The planted leg extends fully and fires the body up and forward. The push pose is the most energetic drawing in the cycle, and if it is weak the whole run dies.
- Airborne. Both feet off the ground, legs scissoring past each other, body at its highest. Hold nothing here: the body is decelerating upward and accelerating downward the entire time.
Run cycle timing and frames
Runs are fast. At 24 frames per second:
- 8 frames per stride (16 per cycle) is a standard run.
- 6 frames per stride is a sprint, and at this speed some poses exist for a single frame.
- 10 to 12 frames per stride is a jog.
With so few frames, every one carries real weight. A run cycle is often animated on ones, and it is normal for the contact and down to sit only a frame apart. Block contacts and pushes first, then place the airborne peak exactly halfway between push and the next contact.
The mechanics that sell it
- Forward lean. A runner falls forward and keeps catching themselves. An upright run reads as jogging on a treadmill.
- Deep compression. The landing leg bends far more than in a walk. Cheat it deeper than reality; at this speed subtlety vanishes.
- Arms drive, not dangle. Elbows bent near 90 degrees, pumping opposite the legs, hands tracing long arcs. In a sprint the arms are half the energy of the shot.
- The spine stretches and squashes. Extended in the air, compressed in the down. Keep the volume, change the shape.
- Head and chest stay on target. The body churns underneath, but a runner looks where they are going. Too much head bounce reads as flailing.
Common run cycle mistakes
- Floaty airtime. Even spacing in the airborne frames. The body must ease out of the push and accelerate into the landing, like any thrown object.
- No impact. A landing without a sharp down. If the character could be carrying a tray of drinks, the down is too soft.
- Walk poses at run speed. Speeding up a walk cycle does not make a run; the poses themselves are different, starting with the lean and the ball-of-foot contact.
- Symmetrical arms. Offset them a frame from the legs and from each other, exactly as in a walk.
Using run cycle reference
Runs are too fast to eyeball, so reference matters even more than for walks. Film a run from the side in open space, or pull sports footage where athletes run across frame, and step through it. Count the stride frames; you will find real sprints are faster than feel comfortable to animate, which is exactly why sprints are cheated with fewer, stronger poses. Study where the foot lands relative to the hips, how few frames the contact occupies, and how the head keeps almost level while everything else churns.
Practise on a rig built for it
Run cycles punish bad rigs: you need clean IK feet, a reliable spine, and controls that do not flip mid-stride. The free Maya rigs on Animworks are animation-ready and downloadable in seconds, so the hour goes into the run, not the rig. Start with a plain biped, and once your standard run works, try the same cycle on a heavier character; if the two runs look identical, the weight is not there yet.
If you already animate walks with confidence, a run cycle is the natural next reel piece, and the walk cycle guide covers the shared foundations. For professional eyes on your cycles, the Animworks mentors review shots one-to-one, with every session recorded.
Put a run on your reel
Pick an animation-ready rig from the Animworks free library and spend the session on the cycle, not the setup.
Browse the free Maya rigsRun cycle FAQ
How many frames is a run cycle?
A standard run is 16 frames for the full cycle at 24fps, 8 per stride. Sprints drop to 12 frames per cycle, jogs stretch to 20 or 24.
What is the difference between a walk cycle and a run cycle?
A walk always has a foot on the ground; a run has an airborne phase where neither foot touches. The run also adds forward lean, deeper compression on landing, and driving arms.
Should I animate a run on ones or twos?
At run speeds, ones. With only 6 to 8 frames per stride, animating on twos leaves too few drawings to carry the motion.
About Harvey Newman
I’m Harvey Newman, an Animation Director and game developer with over a decade of experience working across AAA and indie studios. I’ve contributed to titles like Star Wars Battlefront II, Battlefield V, Horizon Zero Dawn, and Dune Awakening, and I’ve spent a lot of time on both sides of the hiring process, creating animation and reviewing showreels. Alongside studio work, I run Anim.works and create courses, tools, and content focused on helping game animators understand what actually matters in production and recruitment. My approach is straightforward and experience-led, no fluff, just practical guidance based on how studios really work.
View all posts by Harvey Newman