A walk cycle is usually the first real animation people attempt in pixel art, and for good reason — it's short, it loops, and it teaches the two things every other animation depends on: timing and weight. The good news is that a convincing walk needs far fewer frames than it looks like it should.
The Four Key Poses
Most walk cycles, at their simplest, come down to four poses repeated on both legs:
- Contact — the front foot has just touched the ground, legs are furthest apart. This is the pose people recognize as "walking" from a single still frame.
- Down — weight is fully loaded onto the front leg, the body dips slightly lower than its resting height.
- Passing — the moving leg swings past the planted leg, body at its highest point in the cycle.
- Up — the moving leg is about to become the new contact pose, body still elevated.
A full cycle is these four poses, then the same four again with the legs swapped — eight frames total, back to the starting pose. That's the classic, professional-feeling walk cycle. It's also more than most sprite work actually needs.
You Can Get Away With Fewer Frames
For small sprites — the kind you'd draw at 16×16 or 32×32 — a lot of the subtlety in an 8-frame cycle simply doesn't read at that size. A 4-frame cycle (contact, passing, contact-opposite-leg, passing-opposite-leg) reads perfectly well for most 2D games, and it's a much smaller time investment while you're still learning the shapes. Save the full 8-frame version for a hero character or a cutscene where the extra polish is actually going to be seen.
Timing Matters More Than Frame Count
A walk cycle that uses the right four poses but plays back at the wrong speed still looks wrong. As a starting point, 8–12 FPS reads as a normal walking pace for a small sprite; push it to 14–16 FPS and it starts to read as jogging. It's worth exporting a quick test GIF and watching it at actual size before committing to more frames — problems that are invisible frame-by-frame are usually obvious once it's moving.
Common Mistakes
- No vertical bob. The body should rise slightly during the passing pose and dip during contact/down. A walk with a perfectly flat head-height looks like gliding, not walking.
- Arms moving with the same-side leg. Arms and legs alternate — right arm forward pairs with left leg forward. This is the single most common thing that makes a walk cycle look subtly "off" even when the viewer can't say why.
- Identical left and right steps. Very few real walks are perfectly symmetrical. A tiny bit of asymmetry between the two halves of the cycle often looks more natural than a mirrored copy-paste.
Building It in Pixelsito
Start with the contact pose on frame 1 and get the silhouette right before worrying about color or shading — a walk cycle lives or dies on its poses, not its palette. From there:
- Add a new frame and turn on onion skinning so the previous pose stays faintly visible while you draw the next one — this makes it much easier to judge how far a limb should move between poses.
- Draw the remaining three (or seven) poses, using the timeline to jump back and check spacing against earlier frames.
- Set the frame rate in the animation panel and use the live preview to watch it loop before exporting.
- Export as an animated GIF to share or preview it, or as a spritesheet if it's going into a game engine.
If you're new to the animation tools specifically, the User Guide covers the timeline, onion skinning, and frame tagging in more detail.
Ready to try it?
Open the Editor