Web containers
Focuses on KTX2 and Basis workflows that are practical for browser texture delivery.
WebGL texture delivery
Convert textures for WebGL delivery
Prepare browser-friendly KTX2 or Basis textures from common source images and keep a path to WebGPU-ready outputs when your runtime supports them.
Tool entry
Choose a WebGL texture output
Start with KTX2 for modern web delivery or Basis Universal when your pipeline needs a runtime transcoding asset.
What this page covers
Compression choices
Points you toward UASTC, ETC1S, or Basis output depending on quality, size, and runtime needs.
Runtime checks
Pairs with the WebGPU support page and Texture Doctor when you need compatibility and container validation.
How to use it
Choose KTX2 or Basis, upload a source image, and export a browser-oriented compressed texture asset.
- 01
Choose the web container
Use KTX2 for modern delivery or Basis when your runtime pipeline expects it.
- 02
Upload a source texture
Load a supported raster, HDR, or EXR source image into the encoder.
- 03
Validate the output
Inspect the exported texture with Texture Doctor before shipping it in your web app.
FAQ
KTX2 is the preferred modern container for many web engines, while Basis remains useful for pipelines that already expect .basis assets.
Often yes when the runtime supports the target payload. Check WebGPU compressed texture support and validate in the engine.
The pages run the conversion locally in your browser and do not upload your texture files.