Create 2D sprites for your game

1. STEP 1

   Keep a working editor and choose one sprite

   Use a copy or test branch of your existing game. Choose one small token or original character silhouette. Record engine/version, target, supported PNG importer and intended sprite size. Keep the placeholder’s movement and collision.

   Keep your current editor if it already exports the files you need. Krita is a free painting/frame-animation option. Aseprite adds a pixel-focused palette/frame/tag workflow and convenient paid binaries. Its own-use source route needs a toolchain; the trial cannot save. Packing existing frames alone does not require buying an editor.

   Check: One safe test project and one small art task.

2. STEP 2

   Draw and keep the editable source

   Create a 32 × 32 transparent document in Aseprite and draw your own simple shape on a paint layer. Use a consistent ground line/anchor. Hide or remove the opaque background layer in the exported copy; check the transparent area rather than trusting a white preview.

   Save token-source.aseprite with File → Save; keep layers and frames in the native file. Export one transparent PNG first and test its size/appearance in the game before animating.

   Check: An editable master and one transparent PNG are saved.

3. STEP 3

   Export a short PNG sequence

   Create four equal-size poses for one small pulse or idle change. Record the source frame range and timing; duplicate unchanged held frames when you need an evenly timed sequence.

   In Aseprite 1.3 use File → Export → Export As and a numbered name such as token001.png for the sequence. Select the intended frames and preserve original scale. The documented File → Export Sprite Sheet route is an alternative when your importer supports that output; do not repack a working sheet unnecessarily.

   Check: The sequence has the intended frame count, dimensions, order, alpha and holds.

   

4. STEP 4

   Pack only when needed

   Open Sprite Sheet Maker, choose the exported PNG frames and use Move earlier / Move later to set their order. Choose Preserve original pixels, 4 columns, 0 padding/spacing and 8 FPS for four evenly timed 125 ms frames. Change these example values to your recorded source timing.

   Keep Nearest-neighbour / pixel art for pixel artwork; turn it off when smooth painting needs that preview. Mixed sizes require an explicit Pad or Resize choice; Pad retains pixels while Resize changes them. Preview, pause, reorder and replay before downloading PNG and JSON together. Frames stay in this browser tab; no account or upload is required. Forge records one global FPS: variable frame durations need repeated frames or importer-specific timing, not a false exact transfer.

   Check: Order, alpha and timing are checked and both export files are saved.

   

5. STEP 5

   Import, run and keep the result

   Import one sprite/sheet into your current engine’s test scene using its documented texture/sprite workflow. Match cell size, frame order, anchor and scale. Keep collision separate. Forge JSON contains cells/pixel rectangles/order/FPS; Aseprite JSON uses a different schema. Native KRA/ASEPRITE masters are not universal game import files.

   Run two consecutive starts. Check still appearance, looping, pause/resume, restart and your actual target build. Record editor/engine versions and observed failures. Keep the original source, final exports, export settings and rights notes once the test passes. If alpha is black, use PNG frames; if speed changed, check holds/FPS; if edges blur, check importer filtering. Avoid replacing working game systems while fixing art.

   Check: Actual engine/target results are recorded; remaining tests stay explicit.

   

Try the separately tested five-frame CC0 example · Make your game animations better · Create a 3D prop instead