Texturepacker Multipack (360p 2027)

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.

: Specifically, the Multipack feature allows for the creation of multiple texture atlases from a single set of textures, which can be useful for organizing assets by size, texture type, or other criteria. texturepacker multipack

Change the setting from "Off" to "Manual" or "Automatic". On a single atlas, this is trivial

: All sheets in a Multipack project generally share the same settings for file type, padding, and size. TexturePacker GUI: User Interface documentation Moreover, if a sprite is split across pages

💡 TexturePacker Multipack is the bridge between "too many assets" and a "high-performance game." It removes the manual labor of asset management so you can focus on coding. If you'd like, I can dive deeper into: How to set this up specifically for Phaser or Unity . The difference between Manual and Automatic packing logic. Ways to further reduce draw calls using these sheets.