Why living things move in curves
Hand-drawn animation has a signature failure, and it is the straight line. A hand that travels in a perfectly straight path from A to B, a head that slides sideways, a ball that rises and falls along two straight diagonals — each of these reads instantly as wrong, even to viewers who have never thought about animation in their lives.
The reason is mechanical. Living bodies move by rotating segments around joints, and a point on a rotating segment traces an arc. Thrown and falling objects are pulled by a constant force while travelling sideways, which also produces a curve. Straight-line motion requires either a rail or a continuous correction, and in the natural world almost nothing has either.
Joints are hinges, so paths are arcs
Work out which joint is driving a movement and the arc draws itself. If the elbow is locked and the shoulder is doing the work, the hand sweeps a wide arc centred on the shoulder. If the shoulder is still and the elbow bends, the hand sweeps a tighter arc centred on the elbow. Most real reaches use both at once, which produces a compound curve that flattens as the arm extends — and that flattening is a large part of what makes a reach look intentional rather than robotic.
That diagram is worth sitting with, because it shows arcs and spacing arriving together. A pendulum is slowest at the top of its swing and fastest at the bottom, so placing frames evenly in time along a circular path automatically gives you the ease in and ease out described in timing vs spacing. Many motions you would otherwise have to hand-tune for spacing come out right simply by respecting the pivot.
The same move, straight and arced
Below is a thrown object travelling from the lower left to the upper right. Both versions start and end in the same place and use the same number of frames. The first follows the direct path; the second follows an arc.
The difference costs nothing. You are not adding drawings or changing the duration — you are moving each in-between a few pixels off the line. This is the highest ratio of improvement to effort available anywhere in frame-by-frame animation.
Finding the arc before you draw
The arc has to be a decision, not something you hope emerges. The order of work matters: extremes first, then the path, then the breakdown on the path, then the in-betweens.
- 1Draw the two extremesPut the start and end poses down first. Do not draw anything in between yet — the path has to be decided before the frames that follow it exist.
- 2Identify the pivotFind the joint the moving part rotates around. A hand pivots at the shoulder if the arm is straight, at the elbow if the upper arm is still, and often at both at once.
- 3Sketch the path on a guide layerOn a separate layer, draw the curve the moving point will travel along, from its position in the first extreme to its position in the last. Make it a genuine arc, not a bent straight line.
- 4Place the breakdown on the curveDraw the middle frame with the moving part sitting on the guide, off the straight line between the two extremes. This single frame is what makes the path read as curved.
- 5Fill the in-betweens along the guideDraw the remaining frames with the moving point landing on the curve each time. Vary the gaps along it so the action has spacing as well as a path.
- 6Delete the guide layer and play it backHide or remove the guide, then play the animation at your target frame rate. If any frame pops, it has drifted off the arc — fix that drawing rather than its neighbours.
The guide layer is the key practical trick. Drawing the path once as a visible line means every subsequent frame has something concrete to land on, and you are no longer eyeballing a curve from memory across a dozen drawings. When the sequence is finished the guide layer is deleted or hidden, and nothing about it appears in the export.
When straight lines are correct
Arcs are the default, not a law. A straight path is right whenever the thing moving genuinely has no pivot and no sideways force acting on it:
- Free fall with no horizontal motion. Something dropped straight down travels in a straight line, accelerating. The path is straight; the spacing is not.
- Machinery on rails. Pistons, lifts, sliding doors, conveyor belts. Their straightness is exactly what makes them read as machines.
- Interface elements. A cursor, a progress bar, a panel sliding in. These are not pretending to be physical objects.
- Projectiles over short distances. A bullet or a laser covers its distance before gravity has time to curve it meaningfully.
- Deliberate stylisation. Sharp, linear motion is a legitimate graphic choice — but it only reads as a choice when the rest of the shot shows you can do arcs.
Breaking the arc for impact
Having established the arc, breaking it becomes a tool. An arc that is travelling smoothly and then changes direction sharply reads as a collision, because an instant change of direction implies an instant application of force.
Two arcs meeting at an angle, with no smooth drawing bridging them, is how an impact is drawn. If you round that corner off with an in-between, the force disappears — which is the single most common reason a bounce looks soft. This is covered in practice in the bouncing ball tutorial, where the contact frame deliberately has no smoothing around it.
Checking arcs in FrameAnim
Arcs are hard to judge one drawing at a time and obvious when you can see several at once, which makes onion skinning the right tool for the job. Turn it on with O and raise the number of previous frames shown until you can see the whole sweep of the move as a row of ghosts.
One stray drawing is enough to break the illusion, and it will always look like a timing problem when it is actually a path problem. If a move pops at a specific frame, check that frame's position against its neighbours before you touch anything else.
Common mistakes
- In-betweening on the straight line. Placing each drawing halfway between its neighbours flattens any arc you planned. The middle drawing must sit off the chord.
- Arcs with a visible corner. A path made of two straight segments is not an arc. If you can see where the bend happens, it needs more curvature spread over more frames.
- Limbs that change length along the arc. Usually means the pivot moved. Mark the joint on your guide layer and measure against it.
- Smoothing an impact. Rounding the corner where two arcs meet removes the force from the collision.
- Giving everything the same arc. A hand, an elbow and a shoulder rotate around different pivots at different radii, so their paths should not be parallel.
- Checking the arc only at the end. By then every in-between is already drawn. Plan the path before you fill the gaps.
Where to go next
Arcs and spacing are the two halves of a motion path: where the drawings go, and how far apart they sit. Read timing vs spacing for the second half, then put both to work in the bouncing ball tutorial.
Trailing parts follow arcs too, which is why follow through and overlapping action is the natural next principle. For the longest practical arc exercise there is, the hips, hands and feet of a walk cycle all trace curves on a very tight frame budget.