Sprite Sheet
Cutter

Columns are vertical divisions and Rows are horizontal divisions. Their product is the expected frame count. A grid with eight columns and two rows contains sixteen cells even if some cells are transparent. The sprite sheet cutter deliberately preserves empty cells because an empty slot may carry timing or indexing meaning in an existing animation table.

Frame Width and Frame Height describe the exported rectangle, not the visible character bounds. A 64 by 64 frame can contain a 40-pixel-tall character positioned on a consistent baseline. Cropping every pose to its nontransparent pixels would create different frame sizes and make animation alignment harder. Use a sprite extractor that keeps the authored cells when the sheet already has stable alignment.

Offset X begins the first cell that many pixels from the left edge. Offset Y begins it below the top edge. Spacing X is skipped after every cell except the last column, and Spacing Y is skipped after every cell except the last row. The overlay reflects all four values, so an advanced spritesheet cutter workflow remains visual rather than relying on arithmetic alone.

The grid is valid only when all configured rectangles fit inside the source image. A mismatch warning means the last row or column would extend beyond the source or the inferred equal division leaves a fractional pixel. Do not export through that warning. Correct the frame size, row count, column count, gutter, or offset until the full grid is contained.

Start with information from the artist or engine importer. A filename such as run_8x1_96.png may indicate eight columns, one row, and 96-pixel cells. Otherwise divide the source dimensions by likely counts and check visible repetition.

Transparent padding inside a cell and spacing between cells are different. Internal padding travels with the exported frame and maintains alignment. Grid spacing is discarded by the sprite sheet cutter. Outer transparent margin should be represented by Offset X and Offset Y only when it sits before the first cell; a symmetric margin on every cell is normally part of the frame itself.

Texture bleeding happens when a renderer samples colors just outside a cell, especially with linear filtering, mipmaps, scaling, or atlases. Existing spacing can protect the source sheet, but extracted standalone PNG frames do not need that gutter. If you repack them with the homepage maker, add the spacing required by the destination engine and preserve a stable cell size.

Horizontal and vertical strips are the simplest case. Use one row for a horizontal strip and one column for a vertical strip. The same sprite cutter engine handles both because cell positions are derived from grid geometry. Preview numbering still makes sequence direction explicit before the files are used in an animator or GIF encoder.

Auto Detect scans transparent columns and rows to look for regular gutters. It works best when every column contains visible pixels, every row contains visible pixels, and the empty separators have consistent width. That pattern is common in clean character sheets and effect grids exported with transparent gaps. When confident, the tool fills rows, columns, frame dimensions, offsets, and spacing, then asks you to review the overlay.

Detection becomes ambiguous when sprites overlap the conceptual cell edge, a background is opaque, some rows are completely empty, or internal transparent gaps resemble real gutters. Irregularly packed texture atlases are not regular sprite sheets and cannot be solved by rows and columns alone. In those cases the sprite sheet cutter says auto detection is uncertain and keeps manual control visible.

An uncertain result is safer than a confident but wrong grid. One-pixel shifts can clip a weapon, introduce a neighbor, or move every baseline. Inspect the first and last cell in each row, because an incorrect spacing value often accumulates and becomes more obvious toward the right or bottom edge. Zoom the browser if a pixel boundary is hard to see.

After extraction, open the sequence in the Sprite Sheet Animator. Movement exposes mistakes that static thumbnails hide: a clipped outline flashes, a borrowed pixel appears intermittently, or an incorrect frame order causes a jump. The sprite sheet cutter and animator are separate tools so cutting stays precise while playback stays fast.