Managing Large Frame Counts: Multi-Sheet and Grid Layouts
When one sheet isn't enough: row vs grid layout, multiple sheets, and keeping metadata usable in your engine.
Long animations or high FPS can mean hundreds of frames. A single 4096×4096 texture fits only so many frames before you run out of space. Multi-sheet layouts split frames across several PNGs so you stay under size limits and still get one metadata file (or one per sheet) that describes every frame.
Row vs Grid
Row layout: place frames in a single row until the row width hits the max; then start a new row or a new sheet depending on the tool. Grid layout: fix the number of columns (and optionally rows); when the grid is full, start a new sheet. Row is good when frames are wide (e.g. full-screen); grid is good when frames are small and you want to fill the texture efficiently.
For row layout, the tool might create one PNG per row or one PNG per N rows until a max dimension is hit. For grid layout, you typically set columns (e.g. 8) and the tool fills rows then starts a new sheet when the current sheet is full. Grid uses space more efficiently when frame size is uniform; row can be simpler for very wide frames where stacking rows would make the texture too tall. Check your tool's options for "max width", "max height", or "max sheet size" and how it decides when to start a new file.
Estimating sheet count
Frames per sheet ≈ (maxWidth / (frameWidth + padding)) × (maxHeight / (frameHeight + padding)) for grid. For row, it's roughly maxWidth / (frameWidth + padding) frames per row, then as many rows as fit in maxHeight. Total sheets ≈ ceil(totalFrames / framesPerSheet). Run the numbers before exporting a long animation so you know what you're getting.
Metadata and Engine
Some engines expect one texture per animation; others can reference multiple textures. When you export multiple sheets, the metadata may list sheet index and rect so the engine can load the right texture and sample the right rect. If your engine only supports one sheet per animation, you may need to split the animation into multiple clips (one per sheet) and stitch them in code.
Metadata format matters: each frame entry might include a "texture" or "sheet" index and a rect (x, y, w, h). Your loader then binds the correct texture for the current frame and uses the rect for UVs. If the engine has no multi-texture support, you'll need to split the animation into segments: e.g. frames 0–63 on sheet 0, 64–127 on sheet 1, and play them back-to-back in code so the transition is seamless. Document how your tool numbers sheets and frames so that the engine or script can map frame index to (sheet, rect) correctly.
Recommendations
Set a max sheet size (e.g. 4096) and let the tool spill into the next sheet. Use grid layout for small frames to maximize density. Keep FPS and scale reasonable so that total frame count doesn't explode (e.g. 24 FPS × 5 s = 120 frames; at 512×512 per frame you might fit a few rows on one 4096 sheet).
Plan ahead: estimate frame count (duration × FPS) and frame size to see how many sheets you'll get. If you need to reduce sheet count, lower FPS or scale, or use a smaller max sheet and accept more files. Multi-sheet is a normal part of long or high-framerate animations; the key is having consistent metadata and an engine or script that can handle multiple textures per animation. Test with a short segment first to confirm the pipeline before committing to a very long export.
Summary
Use row or grid depending on frame size; set max sheet size and let the tool create multiple PNGs. Ensure metadata includes sheet index and rect per frame, and that your engine or script can load the right texture and rect for each frame. Tune FPS and scale to balance quality and sheet count.