Animation Preview
Play the sheet back before you export it. Set the FPS, step frame by frame, and find the pose that reads wrong.

Catch it here, not in the engine
The sprite sheet preview sits next to the canvas and loops your frames at the FPS you set. Pause it and step one frame at a time when something looks off. Every visible layer is stacked into the preview, and recolor slider changes show up live, so you judge the sprite animation as it will look rather than as a grid of stills.
Speed slider
1 to 60 frames per second. Drag it while the loop runs until the walk stops looking like a shuffle.
Frame stepping
Pause, then step forward or back, or drag the frame slider. This is how you find the frame that is two pixels off.
Visible frames
Untick a frame and playback skips it while the sheet keeps it. Test a six-frame cut of an eight-frame run without deleting anything.
Onion skinning
Up to three frames either side as tinted ghosts, warm for earlier and cool for later, with adjustable opacity.
Compare sprites
Lay all frames over each other at once to see the full arc of a swing or a jump.
Zoom and pixel perfect
Zoom from 0.5x to 10x, with pixel-perfect rendering on so edges stay sharp instead of blurring.
A grid of poses tells you nothing about motion
Every frame in a sheet can be correct on its own while the animation is broken. Timing, spacing and frame order belong to the sequence, not to any single image, so a static layout hides them. You have to watch the frames play.
Checking that in a game engine means an import, a resource setup, an animation node and a run, and then doing it again after every change. Playing the sheet where you built it cuts that loop down to a glance: change a frame, watch, change it again.
Set the preview to the engine rate
The number that matters is the one your game will use. A loop previewed at 24 FPS and played at 10 in game is a loop you have not actually seen. Set the slider to the project rate first, then judge.
Dragging the slider while the loop runs is still useful when the rate is not decided yet. A walk that shuffles at 6 and jogs at 16 has a right answer in between, and you find it by watching rather than calculating. The pixel art animation guide has typical rates for idles, walks and attacks.
The faults a loop shows and a still frame hides
A pop is one frame that does not belong: a pixel too bright, a limb in the wrong place, flashing once every cycle. At speed you see the flicker but not the cause. Pause and step frame by frame to find which one.
What else to look for
- Drift: a character that creeps across the cell over a loop that should stay put. Onion skinning shows it, because the planted foot stops lining up with its ghost.
- Uneven spacing: two nearly identical frames followed by one that jumps, so a smooth swing stutters.
- The seam between the last frame and the first. It is the one transition an artist never sees while drawing in order.
Unticking frames is the cheap way to test a shorter cycle. Hide the two weakest frames of an eight-frame run and watch the six-frame version straight away. Keep it if it reads better and delete those frames for real; tick them back on if it does not.
Uniform timing is a starting point
The preview gives every frame the same duration. Good animation usually holds on the extremes and moves quickly through the middle, so an attack that lingers on the wind-up and the follow-through reads better than the same frames at even spacing.
You can test that here by duplicating the frames that should hold: a two-frame hold is the same frame twice. Once the timing feels right, move it into the engine as per-frame durations (Godot SpriteFrames, Unity keyframes, Phaser frame configs) and delete the copies, so the sheet does not pay texture memory for repeats.
More questions? See the full FAQ.
Preview your animations
Set the rate your game uses, step through the loop, fix the frame that pops.
Open the editor