Texture memory calculator
Estimate the raw pixel budget of a complete texture set, including maps with different dimensions, channels, precision and tile counts. Compare each group, your texture-only target and a half-resolution alternative before testing actual memory use in Blender.
Build your texture set
Each row represents images with the same settings. Count every UDIM tile and unique image once. Reusing one image across several materials does not create another copy in this budget.
Estimated uncompressed texture storage
138.7 MiB
4 map groups · 4 images · 0.14 GiB total
- Base pixels, without mipmaps
- 104 MiB
- Half width and height for every map
- 34.7 MiB · saves 104 MiB
- Largest group
- Base colour · 64 MiB
Within your 512 MiB texture-only target by 373.3 MiB.
This is a raw pixel budget, not Blender’s measured VRAM use or compressed file size. GPU channel padding, compression, internal precision and engine allocation can change memory use. Geometry, render buffers and applications need additional space; do not use your GPU’s entire capacity as the texture-only target. Examples are starting points, not recommended settings for every asset.
How to count your texture images
Use one row for each group with identical settings. A material with five maps across four tiles uses twenty images. Count a shared image once; count distinct variants separately. Use three channels for RGB data and four when budgeting an alpha channel, while remembering that an engine may pad RGB to RGBA internally. A single-channel input is a raw-data assumption, not a promise about GPU storage.
A mixed-resolution example
The four-map preset contains two 4,096 × 4,096 RGB images and two 2,048 × 2,048 single-channel images, all at 8 bits per channel. Its base pixels total 104 MiB, or approximately 138.7 MiB with the full mipmap estimate. Halving both dimensions yields 26 MiB before mipmaps. These are arithmetic examples, not quality recommendations.
Check the complete workflow
The calculation and its limits
Base bytes = width × height × channels × (bits per channel ÷ 8) × images. The mipmap calculation halves each dimension, rounding down and stopping at one pixel per axis, then sums every level through 1 × 1. Large square images approach four-thirds of the base size; narrow strips can have greater overhead. Halving both dimensions of an even-sized image cuts the base pixel budget to one quarter. The estimate does not include an engine’s extra working memory.
Choose a Blender texture-painting workflow →Khronos OpenGL specification: mipmap dimensions