Sprite Sheet Size Calculator

PNG is compressed on disk, but the GPU stores textures decoded. A 2048×2048 sheet at RGBA8888 always occupies 16 MB of video memory regardless of how small the PNG was — unless you use a GPU compression format like DXT, ETC2, or ASTC in your engine's import settings.

2048×2048 is supported by effectively every device in use today. 4096×4096 covers most phones from the last decade, and 8192 is desktop territory. If the calculator shows your animation exceeding 2048, consider lowering frame size, frame count, or splitting into multiple sheets.

Mipmapped textures store a chain of progressively smaller copies for clean scaling, which costs about one third extra memory. UI and 2D sprites rendered at native size usually don't need mipmaps; textures viewed at varying distances do.

Rounding 1100×900 content up to 2048×1024 adds empty space that still costs memory. If efficiency is low, try a different column count so the content dimensions land closer to a power of two.

In order of least quality impact: trim transparent borders from frames (packing them via the atlas tool), drop the animation FPS so there are fewer frames, split by action into multiple sheets, and only then reduce frame resolution. The calculator lets you test each scenario before touching your art.