Free · No signup · Runs in your browser
Sprite Sheet Animator
Play any sheet at your own frame rate, step through frames one at a time, and catch the bug before your engine does.
Load a sheet, then press play.
Most sprite bugs are animation bugs, and most animation bugs are easier to see than to read. This tool plays a sprite sheet in your browser at whatever frame rate you choose, so you can check a walk cycle before it ever reaches your engine.
Load the sheet, set the frame width and height, pick the frames that belong to one animation, and press play. The frame counter under the preview tells you exactly which cell is on screen, which makes it easy to spot the frame that is one pixel too high or drawn facing the wrong way.
What to look for when it plays
- Jitter. A foot or shoulder that jumps up and down between frames means the frames were drawn on different canvases. Keep the character's anchor point in the same place in every frame.
- Pacing. A run cycle usually reads well at 8 to 12 frames per second. If it looks frantic at 10 fps, your frames are too dense, not your speed too high.
- Loop seams. The last frame has to flow into the first. Step through the end of the range frame by frame and watch for a pause or a pop.
- Missing frames. A blank cell inside your range is almost always a slicing error, not a drawing error. Check the frame size against the sheet.
How the controls work
- Frame size must match how the sheet was built. If the character is split in half, the width is too small.
- Padding and offset handle sheets with gaps between cells or a border around the edge.
- First and last frame limit playback to one animation inside a larger sheet. A sheet holding idle, walk and attack in three rows can be checked one row at a time.
- Speed sets the playback rate in frames per second. It changes the preview only; your engine stores its own animation speed.
- Zoom scales the preview up to 8× with nearest-neighbour sampling, so pixels stay square instead of blurring. Use it to check the alignment of single pixels.
- Prev and Next step one frame at a time while paused. This is the part that finds real mistakes — playback hides them.
Why check before importing
Once a sheet is sliced inside an engine, every frame carries engine settings as well as pixels. Fixing a jitter means going back to the drawing app, re-exporting, rebuilding the sheet and re-slicing. Doing that loop in a browser tab takes seconds; doing it in an engine project takes minutes, and it is the sort of thing that ends up deferred until launch week.
Where the numbers come from
If you built the sheet with our sprite sheet maker, the frame width, height and padding are in the meta block of the downloaded JSON. If someone else built it, the sprite sheet splitter can help you work out unknown values by looking at where the cut lines land on the art.
No upload, no account
The sheet is read locally by the browser, drawn to a canvas, and looped with requestAnimationFrame. Nothing is sent anywhere, and the preview keeps running with your network switched off.
Frequently asked questions
What frame rate should I use for a walk cycle?
Eight to twelve frames per second suits most pixel art walk cycles. Faster reads as a run, slower reads as a stagger. The setting here only affects the preview, so try a few values and note the one that looks right.
Can I preview only part of a sheet?
Yes. Set the first and last frame numbers and playback loops inside that range only. Each animation in a multi-row sheet can be checked separately.
Why does the preview show empty frames?
Either the frame width or height does not match the sheet, or your last-frame number goes past the number of cells that actually exist. Check the grid count in the status line.
Can I export a GIF or video from this?
Not yet. This tool is for checking frames, not for rendering files. Record the preview with a screen recorder if you need to share it.