From a 4 4 AI VFX Sheet to 16 Reproducible Game Frames

An attractive VFX contact sheet is not automatically a usable game animation. The useful artifact is a sequence with an explicit contract that another developer can reproduce. For one current FrameSprite sample, that contract is: a 4×4 source sheet; sixteen frames in left-to-right, top-to-bottom order; a 512×512 canvas for every frame; transparent PNG output numbered 000–015; a one-second preview at 16 fps. Validate motion before export Reviewing sixteen thumbnails independently misses sequencing problems. I review the result as an onset, buildup, peak and decay. The exact phase boundaries can vary, but the sequence should not restart or reverse unexpectedly halfway through. Validate alpha separately A PNG can contain an alpha channel and still show a bright or dark halo in an engine. Preview the same frames on both light and dark backgrounds. RGB edge colors, premultiplication and the engine blend mode can produce different results even when the cutout looks clean in a browser. Keep the engine boundary honest The exported PNGs do not contain a Unity material, a Godot scene, a particle lifetime or a blend mode. They are lossless source frames. Those engine choices should remain explicit rather than being hidden behind a “game-ready” label. I published the original frame pack, measured dimensions and the complete workflow here: https://www.framesprite.com/guides/game-vfx-sprite-sheet-generator?utm_source=devto&utm_medium=technical_article&utm_campaign=vfx_16frames_20260827 Disclosure: I build FrameSprite. I would especially value reproducible feedback about the first engine/import combination you would test.