Texture Memory Planner

local processing
Plan the GPU memory your textures need: enter sizes, counts, mip maps and compression formats, check them against a memory budget and a target platform, see what each format costs and which choices will not work, and export the table. Everything runs in your browser.

Texture Memory Planner

What it is

Textures are usually the largest part of a game’s memory, and their size depends on more than width times height. A full mip chain adds about a third, block compression changes the cost per pixel by a factor of 4 to 16, and sizes round up to whole blocks. This tool adds up your textures with exactly these rules. Enter a list by hand, paste lines, or drop images to read their sizes; choose a format and a usage for each texture; and compare the total with a budget. It warns about sizes that are not a power of two, sizes that do not fit the compression blocks, formats the platform cannot use, textures above the usual size limit, and uncompressed textures that could be much smaller. A table shows what the whole set would cost in other formats, and a CSV or JSON export lets you share the numbers.

When to use it

Use it early in a project to set a texture budget, when a target platform runs out of memory, before you choose a compression format, or to see which handful of textures cost the most. Compare the same set as ASTC 6×6 and BC7 to see what each platform would pay.

Gotchas & limits

These are estimates of the texture data only: engines add padding, alignment, streaming pools, render targets and their own copies, and drivers may store formats differently. Platform support and size limits are common values, not guarantees; check the devices you ship on. Block-compressed formats lose some quality, so look at the result before committing to a coarse block size. Sizes are in binary units (1 MiB = 1,048,576 bytes). Mip maps are counted for the full chain down to 1 × 1.