// Before Texture playerTex = new Texture("player.png"); // After (no logic change needed in your entity class) TextureRegion playerTex = gameAtlas.findRegion("player"); 1. 9-Patch (Scalable UI) Name your raw files with .9 (e.g., panel.9.png ). In TexturePacker GUI, enable StripWhitespace and Ignore blanks . LibGDX will automatically load them as NinePatch objects. 2. Pixel Perfect (Retro Games) If you make pixel art, turn off filtering (set to Nearest ) and turn on edgePadding = false to prevent bleeding between sprites. 3. Debug Visualization LibGDX has a built-in debugger for atlases. Render this to see if your packing is efficient (red = empty space):

public class AtlasPacker public static void main(String[] args) // Settings TexturePacker.Settings settings = new TexturePacker.Settings(); settings.maxWidth = 2048; settings.maxHeight = 2048; settings.pot = true; // Power of two (required for legacy devices) settings.filterMin = TextureFilter.Nearest; settings.filterMag = TextureFilter.Nearest; // Input: raw images, Output: folder for assets TexturePacker.process(settings, "../raw-assets/ui", "../android/assets/ui", "ui-atlas"); System.out.println("Packing complete!");

Set up your assets like this:

If your game uses "player_stand.png" and "player_run.png" , pack them into the atlas. LibGDX’s TextureAtlas can act as a drop-in replacement for AssetManager .

// Or create an AtlasSprite for advanced animation AtlasSprite cursorSprite = new AtlasSprite(gameAtlas.findRegion("cursor")); Here’s where the magic happens. You don't need to change your code logic.

If you’ve been developing with LibGDX for more than a week, you’ve likely heard the mantra: “Batch your draw calls!”

Run this every time you change your art. Put it in a Gradle task so you never forget. Step 4: Loading the Atlas in LibGDX Once packed, you get two files: ui-atlas.atlas and ui-atlas.png . Copy these to your Android/assets folder.