Texturepacker Multipack Jun 2026

: For automation and scripting, TexturePacker provides a CLI, enabling developers to incorporate atlas creation into their build processes.

Finally, the multipack feature elegantly handles the often-overlooked issue of . When textures are packed tightly, bilinear filtering can cause adjacent sprites to “bleed” into one another. TexturePacker combats this by extruding a border of duplicate pixels around each sprite. On a single atlas, this is trivial. However, on a multipack, sprites that touch the edge of a page do not have neighbors beyond that page. TexturePacker’s multipack algorithm intelligently applies extrusion only to internal edges, while sprites on the page boundary receive outward extrusion safely. Moreover, if a sprite is split across pages (which it should never be—the algorithm prevents this), the extrusion logic would fail. The multipacker ensures no atomic sprite is fractured, preserving visual integrity. texturepacker multipack

Change the setting from "Off" to "Manual" or "Automatic". : For automation and scripting, TexturePacker provides a

: Users can customize how textures are packed, including settings for padding, spacing, and rotation, allowing for fine-grained control over the atlas creation process. TexturePacker combats this by extruding a border of

: In Manual Multipack mode, a smart folder cannot be split across multiple sheets. If you need to distribute the contents of one folder across different sheets, you must add the sprites individually.

Multipack works out-of-the-box with most major frameworks, including: (via the TexturePacker Importer) Cocos2d-x Phaser PixiJS LibGDX