Why power of two is a conditional requirement
Power of two describes each complete texture dimension: 64, 128, 256, 512, and so on. A 256 × 512 texture qualifies even though it is not square. A sheet containing 32 × 32 cells does not automatically qualify; three columns produce a 96-pixel width before any additional space. Cell geometry and texture allocation answer different questions.
Rules checked November 9, 2026: Unity 6.0's NPOT scaling setting can preserve non-power-of-two dimensions, and SystemInfo.npotSupport reports GPU support. That is not a universal promise about every compression format or build target. Inspect the actual imported texture rather than assuming every Unity sprite must be a square power-of-two file.
Godot's stable image-import documentation recommends, but does not require, power-of-two sizes in its 3D sizing advice. Its default 2D import settings use lossless compression without mipmaps. This does not justify imposing a mandatory power-of-two source grid on every AnimatedSprite2D animation.
MDN's WebGL texture guide explains the actual WebGL 1 restriction: NPOT textures need clamp-to-edge wrapping and non-mipmapped nearest or linear filtering. Khronos's WebGL 2 specification removes those special NPOT restrictions. Renderer version matters more than a blanket “web games require 512” rule.
Step by step: choose the smallest necessary change
- Identify the destination renderer and build target. Write down whether the asset is a nearest-filtered character animation, a repeating surface, or a texture that will shrink substantially. Do not choose dimensions before knowing which behavior you need.
- Export an ordinary PNG from the packer or slicer. Record the full sheet dimensions, common cell dimensions, and actual frame count. Those values let you distinguish an import scaling issue from an incorrect crop.
- Import the sheet with your intended filtering, mipmaps, and compression settings. Compare its effective imported dimensions with the source. A successful editor preview alone does not establish that the mobile or browser build uses the same texture format.
- If the target specifically requires power-of-two allocation, prefer expanding the canvas without scaling the drawings. For example, a calculated 300 × 180 sheet fits inside a 512 × 256 canvas. Keep the frame rectangles unchanged and describe the unused area correctly.
- Use an external editor or target-specific packer for that canvas change. SheetSlicer currently lays out equal cells from the largest frame plus padding; it does not offer a dedicated force-power-of-two switch. Adding blank canvas is different from stretching the PNG.
- Test the final asset in a local target build at the smallest and largest intended display sizes. Look for missing textures, blurry pixels, edge bleeding, and unexpected repeated edges. Record which import setting fixed the actual problem.
Common pitfalls
Do not expand both dimensions to a square unless the chosen format or destination demands it. A wider blank canvas can substantially increase decoded texture area without adding useful artwork. Conversely, avoiding blank pixels at all costs can be the wrong tradeoff if a particular platform needs a supported compressed texture layout. Measure the build result rather than assuming either choice always wins.
Power-of-two dimensions do not prevent neighboring atlas frames from bleeding into one another. Filtering and mipmaps can still sample outside a frame rectangle. SheetSlicer adds transparent padding but does not extrude border colors. A production mipmapped atlas may need a specialized packing step and target-specific testing.
Do not reinterpret blank canvas as extra animation frames. If a destination uses cell counts instead of metadata, restrict the animation to the populated cells. Keep any metadata synchronized after changing atlas dimensions; old texture-size fields should not accompany a different image.
Related tools and engine guides
Use sprite sheet to GIF to check the animation order before investigating GPU settings. Follow the Godot resource guide for the exported SpriteFrames path and the Unity guide for grid slicing. These are separate checks: a correct loop does not prove that a target GPU import is configured correctly.