Prevents the engine from failing to load oversized textures.
When Multipack is active, TexturePacker generates two types of files: 1. The Image Files texturepacker multipack
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. Prevents the engine from failing to load oversized textures
: You can drag entire folders into a specific sheet; TexturePacker will sync any changes to that folder automatically. When textures are packed tightly, bilinear filtering can
: When publishing, you can use the {n} placeholder in your file name (e.g., sheet-{n}.png ). This is automatically replaced by the sheet's name or number to distinguish the output files. Common Limitations