Find the task that matches
One regular sheet needs separate PNG frames
Split the original 64×32 sheet into eight 16×16 frames. Declare cell size, margins and gaps; use an explicit range when needed. Inspect each crop and keep the source-frame indices in the downloaded manifest.
Split a sprite sheet into individual PNG frames →Separate PNG frames need one ordered sheet
Arrange eight frames into a four-column 64×32 sheet. Compare natural, lexical and manual order. Use strict sizes for equal frames or explicit transparent padding for mixed dimensions; the maker does not resize them.
Make a sprite sheet from ordered PNG frames →A long strip needs several shorter rows
Split the 192×16 strip into twelve 16×16 frames, then pass those actual downloads to the maker. Four columns produce a 64×48 sheet. Keep both manifests so the source cells and destination rectangles remain traceable.
Reflow a long sprite strip into a multi-row sheet →Source margins or gaps shift otherwise valid grid cuts
Use known source offsets and gutters to locate each cell; compare a valid-but-wrong declaration with the intended crop.
Fix shifted sprite-sheet crops with exact margins and gaps →Names and manual order no longer identify the right frame
Keep original selection indices, Unicode-safe aliases and output positions together, then inspect every placed frame marker.
Keep sprite frame identity across filenames and manual order →Regular cells need transparent separation
Declare the original margins and gaps, add 2 pixels per side, and verify the four 6×4 content rectangles inside the 20×16 output.
Add transparent gutters to a regular sprite sheet →Cell edges need copied pixels rather than empty padding
Compare transparent padding with extrusion 1 and 2, inspect every copied edge/corner and keep finite sampling tests separate from GPU claims.
Extrude sprite edges and test the limits of bleed prevention →Known margins and gaps should be removed
Feed the actual padded download back into the tool with zero output padding; recover its 12×8 content and keep both geometry manifests.
Remove known margins and gaps from a sprite sheet →Independent tight crops introduce extra animation movement
Use one shared 9×8 crop and offset for all four 16×12 frames, build a 36×8 sheet from the actual downloads and preserve the empty dwell.
Trim animation frames without introducing position jitter →
Keep each diagnosis separate
The padding and extrusion tool retains declared cells; the transparent-border trimmer retains recorded offsets. Their original geometry project keeps Node references separate from the actual browser figures.
Try the sprite sheet splitter for one regular static PNG, or the sprite sheet maker for separate frames. Download the original CC0 sprite-grid project for all three walkthroughs. Its Node runner produces reference images; the examples below are separate actual browser exports.
The split example's first 16×16 frame and eight-frame manifest show the crop mapping. The two sheets below are retained browser downloads, with their saved geometry manifests.
These tools use declared regular cells and explicit frame order. They do not infer animation timing, tags, pivots, rotated regions or an engine's import settings. An incomplete grid or unequal strict-mode frames requires a corrected declaration or a deliberate padding choice.
Browser image decoding and PNG export can round partial-alpha colors, discard hidden RGB and omit metadata. Keep originals when those details matter. Geometry manifests describe the exported layout; they are not engine-specific animation files. Enlarging a PNG is a separate task and does not repair a wrong crop or order.