Frame count does not determine animation speed by itself. Eight drawings can form a quick hit, a relaxed walk, or a two-second idle. Timing comes from how long each drawing remains visible.
For a sequence where every frame has the same duration:
frame duration = 1 ÷ FPS
loop duration = frame count ÷ FPS
FPS = frame count ÷ target loop duration
A six-frame loop at 12 FPS lasts 0.5 seconds. At 6 FPS it lasts one second. You can then vary individual holds to give the action its rhythm.
Start with what the animation must communicate in the game.
Choose a rough duration, calculate an initial FPS with frame count ÷ duration, then preview the motion at game scale and adjust.
Do not add frames merely to make an animation “higher FPS.” More drawings can describe motion in finer steps, but playing identical poses faster changes duration without adding information. Likewise, doubling both the frame count and FPS can preserve the same loop duration.
A game may render at 60 frames per second while a sprite changes drawing at 8 or 12 FPS. The renderer can show the same sprite frame across several display updates.
This separation is normal. It lets deliberately stepped pixel animation keep its cadence while movement, input, and the camera update more frequently. Do not export duplicate artwork for every display frame unless the target system truly requires that representation.
Uniform timing is easy to configure, but it can flatten an action. A longer anticipation makes an attack readable. A short impact pose feels sharp. A pause at the top of a jump adds weight.
If the engine supports per-frame durations, keep one copy of each drawing and assign longer durations where needed. If it supports only one FPS, repeated frames can approximate a hold. At 10 FPS, one frame lasts about 100 milliseconds; repeating a pose three times holds it for about 300 milliseconds.
Use explicit duration data when your engine or animation format supports it. Repeated frames work as a fallback, but increase the frame count and make later edits harder.
Godot's SpriteFrames documentation defines frame duration as a relative value. At normal playback speed, a relative duration of 2 lasts twice as long as 1. The absolute duration also depends on animation FPS and the current playback speed; see AnimatedSprite2D's playback controls.
For a reproducible timing check, take four drawings with relative holds of 1, 2, 1, and 4. At 10 FPS and playback speed 1, they last 100, 200, 100, and 400 milliseconds: an 800-millisecond loop. Replacing them with four equal 100-millisecond frames cuts the loop to 400 milliseconds and loses the holds. This is a timing calculation; check the playback after setting those durations in Godot.
An animated GIF can store a different delay for each frame. Converting its pixels into a PNG sheet does not automatically embed those delays in the sheet.
The GIF to sprite sheet converter decodes the frames in the browser and previews them using the recovered per-frame delays. Compare that preview with the original GIF before choosing an engine timing model. The detailed GIF conversion guide explains how to translate variable delays into relative durations or repeated frames.
Sprite Sheet Tool's PNG and atlas JSON exports describe pixels and frame rectangles; they do not create an engine animation clip or store a timing track. Record the intended FPS and any special holds separately, then configure them in the destination engine.
When reviewing a loop, look beyond “too fast” or “too slow.” Ask:
The free sprite sheet editor previews separate images at 1–30 FPS and decoded GIF frames at their recorded delays. Use it to check cadence, then test in the game with movement, input and animation events running.
Suppose a four-frame walk should complete one loop in 0.8 seconds:
FPS = 4 frames ÷ 0.8 seconds = 5 FPS
Start at 5 FPS. If the character moves through the world during that loop, compare the foot contact frames with the distance traveled. Speeding the artwork to 8 FPS shortens the loop to 0.5 seconds; it does not by itself correct sliding. You may need to change movement speed, pose spacing, loop duration, or all three as one coordinated decision.
For an eight-frame attack that should last 0.4 seconds, a uniform starting point is 20 FPS. But if anticipation and recovery need more time than the strike, per-frame durations will usually express the action more clearly than forcing all eight drawings into identical 50-millisecond slots.
One FPS value is not enough when the sequence contains deliberate pauses, animation events, variable source delays, or gameplay-controlled holds. A charge pose might remain active until input is released. A terminal death frame may display indefinitely. Those are state-machine rules, not properties of the sprite sheet image.
Timing advice for loops also does not fully apply to one-shot effects. Judge those by total duration, readable phases, and what happens after the final frame. Do not add a duplicate first frame at the end unless the playback system or export format specifically needs it; many loop players already wrap from the last frame to the first.
Keep the timing notes beside the sheet: intended FPS, special holds and whether the action loops. When you import it, apply those notes to the animation data so the PNG can stay unchanged.

Understand outer padding, gaps, edge extrusion, and sampler settings so you can diagnose texture bleeding without breaking sprite sheet slicing.

Learn how canvas size, visible artwork, pivots, and grid math affect sprite frame dimensions before you pack an animation sheet.

A character reference sheet records a design. A sprite sheet contains game images. See how to turn an existing character into walking frames, or pack frames you already have.