Idle animation timing, measured on 127 official Spine animations
An idle is what a character plays while it is not doing anything else: too much motion reads as nervous, too little as a still image. Instead of guessing, we counted what the animators of the official Spine examples actually did.
What was measured
The sample is the JSON exports we took from the examples/ folder of the official spine-runtimes repository, branch 4.2: 26 skeletons, 127 animations and about 18,000 keys — spineboy, raptor, owl, goblins, hero, windmill and the rest. For each animation we took the time and value of every key, the curve on it, the range of values per timeline, whether the cycle closes, and the phase between paired bones. Bone roles (leg, arm, torso, head, secondary) were assigned from bone names, so the numbers below are rough tendencies, not a verdict on one skeleton.
The grid is 30 frames per second
About 98% of the measured keys sit on multiples of 1/30 of a second, allowing for rounding in the export; only 39% land on a 24 fps grid. The coin stands out most, with about 38% of its keys off the grid — its timing probably follows the period of the spin rather than frames. The runtime accepts any fractional time, but a shared grid makes timing between animations and the moments of events easier to line up frame by frame. Below, a “frame” is 1/30 s.
How long an idle lasts
Idle loops in the sample run from 30 to 200 frames, that is 1 to 6.7 seconds: hero/idle is 30 frames, spineboy/idle 50, owl/idle 200. An idle is noticeably longer than a walk cycle of the same character — spineboy breathes over 50 frames and walks a cycle in 30.
Breathing does not have to be a whole multiple of the walk cycle; keeping the periods different helps avoid motions overlapping at the same moment every time.
Few keys, and fewer bones keyed
The median rotation timeline of an idle has 3.0 keys per second (2.4 to 4.3 between the quartiles). A run is 11.2 keys per second, a walk 5.5.
An idle also keys less of the rig: the median share of bones with keys of their own is about 31%, against about 54% in a walk or a run. Bones without keys still move with their parents, so this does not mean the rest of the figure is frozen on screen — but limiting which parts are animated, rather than moving the whole rig evenly, is a sound rule for an idle.
How far things move at rest
For each rotation timeline in an idle, the range is the difference between its largest and smallest key value; for translation, the larger of the X and Y ranges, in the export's units. Take the median as the starting point and the upper quartile as “energetic”:
| Bone role | Median, ° | Upper quartile, ° |
|---|---|---|
| Leg (thigh, shin, foot) | 14 | 29 |
| Arm (shoulder, forearm, hand) | 12 | 35 |
| Torso (spine, chest) | 4.6 | 8 |
| Head, neck | 4.1 | 12 |
| Secondary (hair, tail, cloth) | 8.5 | 17 |
| Bone role | Median, px | Upper quartile, px |
|---|---|---|
| Hips | 6.9 | 16 |
| Torso | 5.4 | 8 |
| Head | 2.9 | 11 |
Rest is built from micro-motion: single degrees and single pixels. In a walk the head moves little (8.9° against 79° for a leg); in an idle the torso moves little, so light parts such as hair stand out by comparison. In spineboy/idle the hair moves through 16.7° while the torso moves through 3.8°.
Loops close, and a key at zero holds the pose
Among bone rotation, translation, scale and shear timelines with more than one key and a last key at the end of the animation, 85.5% end on nearly the values they start with. An idle is a loop: its last key repeats the first, or the seam shows as a jerk every cycle.
About 86% of the bone rotation, translation, scale and shear timelines counted have a key at time zero. Without it a bone keeps the pose of the previous animation while the two are mixed. A timeline of a single key is legitimate too — the whole sample has 872 of them: it says “in this animation, hold this value”.
Curves: fewer than you would think
Counting only keys that have a next key, 53.2% are linear, 43.1% Bezier and 3.7% stepped. Normalized to the segment between two keys, the medians of the control coordinates (cx1, cy1, cx2, cy2) are (0.31, 0.00, 0.70, 1.00) — an S-curve that eases out of one key and into the next. The editor preset (0.25, 0, 0.75, 1) alone accounts for 17.7% of Bezier uses.
As a rule of thumb, ease goes on parts that should feel heavy — torso, head, arms — and fast parts can stay linear. In an idle that means the breathing torso eases, while a flicker keyed every few frames works fine with linear interpolation. How the curve is written in the file is covered in Spine 4.2 Bezier curves in JSON, explained, and the curve converter turns a CSS easing into that array.
Stagger the key times between bones
Counting the distinct sets of key times in each animation and summing them gives about 57% of the number of timelines. The keys gather at the start, the middle and the end of a cycle, and are spread almost evenly everywhere else — there is no “key every quarter” grid. The seven leaves of owl/idle share a period of 20 frames but sit at three phases, shifted by 0, 5 and 10 frames; the foliage of windmill keeps one range while its period wanders by 10 to 15%. Keys on the same frames for every bone make the whole figure stop and start at once, which tends to look mechanical.
Where these numbers go
Riggy's AI reads these rules as a reference before it sets keys, instead of guessing lengths and ranges. The examples show what comes out: rigs animated from one sentence, playing in the official runtime.