See what your textures really cost.

Drop a texture set or ZIP. Get a platform-aware memory budget, compression comparison, and an optimization plan in seconds.

Open the texture set analyzer

Analyze a complete texture set or ZIP

Choose the real source files instead of entering every width, height, quantity, format, and mip setting by hand. The browser tool reads supported image headers, expands ZIP entries locally, hashes exact duplicates, samples decoded alpha where supported, and calculates each mip level with GPU block rounding.

  • Download size and expanded source bytes
  • RGBA8-equivalent uncompressed GPU memory and exact mipmap overhead
  • Desktop, Mobile, and VR / Quest recommendations
  • BC1, BC3, BC5, BC7, ASTC, ETC2, and KTX2 transcode comparisons
  • Unused alpha, duplicate, oversized-map, normal-format, and ORM packing checks

Run Texture Budget & VRAM Analyzer

What does the texture memory calculator measure?

The analyzer reads every supported texture in a set, totals its decoded RGBA8-equivalent GPU cost, calculates the complete mip chain, compares desktop and mobile GPU formats, and identifies duplicate data, unused alpha, oversized maps, inefficient normal maps, and channel-packing opportunities.

Uncompressed baseline

RGBA8-equivalent allocation plus a complete mip chain

Desktop formats

BC1, BC3, BC4, BC5, and BC7 comparisons

Mobile formats

ASTC and ETC2 estimates with KTX2 delivery context

From texture set to a defensible memory budget

A useful budget starts with the files that will actually ship. Upload the set once, then compare the same source against Desktop, Mobile, and VR / Quest targets.

  1. Upload the complete set. Choose multiple texture files or a ZIP. Supported files are inspected locally and grouped as one material budget.
  2. Choose the target. Switch between desktop, mobile, and VR / Quest presets to change resolution ceilings and recommended GPU formats.
  3. Review the plan. Inspect per-map savings, channel-packing opportunities, duplicate files, alpha use, and the final recommended total.

Texture Budget & VRAM Analyzer FAQ

Do my texture files leave the browser?

No. Texture inspection, ZIP extraction, duplicate hashing, alpha sampling, and memory estimates run locally in the browser. PLAYTEX AI does not upload the files for this analysis.

Are the GPU-memory numbers exact?

They are deterministic estimates from the texture dimensions, mip chain, channel layout, and selected GPU compression. Engine import settings, platform support, streaming, virtual texturing, alignment, and driver behavior can change the final resident memory.

Can the analyzer open a ZIP with several materials?

Yes. It expands supported image files from a ZIP, preserves their paths, detects exact duplicates across folders, and reports skipped or unreadable entries separately.