Roblox opens AnimatedImage early access for 2D animation
Roblox opens AnimatedImage early access for Aseprite imports and animation playback. Test in standalone Studio files; publishing and Team Create are not supported.
Roblox launched limited AnimatedImage early access for developers building 2D games, according to its October 27, 2026 announcement. The program adds Aseprite imports and animation playback APIs, but remains Studio-only: developers can test through Play mode and Device Emulation, not publish games using these features.
What the workflow changes
Roblox says importing an Aseprite .ase file creates an AnimatedImage asset while preserving frames, named tracks and timing. AnimationPlayer handles playback on an ImageLabel, including track selection, speed and looping. AnimatedImageService lets developers create or replace tracks using existing frames, with custom tracks saved in the place. This provides an alternative to manually scripting spritesheet frame selection and timing.
Access requires admission to the Early Access Program. Roblox is accepting applications and admitting creators in waves; check Early Access Programs in account settings for access. The announcement will carry updates as admissions and features expand.
Keep tests away from production
Roblox warns that standalone place files saved with AnimationPlayer may not remain compatible with Studio Beta. Do not modify or save live games while enrolled: they become unplayable for users outside the program. Revert the account setting before editing live games or Team Create projects. Team Create is unsupported, and Studio autosaves can leave collaborators outside the program unable to access the project.
Our recommendation is to apply this week and, once admitted, import a representative Aseprite asset into a separate place. Compare timing and track switching with your current implementation, preserving any spaces in track names. Test representative animation density: Roblox warns that large or numerous images may perform poorly. Playback is not synchronized between clients, and API names may change, so treat this as workflow evaluation rather than a production migration.