QUICKUPSCALE

CHOOSE A WORKFLOW

Tilesets, animation and atlas handoff

Start with the next consumer of your image. Tiled needs the content tile size, margin, spacing and tile identity that belong to the sheet. A CSS strip needs frame positions and timing. Phaser needs the frame and animation metadata that belongs to its PNG. For the original GIF controls, use the native Python/Pillow recipes to retain raw timing or diagnose disposal. Choose the task that matches the handoff you need.

Find the task that matches

Keep each diagnosis separate

The Tiled tasks use native Tiled 1.12.2 save/reopen and native-size render checks. The extrusion task consumes the actual padding-tool PNG; a matching integer map does not establish GPU bleed prevention. Download the original extruded-tileset project and retain the actual tool manifest separately.

The CSS task includes a standalone HTML/CSS project. The T35/T36 Aseprite-to-Phaser tasks share an original editable source and pinned local Phaser project. T32 uses a separate original GIF and the Aseprite CLI to export complete PNG frames. Their native evidence uses the historical Aseprite 1.1.7-dev Linux CLI; T35/T36 also use Phaser 3.90.0 Canvas. These are recorded CLI workflows, not a current desktop editor walkthrough.

The GIF recipes require an existing Python environment with Pillow 12.3.0; the recorded native run used Python 3.14.8 on macOS ARM64. The sheet recipe covers ten named originals, and the disposal diagnostic accepts three named controls. These are controlled CLI recipes, not a browser GIF tool or proof of arbitrary GIF validity or player timing.

An enlarged PNG alone does not choose playback order or update atlas coordinates. Keep the exported metadata with its image, and read each task’s runtime and timing limits before applying it to another project.